Users report a bug with Windows 10 2004: it downloads and at the end a message appears warning that it is not compatible

Almost two months ago the Windows 10 May 2020 Update began by Microsoft. The last update of Windows 10 in which it is also known as version 2004, began to reach users with compatible computers in stages in order to prevent them from a possible failure would extend beyond what was desired.

And we already saw how Microsoft was going to take care of notifying all those users whose computers were not compatible. A notice that apparently is causing complaints in its operation, since some affected people affirm that this notice is also displayed on the screen even when the update has been downloaded.

First it downloads and then alerts

Microsoft did well by offering a staggered release, seeing the bugs caused by the Windows 10 May 2020 Update and even forcing the company to release a loaded patch of fixes to mitigate existing issues.

"

In theory, the warning should appear when we checked for the update by accessing the path Settings > Update and security > Windows Updateand select Check for updates. You should then see something similar to this message:"

The problem now is that machines that are compatible and on which the update is offered, see a similar message appear on the screen with the update already downloaded A somewhat vague error message, because they also complain, it does not describe the reason for the update blocking or indicate an alternative solution.

If you are affected by this issue, a thread has been opened in which a Microsoft representative details possible solutions to remove the update lock. They offer three possibilities if you are affected by this problem:

• Update drivers for computer hardware, such as the display, audio, or Bluetooth.
• Open Windows Security> Device Security> Core Isolation and disable the feature.
• You can also check the Windows 10 2004 support page for new solutions.

If you are affected by this bug, you can try one of the solutions proposed in the thread affected and wait for Microsoft to fix it resolve permanently.

Via | WindowsLatest