Upgrade Block to Windows 10 2004 for devices with Core isolation (HVCI)

[German]Microsoft has set an upgrade stop on the feature update to Windows 10 version 2004 for machines that use hypervisor-protected code integrity (HVCI) or memory integrity (Core isolation).


Advertising

The feature update to Windows 10 Version 2004 was released to OEMs in early May (see Refreshed Windows 10 V2004 ISOs released on MSDN/MVS) and was updated later. On December 27, 2020, the feature update was generally released (see Windows 10 Version 2004/Windows Server 2004 released).

Core isolation/HVCI drivers are a problem

If you try to upgrade your Windows 10 system to Windows 10 version 2004, the upgrade wizard will display the message "Your PC settings must be adjusted before you upgrade to the latest version of Windows 10" if memory integrity is enabled. It then suggests disabling storage integration protection to continue. Techdows has described this here – Microsoft has this KB article about it (where the screenshot was taken).

Upgrade-Issue Windows 10 2004
(Upgrade-Issue Windows 10 2004, Source: Microsoft)

Cause: Incompatibility has been found with certain display drivers and Windows 10, version 2004, when memory integrity protection is enabled. To prevent problems, Microsoft has therefore set an upgrade compatibility lock for Windows 10 version 2004 for affected devices. Microsoft suggests as a workaround to disable the core isolation in the settings of the machine under Windows Security in the preferences. After a reboot, the upgrade should be possible. Details about disabling Core isolation may be found at techdows

Similar articles:
Windows 10 V2004 is ready, rollout for Insider
Windows 10 Insider Preview Build 19041.264 as new RTM.
Windows 10 Version 2004 release between 26th & 28th May
Windows 10 Mai 2020 Update released at MSDN & for OEM
Refreshed Windows 10 V2004 ISOs released on MSDN/MVS


Advertising


Advertising

This entry was posted in issue, Windows and tagged , . Bookmark the permalink.

One Response to Upgrade Block to Windows 10 2004 for devices with Core isolation (HVCI)

  1. Chris Pugson says:

    Thanks for the heads-up. I was unable to disable hyper-virtualisation by normal means but it is possible by disabling the HV Host service, is simple and seems to be a satisfactory alternative. The reduced memory required releases 2GB and the system seems much quicker.

Leave a Reply

Your email address will not be published. Required fields are marked *

Note: Please note the rules for commenting on the blog (first comments and linked posts end up in moderation, I release them every few hours, I rigorously delete SEO posts/SPAM).