Why Memory Integrity Setting Cannot Be Turned On in Windows 11

Quick fix: Memory integrity (Core Isolation feature) won’t enable when incompatible drivers are loaded. Open Windows Security → Device security → Core isolation → Memory integrity. Click Review incompatible drivers. Update or uninstall each. Reboot. Toggle Memory integrity on.

Windows Security shows “Memory integrity is off. Your device may be vulnerable.” You toggle it on. Toggle reverts to Off. Driver compatibility list shows specific old drivers blocking it. The fix: update/uninstall those drivers.

What causes this

Memory integrity (HVCI = Hypervisor-protected Code Integrity) requires that all loaded kernel-mode drivers be signed with HVCI-compatible signatures. Older drivers without modern signing block HVCI from enabling. Common offenders: old Realtek audio drivers, old NVIDIA GPU drivers (pre-2018), virtualization drivers (VMware, VirtualBox older versions), some game anti-cheat drivers.

Method 1: Identify and update incompatible drivers

The standard fix.

1. Open Windows Security → Device security → Core isolation details.
2. Under Memory integrity, if toggle is off, look for “Review incompatible drivers” link. Click.
3. List shows each incompatible driver: file name, publisher, last loaded date.
4. For each: update if newer version exists. For example, if it’s Realtek HD Audio — visit Realtek/motherboard manufacturer site for latest.
5. For drivers that can’t be updated: uninstall via Device Manager → right-click device → Uninstall device (tick “Delete driver software”).
6. Reboot.
7. Repeat checking incompatible drivers list. As you update each, list shrinks.
8. Once list is empty: toggle Memory integrity on. Should succeed.

This is the standard fix.

Method 2: Manually identify drivers via PowerShell

For when the UI list isn’t accessible or detailed.

1. Open Terminal (Admin). Run:

   Get-WindowsDriver -Online -All | Where-Object { $_.Date -lt "2018-01-01" } | Format-Table OriginalFileName, ProviderName, Date

   Lists drivers older than 2018; many are HVCI-incompatible.

2. Run hardware test for HVCI compatibility:

   Get-WinEvent -LogName "Microsoft-Windows-HypervisorVMM-Operational" -MaxEvents 50

   Shows HVCI-related events.

3. For more detail: Driver Verifier. Run verifier from Run dialog. Pick “Create custom settings” → check “Concurrency stress tests” and “HVCI compatibility.” Verifier reports incompatible drivers.
4. Note: Driver Verifier slows the system; turn off after testing.
5. For specific known issues: outdated NVIDIA drivers, MSI Mystic Light, old game anti-cheat drivers are common HVCI blockers.

This is the diagnostic path.

Method 3: Use compatibility-mode drivers or accept Memory integrity off

For drivers without HVCI-compatible versions.

1. If a critical app/driver lacks HVCI-compatible signing: vendor must release update. Contact vendor.
2. For old hardware drivers (VR headsets, MIDI controllers, capture cards): vendor may have abandoned support. Either accept HVCI off or replace hardware.
3. For Memory integrity vs. compatibility trade-off: HVCI improves kernel security significantly. Most users should enable. Gaming or specialized hardware users may need it off.
4. To suppress the warning without enabling: Windows Security → Notification settings → toggle off Security notifications. Reduces nag.
5. For monitored compliance: HVCI status reports in Defender ATP / Intune. If your environment requires HVCI, must resolve all incompatible drivers.
6. For Hyper-V or virtualization software conflict: ensure VMware/VirtualBox is latest version. They’ve been updated to coexist with HVCI.

This handles the can’t-update case.

How to verify the fix worked

• Windows Security → Device security → Core isolation → Memory integrity: On.
• Yellow warning banner in Windows Security clears.
• Run Get-CimInstance -ClassName Win32_DeviceGuard | Select-Object SecurityServicesRunning. Includes value 1 (Credential Guard) and 2 (HVCI).

If none of these work

If toggle won’t enable despite no incompatible drivers shown: BIOS settings: enable Virtualization (Intel VT-x or AMD-V). HVCI requires this. Hyper-V conflict: HVCI may not enable while Hyper-V is in specific states. Disable Hyper-V temporarily: Optional Features → untick Hyper-V Platform. Reboot. Enable HVCI. Then re-enable Hyper-V. For ARM PCs: HVCI behavior differs on ARM. Verify Surface Pro X or similar has HVCI option. For Windows 11 with certain antivirus: third-party AV may have HVCI-incompatible kernel hooks. Try with Defender only; uninstall third-party AV.

Bottom line: Memory integrity requires HVCI-compatible drivers. Windows Security shows incompatible list — update or uninstall each. Reboot. Enable Memory integrity.