Teamviewer ID Changed after upgrade windows 10 2004 verion (May update), Wasted my Teamviewer bussiness subscription two device moves. -_-
Hi @TGeRi
As of now, I can only direct you to the Note we added here: Which operating systems are supported?
Best,
Esther
What will happen on older versions?
For example if I have a v14 on win10x1909 and that win updates to v2004? Will the ID change then?
Hi @CompuShark
We released the Insider Build in question a few minutes ago.
Please give the version 15.7.4 a try.
Thanks and best,
Yuri, I have tested the Beta build on one of my bench workstations. It originally had Teamviewer Host 12 with and ID of 1 177 *** ***, I uninstalled Host, reinstalled Full version by keeping the settings, updated to the Beta build.
I made sure I had access to the workstation with the same ID of 1 177 ***.
Then I proceeded with updating Windows 10 1909 to Windows 10 2004. The ID CHANGED.
I uninstalled Teamviewer Full version (Latest version with beta ) by keeping the settings again. I reinstastalled Teamviewer Full and my old ID of 1 177 *** came back.
I perform the Teamviewer update to Beta version again, My ID of 1 177 *** stayed.
I hope this helps. I send you my troubleshooting bill
Yuri, alot of us are using Teamviewer HOST on our clients workstations. That option is NOT available for the HOST, only FULL install.
One thing I noticed, if the remote teamviewer isn't the latest version,. Update Windows 10 to 2004 THEN update teamviewer host to latest version. It brings the original ID back. ( might have to ask an onsite person or activate RDP and connect from another machine )
Hi all,
Thank you for all of your feedback and we value your input to the community.
After sharing all of your feedback to our development team they found a fix that could be a possible solution. We decided to ask community users to use the insider build which will be rolled out in a few days in order to make sure that this fix will work for everyone.
The intention is to get early feedback on new features, improvements and developments before the public release.This means that the current TeamViewer insider build version may not be tested in full functionality and could contain bugs as it is basically an image of the current development state.As this is a testing environment it is not recommended to use the insider build in a productive environment or to be rolled out globally on all devices you have.
Finally, I apologize for any inconvenience caused and we look forward to hearing your feedback after using the insider build.
Kind regards,Yuri
Hi TeamViewer has really screwed up here, possibly for the last time for our business,
Do you have access to them by any other means aka "backdoor"?All our computers are running a Midnight_update BASH script that pulls repositories etc.Anyhow IF you are able to push command in any way to the remote computer, this might help you:
https://community.teamviewer.com/t5/Knowledge-Base/Command-line-parameters/ta-p/34447
E.G."\Program Files (x86)\TeamViewer\TeamViewer.exe" assign --api-token NNNNNNN-XXXXXXXXXXXXXXXXXXXX --group-id gNNNNNNNNN --grant-easy-access --reassign
You create you api-token under Design&Deploy (See attachment)Find your group ID by selecting your desired folder, and look at the current URL in your browser (see attachment)group-id
This is insane! We user TV HOST on almost all of our computers. We have hundreds of computert in our list. I will have to MANUALLY READD them?? TV, please fix this ASAP!
We pay a lot of money. The purpose of TV is to remotely access a computer... I cannot evet reboot what was suggested before if I cannot access the PC!
We use host as a lot of computers don't have console (keyboard-mouse-monitor) attached to them. Because of this bug we would have to go to the remote (100 kms away!) location by person with a keyboard-mouse-monitor in our hands just to look at the new TV id and to reassign the machine????
Same issue here. See how the ID changed when going from 1909 to 2004. We are using Teamviewer on remote, submerged, field locations! They are as inaccessible the Voyager! And now we lose access to them.
Wow, that crazy update to Build 2004 Changed the Teamviewer ID of the laptop! That has never happened as I have had that same ID on that pc for Over 6+ years!!! So weird.
SO SOLVED! Thanks for making me look closer. WATCH OUT IF YOU UPGRADE TO BUILD 2004.
Me, on my desktop pc, I still run W7 Prof and NEVER GOING TO CONVERT!!!
PS, I LOVE TEAMVIEWER!!! THANKS!!!
Thanks, been there done that. I was in I.T. for over 25 years. I can always restore my Acronis Backup. This laptop is so slow. All I use it for it to sometimes watch some internet things on my tv! It is so weird that it can see all the other pc's online on my account, but I cannot see it!!!
Hi @SamCCFL99
Could you please try to completely restart the computer, applying any new updates, even small ones?
Please note that It may be needed to restart it more than once.
Best regards
To top it off, the laptop can see my PC and also my friend's PC, SO what is going on? Some port blocked in B 2004? So annoying.
Hi, I upgraded to W10 Build 2004 on my laptop and when it came up, it was not even signed in. I sign in and it says connection ready, but my main PC says it is offline. I tried everything, and I am not a dummy. This never happened before.
Anyone else???
Hi
Today a user with a Dell laptop came across the same issue and returned to the old ID after the 3rd restart and some further Windows updates.
I'm posting the link of this thread here as it could be helpful for now.
At this point I've given up on Teamviewer fixing it and I'm already half way through my machines getting 2004 and fixing them. Since I've been paying more attention to this I've noticed 2 things. Its only been the laptops (90%) of our machines. If I open TV Host and click the assign to client button and put our email in. It adds it and uses the NEW host ID. If I get it on our network and push the MSI installer then it reinstalls and uses the OLD host ID that the machine had previously and keeps its description / notes field about it and just overwrites the alias / hostname to the PC name and removes the added - username that I manually edit after the initial install. Hope the info in this thread helps anyone else with this issue as the TV Support idea of reboot the machine has not fixed 1 machine of ours.
V12, as are all my hosts and so far 100% ID change. What is the point of unattended hosts when a remote computer upgrades? This is going to happen yearly and Teamviewer needs to resolve it.
Do I now have to install another remote access program to do an upgrade just to get the next ID?
Another nail in the coffin?
On top of all of this, I've found a handful of machines still running TV13 or TV14 and the policy enforced I've has always been set on is to auto update including new major versions. If you tell it to check for updates it doesn't do anything either. Its just not been the smoothest service but up until now it hasn't failed me either. Even with those handful running TV13 and 14 still apparently.
@CompuShark wrote: Same Issue here. I support over 1000 computers through Teamviewer. All those computers are different brands and models. Alot are custom builds I did with Asus boards and i5 Procs. so I highly doubt the hardware has anything to do with the issue.So far around 90% of the upgrades I did all changed the teamviewer ID. This is a MAJOR issue. Causes me to have to reach out the the clients in the morning and have to re-add their computers to my list by deleting the original one first.Teamviewer Support Team : We pay alot of money every year to use your program. Please put this as your TOP 1 priority to FIX.
Same Issue here.
I support over 1000 computers through Teamviewer. All those computers are different brands and models. Alot are custom builds I did with Asus boards and i5 Procs. so I highly doubt the hardware has anything to do with the issue.
So far around 90% of the upgrades I did all changed the teamviewer ID. This is a MAJOR issue. Causes me to have to reach out the the clients in the morning and have to re-add their computers to my list by deleting the original one first.Teamviewer Support Team : We pay alot of money every year to use your program. Please put this as your TOP 1 priority to FIX.
Yeah support wrote back to me today in my ticket after providing a few logs with this issue. They told me if a reboot doesn't fix it then I just have to redeploy the installer but they have sent the logs over to the dev team to look into. The whole point of TV is that you don't have to be local to the network to connect to it. Never had this issue going through the last 3 or 4 big windows updates. So yeah, needless to say we are a 200pc shop compared to you and a smaller fish, but we will be looking into other remote solutions when I get time. Being mainly a 1 man show... I don't have time to fix all these machines TV connection. With so many people working from home right now and not in the office, doing a GPO / local network push isn't exactly ideal. So when a user calls for something broke and I go oh lets fix your TV connection first... It makes me look bad.
Hi @bclark88 ,
Thank you for attaching a logfile in the support ticket.
I confirmed that our technical support team has investigated the case and they will back to you via the support ticket.
Thank you for your patience and your understanding ?
@bclark88
Until the coming of the next one, could you at least try it with one of the current (TV-reinstalled) computers?
Thank you in advance
@Vatsilidis I can try the cortona thing on the next one I get.
@Yuri_T Also for the support ticket opened for me, I updated it with some info but I don't have old/new ID's for any of the machines previously broken. I could get you log files though for some if that still helps.
Thank you for your feedback.
I have talked to our support team regarding your case and they would like to know more information to investigate.
Since you have a TeamViewer license, I have sent a support ticket. Please read an instruction and reply to the ticket.
What we need in the support ticket:
I will make sure that our technical support team will get back to you as soon as you reply.
Thank you for your understanding and I apologize for any inconvenience caused.
I'm trying to figure out what could cause this strange behavior after this update. I tried to reproduce it, installed the update but the TV ID didn't change after reboot.
One detail in this update that seems strange to me, after reading this official related article, is that Microsoft rebuilds Cortana and tightened its security affecting third-party apps by this:
"Security: tightened access to Cortana so that you must be securely logged in with your work or school account or your Microsoft account before using Cortana. Because of this tightened access, some consumer skills including music, connected home, and third-party skills will no longer be available."
After that, I'd like to find out if someone of you guys could completely disable Cortana, restart the pc and look if this changed the ID to the previous one. I prefer to try this in a pc that didn't reinstall the TV app after the 2004 update if possible.
In order to do that you can find the steps in many articles on the web. I provide as a sample here this one. Please note is a different procedure for the Home version than the Pro or Enterprise one.
Waiting for updates if this makes the change.
@Yuri_T A reboot does NOT resolve the issue. At least not with any of the HP ProBook 650 G2, G3, G5 series laptops. I have over 30 machines now that have received this update and every single one has had to have Teamviewer reinstalled. Yes I have most of them try rebooting as I was hoping that would initially fix it.
Hi All,
Thank you for sharing your feedback in this thread.
In many of these cases, it appears that some hardware is not detectable by TeamViewer after the update and this causes the ID to switch as the software thinks it is on a different machine.However, in this case we have had many reports that a simple restart of the system will allow TeamViewer to detect all the hardware again bringing back your old ID.
Please let us know if this works for you as we value your feedback in the community!
Hope this information will be helpful and we will keep you updated.
Any update on this? So far it seems like a few desktops didn't get a new ID or break. But we mainly have laptops and they are all breaking. All are HP ProBook 650's and are G2, G3, G4 and G5 models.
Hello @iteprogrammers @daniellee @Curtg @bclark88 and @Vatsilidis,
Thanks a lot for your messages! ?
This is, unfortunately, expected behaviour of the TeamViewer ID.
As the TeamViewer ID is linked with the hard- and software of the device itself, a change of the hardware or a major update of the OS can lead to a TeamViewer ID change.
We will keep you posted as soon as we have more information regarding this.
Jean
