Re: Mise A Jour Windows 10 1909
Sandrine Willert
With the Pause in place you dont see it but once the pause period has expired or the Resume Updates button is pressed and all patches installed, it rears its ugly head on my Win10 Home 1903 computer under Optional updates.
Also, 1909 home machine is updated to january patches, but on both 1903 pro machines windows update has not updated them to january (december updates was the last installed). Updates are always installed one month after, using the methodology of not allow updates until the last part of the month.
Just fired up a fresh 1903 VM. Feature updates 365 and Quality updates deferral to 0 and updated. Not offered. Dropped feature updates to 0 and was offered update to 1909 but not 4532695. Playing with the feature update deferral dates after that starts installing 1909.
The 1903 system where I have KB4528760 installed is a recently purchased (about 3 months old) Dell XPS 8930 desktop system (i7-9700 CPU, 16 GB RAM). It came pre-installed with Win 10 version 1903. It seems highly unlikely that this system would be incompatible or have its hardware blocked. How is it possible that the 1909 Feature Update would not be made available or be offered for this system?
If you have any Pause or Feature deferral set, you may not see the 1909 Feature update.
Have you installed the latest .NET update being offered through WU? There has been some indication that that may factor in also.
So my current thinking here is that the presence or absence of KB4532938 is what determines whether or not a system gets offered the Feature update to 1909. But then the question is why was KB4532938 offered to only the 1st system, and not to the 2nd one?
you could check and compare these registry keys between the two
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WaaSAssessment]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\OneSettings]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UpdatePolicy\PolicyState]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators]
[HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WaaSAssessment]:
Almost all values are identical between the two systems except for these two: ETag (REG_SZ) and refreshAfter (REG_QWORD). These two values are completely different between the two systems, and I have no idea how to interpret their meaning.
And if i just install the KB, it said that i cannot install this kb on my laptop,however i choose the 64bits version as my pc so i don't know how can i install just the kb otherwise if it doesn't work with the Microsoft update catalog.
-EDIT- It's been a while since I did a feature upgrade via ISO download. You mount the ISO file and run setup.exe from there. I believe one of the options presented is to retain existing files and apps and that is what you want to select. After the upgrade to 22H2 completes, you might have to reinstall a few apps, one of them being possibly Eset. I would export your Eset existing settings, if modified, prior to Win 10 upgrade so they can be reapplied if Eset needs to be reinstalled.
According to this article: -management/upgrade-windows-10-eol-versions.html , you should be able to perform a feature update on a Win 10 EOL version via Win Updates. It is possible that is busted on your Win 10 installation.
I had the same issue on two of my computers that were on 1909. I was able to resolve it by using the media creation tool here: -us/software-download/windows10. Click the Download Now and do the upgrade (you don't actually have to create the media).
The ID's assigned based on the hardware and software configuration of each computer. If this happened to you after this new Windows update, it seems that the Windows reconfigured internally some critical application settings.
The one taht is marked as unknown is an upgraded 2004 version windows 10. no matter what i do, reinstall, delete contact regarnt easy access... no matter what it will break after a reboot and go into this unknown state, and become useless.
Do you mean that this contact with the unknown text at the end is a computer that has been updated in the last Windows update 2004 and is not working properly. If this is happening, then it is possible to confirm with the other side the ID that this specific computer has in your contacts list or if it has been changed?
Please remember that the Windows updates can be uninstalled from the control panel. At this moment that I'm writing that, I don't know if the changes that this new update has made in the system can be rollback after the uninstall of the update. We will be in touch about that.
Luckily i had someone near the computer made them turn it on. After which i still saw the remote deivce as unknown and offline. So i vip in and RDP to the computer. TV seems to be working properly but in reality it is not. I try several things reinstalling TV deleting the contact and re-granting easy access. reconfiguring the whole thing...
i will try rerolling the update. however this is not a solution for me as the computers i work with are a part of a hospital network and by contract im required to keep them the most up to date possible.
so i rerolled back to 1909 and it's instantly working as expected. Online in my contacts list no more unknown. I had to grant the easy access aagain however. But this time it sticks i can reboot turn off. WOL also works.
Sure this is not a solution, but I wanted to see the results in order to know what could happen in the case of uninstalling the update 2004 in a normal working environment and also to have a temporary solution to other users to that until this case and your feedback forwarded at Monday to the technical team.
Same issue here. So far about 20 machines have received the 2004 update and its broke roughly 30% of our machines from being linked. So I've been having to get the user give me their ID to manually connect, shutdown teamviewer and then push the host installer through PDQ again which makes the original computer in the list show back online and re-enrolls the account for easy access. Then I update this alias name to add a custom detail in the name. Seems to be hit or miss on if the update breaks it or not. Haven't narrowed it down by model or type yet.
We are all HP's here and I just had a ProBook 650 G5 do it. The ID actually changed from the one in my contact list. When I use PDQ to push the installer for our host, it overwrites the contact entry in the list with the one. Updates it alias but leaves the description/comments field I had info in. So its obviously knowing its the same / previous one somewhere for TV to keep its info about it.
Prior to this warning that microsoft made earlier today there was just a simple option in the windows update which was to download 2004 update. I manually started rolling out the updates trying to get ahead of work. (Could have only done it manually as my AD policies disable the auto update shenanigans)
It is auto installing as normal windows 10 updates do. Windows 10 Pro. This is after it does the reboot to finish installing that it breaks TV. Had 4 more people call me today since getting this update over the weekend and when I go to remote in and help them with other issues I found that TV shows them offline.
@Vatsilidis All of mine are logging in with their local domain accounts. Even restarted a few times to see if it would trigger it to go back to the old ID or something. I'm having to re-deploy the MSI installer package I have setup with PDQ Deploy that has the reassign tags with the ID's and such.
But that's not the solution. So they have to do that the ID is written somewhere in the conf. file. I don't understand the whole thing when it just doesn't work and updates to Windows are just needed, just like a customer where I pay about 200,000 a year, so maybe they will release a package? they are already running out of business because re-extension for these problems is not very visible.
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.
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.
@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.
"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.
d3342ee215