Fix Memory Integrity Greyed Out in Windows 11

If the Memory Integrity toggle under Core Isolation is greyed out in Windows 11, it usually means your PC has an incompatible driver, a conflicting hypervisor, or a hardware/software limitation preventing the feature from being enabled. The fix is to identify and remove the blocking driver or setting, then restart and toggle it on again.

What Is Memory Integrity and Why Does It Matter?

Memory Integrity is a Windows 11 security feature that runs kernel-mode code inside a virtualized container, isolating it from the rest of the OS. It is part of Core Isolation, which uses hardware virtualization to create a secure memory region. When enabled, it prevents malicious code from injecting into high-integrity processes, which significantly reduces the risk of kernel-level attacks. Microsoft recommends keeping it on for all supported devices, and it is one of the requirements for the “Secured-core PC” designation.

Why Is the Toggle Greyed Out?

The most common reason is an incompatible driver. Windows blocks the toggle when it detects a driver that is not compatible with Memory Integrity. Other causes include:

Outdated or unsigned drivers (especially older graphics, network, or storage drivers).
Third-party antivirus or security software that uses kernel-mode hooks.
Virtualization-based security (VBS) already running but misconfigured.
Hardware that lacks virtualization support or has it disabled in BIOS/UEFI.
Windows 11 running in a virtual machine (VM) without nested virtualization.

How to Fix the Greyed Out Toggle

Follow these steps in order. Most users resolve the issue with the first or second step.

Check for incompatible drivers – Open Windows Security > Device security > Core Isolation details. If a driver is listed as incompatible, note its name. Go to Device Manager, find that driver, right-click it, and choose Update driver > Search automatically. If no update is found, go to the manufacturer’s website and download the latest driver manually.
Remove the incompatible driver – If updating doesn’t work, uninstall the driver. In Device Manager, right-click the device and select Uninstall device. Check the box “Delete the driver software for this device” if available, then restart. Windows will reinstall a generic driver, which is usually compatible.
Enable virtualization in BIOS/UEFI – Restart your PC and enter BIOS/UEFI (usually by pressing F2, F10, Del, or Esc during boot). Look for a setting named Intel VT-x, AMD-V, or SVM Mode and make sure it is enabled. Save and exit.
Disable conflicting hypervisor – If you use Hyper-V, Windows Sandbox, or Windows Subsystem for Linux (WSL), they may conflict. Temporarily disable them via Control Panel > Programs > Turn Windows features on or off. Uncheck Hyper-V, Windows Hypervisor Platform, and Windows Subsystem for Linux, then restart and try enabling Memory Integrity again.
Run the Memory Integrity diagnostic – Open Windows Security > Device security > Security processor > Security processor details. If it shows an error, run Windows Memory Diagnostic (type “Windows Memory Diagnostic” in Start) and restart to check for hardware issues.
Clean boot – Use msconfig to perform a clean boot (disable all non-Microsoft services and startup items). If the toggle becomes available, re-enable services one by one to find the culprit.

What to Do If the Toggle Still Won’t Enable

If none of the above works, the problem may be a driver that Windows doesn’t list as incompatible but still blocks the feature. Use the Get-CimInstance PowerShell command to list all drivers and their statuses. Look for any driver with a date older than 2019 or a publisher that isn’t Microsoft. Update or remove those. Also check if your PC meets the hardware requirements: Memory Integrity requires a 64-bit CPU with virtualization extensions and SLAT (Second Level Address Translation). Most CPUs from the last 10 years support this, but it must be enabled in firmware.

Common Misconceptions and Pitfalls

Many users think that disabling Memory Integrity is the only solution, but that leaves your system vulnerable. Another misconception is that the greyed-out toggle means the feature is already on. It is not; greyed out means it is off and cannot be changed. Also, some users believe that updating Windows will fix it automatically, but driver updates are often separate. Finally, do not force-enable it via registry edits or third-party tools; this can cause boot failures or system instability. Stick to the official methods.

Frequently Asked Questions

Q: Can I enable Memory Integrity if my CPU doesn’t support virtualization?
A: No. Virtualization must be supported and enabled in BIOS/UEFI. If your CPU lacks it, the toggle will remain greyed out. Check your CPU model online to confirm.

Q: Will enabling Memory Integrity slow down my PC?
A: There is a slight performance impact, typically 1-5% in gaming and heavy workloads, but for most users it’s unnoticeable. The security benefit outweighs the cost.

Q: Why does Windows say “Incompatible driver” but doesn’t tell me which one?
A: Windows lists the driver in the Core Isolation details page, but sometimes it’s vague. Use the PowerShell command Get-CimInstance -ClassName Win32_DeviceDriver to see all drivers and their dates. Look for older ones or those from unknown publishers.

Q: I use a virtual machine. Can I enable Memory Integrity inside the VM?
A: Yes, but you need nested virtualization enabled on the host and the VM must have virtualization extensions exposed. If not, the toggle will be greyed out.

Q: What if I uninstall the incompatible driver and my hardware stops working?
A: Windows will usually install a generic driver that works for basic functionality. If not, reinstall the manufacturer’s driver after enabling Memory Integrity. If the driver is truly incompatible, you may need to wait for an updated version from the manufacturer.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →