Memory integrity is off because of incompatible drivers: how to fix it

What the warning means

Memory integrity, also called Hypervisor-protected Code Integrity (HVCI), is part of Core isolation. It checks drivers inside an isolated virtual environment before Windows lets them run, which makes it much harder for malware to load code into the Windows kernel. Since Windows 11 22H2, Windows Security shows Memory integrity is off. Your device may be vulnerable. when the feature is off.

If you try to switch it on and get Resolve any driver incompatibilities and scan again, one or more installed drivers don’t meet its rules. Microsoft explains that turning memory integrity on would block those drivers, which could break whatever relies on them, so Windows keeps it off instead. Microsoft is also turning memory integrity on automatically for more eligible PCs in updates from October 2026, so the warning may be new on a PC that’s had it off for years.

Memory integrity also needs hardware virtualization switched on in your UEFI/BIOS. If the toggle is missing or greyed out rather than blocked by drivers, check that first.

Step 1: Find the driver and what it belongs to

1. Open Windows Security, select Device security and then Core isolation details.
2. Select Review incompatible drivers. Each entry shows a file name such as wdcsam64.sys; expand it to see the Published Name (for example oem42.inf) and the original INF file name.
3. Note every entry. Search the file name together with the word “driver” to find out which product installed it.

Users commonly report entries like these. The list varies by PC, so treat it as a starting point:

File name	Usually comes from
wdcsam64.sys, wdcsam64_prewin8.sys	Western Digital drive or backup software
iqvw64e.sys	Intel network diagnostics or driver update tools
xhunter1.sys	an anti-cheat used by some online games
PxHlpa64.sys	older CD/DVD burning software
wacomhidfilter.sys	older Wacom tablet drivers
Old graphics, audio or chipset drivers	drivers carried over from an earlier PC or Windows install

Older RGB lighting, fan control and overclocking tools are frequently reported too. If an entry appeared after moving to a new PC, it may be a driver brought across from the old one.

Step 2: Update the driver

This is Microsoft’s first recommendation. Run Settings > Windows Update, then check Advanced options > Optional updates > Driver updates for newer versions. If nothing appears, download the current driver or app from the hardware maker’s support site. After updating, restart and select Scan again under Review incompatible drivers. If Windows Update keeps swapping your graphics driver for an older one, see how to stop Windows 11 from updating your graphics driver.

Step 3: Remove the app or device that installed it

If no compatible version exists, Microsoft’s other option is to remove the device or app that uses the driver:

• In Settings > Apps > Installed apps, uninstall the program the driver came with, such as an old backup, burning or RGB utility. Some drivers show up there as a Windows Driver Package entry.
• For hardware you no longer use, open Device Manager, choose View > Show hidden devices, right-click the device and select Uninstall device. Tick the option to remove the driver if it’s offered.
• Restart and scan again.

Step 4: Remove a leftover driver package

Sometimes the program is long gone but its driver package stays in Windows’ driver store. Microsoft’s own position is that it doesn’t recommend deleting drivers to restore memory integrity, so treat this as an advanced step. Only use it for a driver you’ve identified and are sure you don’t need, never for storage, chipset or graphics drivers your PC is using.

1. Create a restore point first: search for Create a restore point, select your system drive and choose Create.
2. Open Terminal or Command Prompt as administrator and run pnputil /enum-drivers to confirm the Published Name matches the entry you noted.
3. Remove it with the command below, using your own Published Name, then restart.

pnputil /delete-driver oem42.inf /uninstall

If pnputil says One or more devices are presently installed using the specified INF, a device is still using that driver. Stop there and go back to Step 3. Adding /force removes it anyway and can leave that hardware without a working driver.

Advanced users can confirm which drivers memory integrity actually blocks in Event Viewer under Applications and Services Logs > Microsoft > Windows > CodeIntegrity > Operational, where Microsoft lists Event ID 3087 for this.

When to leave memory integrity off

If the driver belongs to hardware you rely on and the maker has no compatible version, leaving memory integrity off is a valid choice. Your PC still has Microsoft Defender, Secure Boot and the other protections; see how to scan for malware if you want to check it. Microsoft notes some effect on performance, mostly on older processors, and in 2022 it told gamers they could turn the feature off while playing, with a warning that the device may be more vulnerable. Some anti-cheat systems now ask for it to be on instead, so check your game’s requirements.

The Microsoft Vulnerable Driver Blocklist setting just below the toggle stays on by default and can’t be changed while memory integrity is on. Don’t use registry tweaks to force memory integrity on while incompatible drivers remain installed.

If Windows won’t start after turning it on

Microsoft warns that an incompatible driver can, rarely, cause a blue screen at startup once memory integrity is on. Windows may switch it off by itself after repeated failed boots. If it doesn’t, start the Windows Recovery Environment (hold Shift while selecting Restart, or let Windows fail to boot twice), open Troubleshoot > Advanced options > Command Prompt and run:

reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity" /v "Enabled" /t REG_DWORD /d 0 /f

Restart, then deal with the driver before trying again. If your drive is protected by BitLocker, have your recovery key ready before using recovery tools or changing firmware settings. If Windows Security itself won’t open, see Windows Security not opening.

Related guides

• Windows Security not opening in Windows 11? 7 fixes that work
• How to stop Windows 11 from updating your graphics driver
• How to Scan for Malware on Windows 11 and 10 (Free, Built-In Tools)
• Secure Boot certificates expired in 2026: how to check and update your PC
• Wi-Fi or VPN stopped connecting after the October 2026 Windows update: the NTLMv1 and MS-CHAPv2 change

Official sources

• Device security in the Windows Security app: Core isolation (Microsoft Support)
• Why do incompatible drivers prevent using memory integrity? (Microsoft Support)
• Enable virtualization-based protection of code integrity (Microsoft Learn)