Some Windows 10 users are being blocked from applying the May 2020 Update when manually seeking to upgrade through Windows Update due to unsupported settings on Windows 10 2004.
According to the user reports, they are encountering "This PC can't be upgraded to Windows 10" errors.
While the error dialog says that Microsoft is actively working on a fix or their settings to be supported, it doesn't list the settings triggering the update block.
"No action needed," the users are advised. "Windows Update will offer this version of Windows 10 automatically when these settings are supported."
Reports of Windows 10 1903 and Windows 10 1909 devices being blocked from upgrading to Windows 10 2004 have been surfacing during the last two weeks via multiple channels including Reddit, SuperUser, as well as the Microsoft Answers [1, 2, 3, 4, 5], Microsoft Q&A [1, 2], and Microsoft TechNet sites.
Users advised to update drivers, disable Core Isolation
While Microsoft hasn't yet officially acknowledged this issue and no official solution is yet available, Microsoft software engineer Jennifer Feng replied in one of the report threads as spotted by Techdows, saying that the company does now that some users will receive this message when they're being blocked from updating.
"The block is in place because of various compatibility issues with numerous systems and hardware configurations," Feng added.
Users who have received this safeguard hold message were advised by Feng to take the following actions to have the May 2020 Update offered through Windows Update:
1. Update your hardware drivers
2. Disable Core Isolation by going to Settings > Windows Security > Open Windows Security > Devie Security > Core isolation details.
3. Keep checking Windows 10 2004 release information page for mitigations and resolutions for Known issues.
Updating offline looks like the right answer
Even though these steps haven't been confirmed to work, there is at least one unofficial fix shared by one user on Microsoft's TechNet web portal for IT professionals that has been confirmed to work.
As he explains, all it takes for the update to successfully finalize is to disconnect the affected computer from the Internet after downloading the update ISO/verifying the update and running the update while offline.
"So what I have done is to disable completely the internet on the computer, reboot the computer and install the iso and wait," he said. "Works perfectly now you can reactivate the internet after. It's probably a bug on something when the installer verifies the computer with Internet before installing."
Seven Windows 10 2004 update blocks left
According to Microsoft's Windows 10 2004 health dashboard, seven update blocks are preventing some devices with known compatibility issues from being offered the Windows 10 May 2020 Update (the one caused by unsupported settings is not listed):
• Difficulty connecting to more than one Bluetooth device
• Errors or issues during or after updating devices with Conexant ISST audio drivers
• Errors or issues during or after updating devices with certain Conexant or Synaptics audio drivers
• Variable refresh rate not working as expected on devices with Intel GPUs
• Stop error with a blue screen when plugging or unplugging a Thunderbolt dock
• Issues updating or starting up devices when aksfridge.sys or aksdf.sys is present
• Issue with older drivers for Nvidia display adapters (GPU)
To get around update installation issues, Windows 10 users can follow this guided walk-through or make use of this Windows 10 update problems troubleshooter.
Comments
jmwoods - 4 years ago
I go by the list of Known Issues -
https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004
We're in no hurry to upgrade to 2004.
It's interesting that people complained mightly when Microsoft freely released Feature Upgrades that trashed their systems.
Now that Microsoft is doing blocks, people are complaining.
Pkshadow - 4 years ago
Microsoft wants to get rid of the Control Panel and send people on a hunt for
Got to mention if you are Settings > Windows Security > Open Windows Security > Device Security > Core isolation details. I got to say that is the most convoluted way of getting to something yet.
Stupidity breeds more Stupidity ! What happened to make it simple (stupid) ?
Ok, I believe that if your running anything that has altered your HOSTS file (including your self) to block Win10 from reporting back to MS such as a custom Host file or one that has been altered by Spybot AntiBeacon or just with O&O ShutUp10, MS Autoruns, Open Shell Menu can cause issues.
Why do I say that ? As I run those things including updated Drivers (including AMD Radeon current version for Video Card (as am still supported) and had a miserable install trying to Update to 2004 release.
It did install but I could not run anything as they acted like they were locked up. 2004 of course got rid of my Radeon Control panel and put a older driver in, I need the panel for Scaling. Is a wonderful experience trying to do anything after any Major Update.
I eventually got back to Revert back to previous version and did so, with glee.
So with the above I would think to get to the 2004 Update you will have to undo all customization's and I think you will figure that out once you get rid of the notice in Settings --> Windows Update and the notice saying : Some settings are managed by your organization.
I am probably wrong on needing to get rid of the notice but am sure need to revert back a wack of customization.
AMDphreak - 4 years ago
This sounds like a horrible change. They're making their tool less expressive by lumping all the data together under it with no way to separate them or specify what you wanted.
Why can't they just use my suggestions. I've sent them dozens of excellent ideas in their Feedback center. They don't need to waste their time on stuff like this that's like "Which is better? 1 apple or 2 apples?" Well, I wasn't in the mood for apples at all, so why am I still debating?