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?
As of now, I can only direct you to the Note we added here: Which operating systems are supported?
Isn't that the build that was released yesterday ? I just checked and my TV says im up to date.
From my experience, yes it will change.
Then perform a teamviewer update on the machine you update to Windows 10 2004 and your ID will come back to what it was originally.
If your teamviewer is already up to date, you can uninstall teamviewer and reinstall it WITHOUT checking the box "Remove settings" during uninstallation. Post reinstallation, your teamviewer will have your old ID.
The fix that could be a possible solution is only part of the current Insider build. The version number of this build is 15.7.4.
We released it yesterday (June 17th, 2020), however in About TeamViewer it says June 16th as the date, but this indicates the build date, not the release date:
Please see this article for more information about insider builds and how to install them: What are TeamViewer insider builds?
The devs and I are looking forward to your feedback!
The Teamviewer ID has changed on many of my managed station !!! This should not happen. They were all at the latest version and some station did change others didn't... It's painful to have to call eaxh user to ask for their Host ID. Could someone do something ? Any fix require ? This is quite costly to revisit every managed station/servers....
And that's the version i've tested it with. I wrote "Beta" but I meant Insider preview build 15.7.4.
Please note this is for information only. If you wish to reply, please make it constructive.
I can fully confirm that after upgrading clients from Windows 1909 to 2004 or Windows 1903 to 2004 the Teamviewer ID changes when using the latest version of TV Host, So if you're going to do this upgrade you will need to be at the computer your upgrading unless you have a user on hand that can give you the new ID.
I’m also aware that Windows 10 2004 is currently not on the list of supported operating systems. but an update from TeamViewer Developers would be greatly appreciated.
I hope this information is of help to someone out there during these trying times with most workers working remotely as most of mine are.
I have seen similar posts showing that the Teamviewer ID changes after Windows update 2004 (May 2020) but the situation is far worse than just an ID change. Teamviewer seems to think that it is now inside an entirely new machines and resets everything including Port numbers, Wake on LAN configurations, Display names and many more settings.
As someone who has nearly 100 desktops and laptops connected to Teamviewer, most of which have WOL enabled along with Teamviewer for remote administration, scattered all over the world I am now left totally disconnected and find myself having to give out adminsitration passwords to all staff levels to try and get Teamviewer back connected.
This is a very serious matter and I am staggered that someone at Teamviewer has not picked up that 2004 causes and total disconnection and reset of all TV settings. In these times of needy remote access, losing this vital and expensive link medium could not come at a worse time. We all knew that Update 2004 was proving to be buggy but TV should have identified this fault during the Beta rollout and proving.
Urgent remedy is required please.
Same problems here, unable to connect after update ....
Tested on several hosts ready for upgrade. Please upscale this to highest priority!
Thanks in advance!
We've spent weeks deploying custom hosts to hundreds of client machines via Intune. We started allowing update to 2004 via WUfB to our pilot machines. After the first reboot initiated during service hours, TV changes TV ID. Another reboot, and it gets back the old TV ID and still shows in our TV apps as online. However, now any computer that's updated to 2004 has lost all the settings originally pushed by our TV policies. There are no saved passwords, account assignments, no easy access, etc. This is a HUGE mess. What is TeamViewer doing for host installs? The insider build is only for full version as far as I can determine.
EDIT: I downloaded the host MSI from TV design & deploy. It is showing as 22.214.171.124. Uninstalled the version I had on my 2004 test system through Intune and deployed 126.96.36.199 to the 2004 test system. Still doesn't TV policies or assign to my account, etc.
The excuse of 'please see the post that says the Windows10 update is unsupported' is very inflammatroy. As other users have posted (3 weeks ago), this should have been a priority#1 email send to ALL TeamViewer customers. Priority #'1!
I'm now in the sitaution where multiple Windows PC's in multiple countries have gone offline, which operate as commercial scoreboards (no KVM or client access possible), and with the global lockldown we're unable to go there. Even then, that has a huge expense incurred, and to say this again - this should have been informed directly by email, clearly, and with PARAMOUNT importance, as preventative steps could have been taken to defer any PC auto update, and you were aware of this 3 WEEKS ago.
What are you going to do about this please?
Still not working! After extra reboot with RDP original ID is back but my credentials are lost...
Any news about a working version?
@GFORCE1 : If you can get in through RDP, either Update Temviewer to latest version, or if it is already up to date, uninstall Teamviewer and DO NOT CHECK "Remove Settings" during uninstallation process, then reinstall it. Your credentials and ID will be back to what they were. That's what I've been doing. I have probably another 500 workstations left to do "Facepalm"
Hi Jean - a month has passed. Any update please, TeamViewer?
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.
Looks like it has not priority to solve this problem! Several costumors want to upgrade to 2004, but we cant because of teamviewer ....
Please upscale this issue to solve this asap please!
After launching the Insider Build (15.7.4), we collected feedback from some users who helped us with the diagnosis and analyzed many Log Files. Thanks to all of you providing us with insights!
As background information, the ID switch does not happen on all machines that upgrade to Win 10 2004.
However, it turned out, the fix implemented in the Insider Build did not resolve the problem completely, and with this, our dev teams went back to the drawing board.
We now have a new version available.
The next step is testing.
I could convince the dev team to provide me with the download link to be published in our community.
Surely we can be much faster with providing a stable version that fixes the issue, the more testers we have.
Therefore - if you would like to help us testing: Please download TeamViewer from this link and provide us with your feedback in here (or via ticket).
Disclaimer: As any Insider build it is not recommended to use the insider build in a production environment or to roll it out globally on all devices you have in place. Also: It is recommended to install the Insider Build on devices you can reach directly so in case of issues you can revert changes quickly.
This version is working on a test machine! Now testing on a (virtual) second machine.
Keep you posted!
In virtual machine the test failed .....
Lost the ID but came back on a reboot, but credentials still lost .....
Thanks for the feedback!
The devs would love to review the log file of the device that failed the test.
May I ask you to send the log files to us via https://support.teamviewer.com/ ?
Thanks a lot in advance and we are happy to read more feedback!
I already forwarded it to the dev team.
Thanks heaps for your super fast help 🙌 I hope your logs help them to find the cause for it.
just checking in for some more feedback from all of you who tested the new version I uploaded here. Did it work? Did it fail?
@GFORCE1 First of all thanks for sending your logfile!! The team reviewed it and they have some questions
Thanks again and we are looking forward to more feedback from you guys 🙌
Have a great day,
This windows is installed in a VMware Workstation 15 envoirement. Its on a SSD with a I7 9700K @5GHz soc.
PS on the other system i tested was a real machine and went well , as i stated before ;-)
Thanks for your reply! This is already a great starting point for the developers!
To be able to reproduce the case, would you mind sharing how exactly you tested the version/update of the OS on the VM?
(If you prefer, you are also welcome to describe your process via your ticket.)
We can keep the community updated on all relevant news in parallel 👍
Thanks again for your help!
I will try to reproduce it again and write down the procedure!
(This cost me a lot of time ......)
Thanks a lot @GFORCE1
I appreciate your help and your time invest here 🙌
Did the upgrade this morning and send the files by mail to support. Can you confirm that you received the files?
Confirmed 👌 And already forwarded to the devs. They will have a look at it immediately.
Thanks a lot 🍀
Hoping this may assist in your solutioning - I've a total of just 8 Win10 PC's I have are configured identically, same hardware. Fast boot off on all. 5 work, 3 offline/changed password. Here's the strange fact - at one site, I've one PC that has changed password (can't connect), and one PC that's working fine, with the update to v2004, on the same LAN with software versions the same?
Look forward to a solution soon, as I mentioned in the thread, we would need a site visit to Germany, Norway and France to revive these PC's, which isn't really acceptable. Luckily, 2 PC's in Dubai are ok. Most of our 60 machines running TV are Ubuntu thank goodness..
I am happy to let you know that the devs released a new TeamViewer version (15.7.7) with a fix for the problem with the possible switching TeamViewer ID when updating to Windows 10 Update 2004.
I posted the Change Log here.
Thanks to all of you who provided the feedback via this thread and mainly via our ticket system to our development teams! Your help was crucial to get this fix live!
Thanks and best,
Sorry - forgot to add the most important part of the info 😅
You can download the TeamViewer full version and the TeamViewer Host here: https://www.teamviewer.com/en/download/windows/
@GFORCE1 oh no - that´s not the news I was expecting. But yes - if possible, it would be great if you could send the logs again. I reply to your ticket and so you can send them easily as a reply to me.