Quick fix: Open Windows Security → Device security → Core isolation → Memory integrity. If toggle is off with a warning, click Review incompatible drivers. The list shows driver names and publishers. Uninstall or update each: Device Manager → find device → Update driver or Uninstall device. After all are resolved, toggle Memory Integrity on. Restart.

Memory Integrity (HVCI — Hypervisor-protected Code Integrity) blocks drivers from injecting malicious code into kernel memory. It uses virtualization. Some old or vendor-specific drivers don’t cooperate with this protection. Windows lists them, and you must update or remove them.

Symptom: Memory Integrity off in Windows Security because of incompatible drivers; want to enable security.
Affects: Windows 11 (and Windows 10).
Fix time: ~30 minutes (depending on driver count).

What causes this

Memory Integrity requires all kernel-mode drivers to be HVCI-compatible. Drivers must not write to executable memory in ways that bypass code integrity checks. Old drivers (especially anti-cheat drivers, virtualization software drivers, VPN drivers, RGB control software) often fail this check. Windows refuses to enable Memory Integrity until those drivers are removed or updated.

Method 1: Identify and remove incompatible drivers

The standard route.

Open Windows Security.
Click Device security → Core isolation details.
Under Memory integrity: click Review incompatible drivers.
List shows drivers with: name, publisher, .sys file path. Common culprits: VBoxDrv.sys (VirtualBox), InsightCloud.sys (ZoneAlarm), VanguardDriver.sys (anti-cheat), RGB drivers (Logitech G Hub, etc.).
For each driver, identify the parent software/device. Search the .sys file name online if needed.
To remove software: Settings → Apps → Installed apps → find the app → Uninstall.
To uninstall a driver directly: Device Manager → right-click device → Uninstall device (tick Delete the driver software for this device if option appears).
Restart PC.
Re-check Memory Integrity. Toggle on. If still warning: continue removing or updating remaining drivers.

This is the standard fix.

Method 2: Update drivers to HVCI-compatible versions

For when you need the software.

For specific drivers: visit the manufacturer’s site. Most major vendors have updated drivers to be HVCI-compatible.
Examples:
- VirtualBox: 7.0+ is HVCI-compatible.
- Logitech G Hub: latest version uses compatible drivers.
- RGB software (Razer Synapse, Corsair iCUE, NZXT CAM): recent versions updated.
- VPN clients (ExpressVPN, NordVPN): recent versions compatible.
Download and install the latest version. Reboot.
Re-check Memory Integrity warning. If driver is now compatible, it disappears from the list.
For drivers with no compatible update: contact vendor for status. Or use alternative software with HVCI support.
For internal Windows drivers from device manufacturers (HP, Dell printer drivers): use Microsoft Update or Device Manager Update driver.

This avoids losing functionality.

Method 3: Use PowerShell to identify all problem drivers in detail

For deeper diagnosis.

Open PowerShell (Admin).

Get all drivers with their status:

Get-WindowsDriver -Online -All | Format-Table OriginalFileName, ProviderName, Version, Date

Run HVCI check with built-in tool:

dism /online /get-features | findstr /i hyper

For each suspect driver, get details:
```
Get-WindowsDriver -Online -Driver oem23.inf
```
where oem23.inf is the driver’s INF file.

Remove driver if obsolete:

pnputil /delete-driver oem23.inf /uninstall

For DriverView (NirSoft, free): GUI alternative shows all kernel-mode drivers with vendor info.
For looking at specific drivers’ HVCI compatibility: download HVCI Compatibility Checker from github.com. It runs against a specific .sys file.

This is for thorough diagnosis.

How to verify the fix worked

Windows Security → Device security → Core isolation: Memory integrity is On.
No incompatible drivers warning.
System boots normally with HVCI active.
For confirmation: msinfo32 → under System Summary, Virtualization-based security → Running — Hypervisor enforced Code Integrity.

If none of these work

If Memory Integrity won’t enable: BIOS / UEFI virtualization disabled: enable Intel VT-x / AMD-V and SVM in BIOS. For older CPUs without SLAT / VT-x: Memory Integrity not supported on hardware. For old graphics driver: very old AMD/Nvidia drivers fail. Update to current. For OEM PC with vendor utility drivers: Acer Care, Dell SupportAssist, HP utilities. Update or uninstall vendor utility. For chronic driver after update: vendor hasn’t actually fixed. Accept Memory Integrity off, or switch hardware. For gaming PCs with anti-cheat: some anti-cheats (Easy Anti-Cheat, Vanguard) need disabling HVCI. Accept the trade-off or skip those games.

Bottom line: Windows Security → Device security → Core isolation → Review incompatible drivers. Update via manufacturer or uninstall via Device Manager. Re-enable Memory Integrity after.