The Windows 10 May 2020 Update: A Disaster.

The Windows 10 May 2020 Update: A Disaster.

Windows 10 It appears to be causing problems again. This time, the issues relate to installing the May 2020 Update, which has proven problematic for users attempting to manually install it via Windows Update. Worse still, Microsoft hasn't provided an official explanation for the nature of the problem.

The issue has been reported by many users in the Windows Answers section of Microsoft's Community pages, as well as the Super User technical forum, with Bleeping Computer and Techdows both investigating the issue (via TechRadar).

What makes this particular error very frustrating is the following message:

Your PC settings aren't yet supported on this version of Windows 10. Microsoft is working to add support for your settings soon.
No action is required. Windows Update will automatically offer this version of Windows 10 when these settings are supported.

Being told nothing's wrong is comforting. Likewise, being unable to do anything to fix the problem or even having an idea of ​​the settings the error refers to is very helpful.

A possible solution

One potential answer, spotted by Techdows, comes from Jenny Feng, a Microsoft employee who discovered that the solution may lie in a driver issue.
His suggested solution is to update your hardware drivers first, then go to: Impostazioni> Sicurezza di Windows> Sicurezza dispositivo> Dettagli di isolamento del coreFrom there, you need to select the "Disable Core Isolation" option. This seems to have a good success rate, but it doesn't work for everyone—the positive feedback is based on what users have written after trying it, but it might only be worth a try if you really need to install the update.

The other potential option is to install the update with your PC disconnected from the InternetThis is done by first downloading the ISO file containing the update, then rebooting the offline PC and running the update from there. However, Microsoft employees have warned forum users against doing this, likely because it could cause the device to freeze if the update encounters a different error and cannot be resolved. As usual, the best solution to this problem is to wait. It may take some time for Microsoft to respond, but it should eventually resolve the issue. 

Source: Tom's Hardware

Newsletter