Symptoms
If you are trying to update to Windows 10, version 2004, you might encounter an update compatibility hold and receive the message, "Your PC settings need to be adjusted before upgrading to the latest version of Windows 10. Turn off memory integrity protection to continue."
Cause
An incompatibility has been found with certain display drivers and Windows 10, version 2004 when memory integrity protection is enabled.
To safeguard your update experience, we have applied a compatibility hold on these devices from installing or being offered Windows 10, version 2004.
Workaround
To update to Windows 10, version 2004 with Memory integrity enabled, you will need to update your display drivers. Updated drivers might be available on Windows Update. See Update Windows 10 for more information. If you are still receiving the safeguard hold, you will need to check with your device manufacturer for updated display drivers (sometimes called video drivers).
If you are unable to update your display drivers, you will need to turn Memory integrity off to be able to update to Windows 10, version 2004.
-
Go to the Core isolation page in Windows Security.
-
Turn the Memory integrity setting Off. You will need to restart your computer for the changes to take effect.
Note: Memory integrity is a security feature that is off by default. If it is enabled on your device, it was enabled by a user or by an IT administrator. These factors should be considered when disabling it. If it was enabled by an IT administrator in your organization, you may not have permission to disable it.
Next steps
After investigation, there is no secure way to resolve this issue within Windows and will require updated drivers. If updated drivers are not available from your device manufacturer (OEM), then you will need to use the above workaround to update to a later version of Windows 10.
Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until you have installed newer drivers or have performed the workaround above.
