Memory integrity (also called Hypervisor-protected Code Integrity, or HVCI) can’t be turned on in Windows Security when a device driver or app is incompatible, virtualization is disabled, or the firmware doesn’t support it. The fix usually involves updating or removing the incompatible driver, enabling virtualization in BIOS, or checking if your CPU meets the requirements. Below is a detailed guide to diagnosing and resolving each cause.
What Is Memory Integrity and Why Does It Matter?
Memory integrity is a Windows security feature that uses hardware virtualization to run the kernel in an isolated memory region. It prevents malicious code from injecting into high-integrity processes, which is a common technique used by rootkits and advanced malware. When enabled, the hypervisor checks code before it runs, blocking unsigned or vulnerable drivers. It’s part of Core Isolation in Windows Security, and it’s on by default on many newer systems. If it’s off, your PC is more exposed to kernel-level attacks, so it’s worth fixing if you can.
Why Can’t You Turn It On? The Main Causes
There are several reasons the toggle might be greyed out, or Windows shows an error when you try to enable it:
- Incompatible drivers: The most common cause. A driver on your system is not compatible with HVCI. Windows lists the offending driver in the Windows Security app under “Review incompatible drivers.”
- Virtualization disabled in BIOS/UEFI: Memory integrity relies on Virtualization-Based Security (VBS). If VT-x (Intel) or SVM (AMD) is off, the feature can’t start.
- Outdated BIOS or firmware: Older firmware may not expose the necessary virtualization extensions correctly.
- CPU doesn’t support required features: Memory integrity needs a 64-bit CPU with SLAT (Second Level Address Translation) and, ideally, Mode-Based Execution Control (MBEC) for full performance. Without MBEC, Windows may block the toggle because it would cause severe slowdowns.
- Windows version or edition: Some older Windows 10 builds or Home editions may have limited support, though it’s generally available on all 64-bit versions.
How to Diagnose the Exact Problem
Before changing settings, find out what’s blocking the feature. Follow these steps:
- Open Windows Security > Device security > Core isolation details.
- Look for a message under “Memory integrity” that says “Incompatible drivers” or “This device doesn’t support memory integrity.”
- If it says incompatible drivers, click “Review incompatible drivers” to see the list. Note the driver names and versions.
- Open System Information (type msinfo32 in Start). Under “System Summary,” check “Virtualization-based Security” and “Hyper-V” to see if VBS is running.
- Press Win+R, type msinfo32, and look at the “Virtualization” section. It should say “Hyper-V requirements: A hypervisor has been detected.” If not, virtualization is off.
How to Fix It: Step-by-Step Solutions
1. Update or Remove Incompatible Drivers
If you see a list of incompatible drivers, you have two options:
- Update the driver: Go to the manufacturer’s website, find the latest version for your hardware, and install it. Many older drivers—like those for graphics cards, network adapters, or storage controllers—have been updated to be HVCI-compatible.
- Remove the driver: If no update exists, uninstall the device driver via Device Manager. For example, if it’s an old Wi-Fi adapter, you might replace it or use Windows’ built-in driver. Be careful: removing a driver for a critical component (like a storage controller) can make your system unstable. Only remove non-essential drivers.
After updating or removing, restart your PC and try to enable memory integrity again.
2. Enable Virtualization in BIOS/UEFI
If virtualization is off, you need to turn it on:
- Restart your PC and press the key to enter BIOS/UEFI (usually Del, F2, F10, or Esc).
- Look for a setting called “Intel Virtualization Technology” (Intel) or “SVM Mode” (AMD). It might be under “Advanced,” “CPU Configuration,” or “Security.”
- Set it to Enabled.
- Save and exit. Boot into Windows and check if the toggle is now available.
Note: Some systems also have a separate setting for “VT-d” (Intel) or “IOMMU” (AMD). Enabling that can help with VBS, but it’s not always required.
3. Update BIOS/UEFI
If virtualization is already enabled but the toggle is still greyed out, a BIOS update might add the missing support. Check your motherboard or PC manufacturer’s website for a newer BIOS version. Follow their instructions exactly—a failed BIOS update can brick your system.
4. Check for MBEC (Mode-Based Execution Control)
Windows 10 and 11 prefer CPUs that support MBEC (also called “Intel Mode-Based Execution Control” or “AMD Rapid Virtualization Indexing”). If your CPU doesn’t have it, memory integrity will work but with a significant performance hit, so Windows may block it. To check if your CPU supports MBEC, you can use the systeminfo command or tools like Coreinfo (from Microsoft Sysinternals). If it doesn’t support MBEC, you might still be able to force it on via registry, but that’s not recommended for everyday use due to slowdowns.
Common Problems and Misconceptions
- “I removed the driver but the message still appears.” Sometimes the driver is in the Windows Driver Store. Use Device Manager to uninstall the device and check “Delete the driver software for this device.” Restart.
- “My PC is a VM and I can’t enable it.” You need nested virtualization enabled in the hypervisor (like Hyper-V or VMware). This is often disabled by default.
- “I enabled virtualization but the toggle is still off.” Windows may have disabled VBS due to a policy. Check Group Policy: Computer Configuration > Administrative Templates > System > Device Guard. If “Turn On Virtualization Based Security” is set to Disabled, change it to “Enabled with UEFI lock” or “Enabled.”
- “Memory integrity is off by default on my PC.” That’s normal on some systems, especially if they were upgraded from Windows 10. It doesn’t mean something is wrong.
What to Do If Nothing Works
If you’ve tried all the above and the toggle still won’t turn on, there are a few last-resort options:
- Use the Registry (advanced): You can force-enable memory integrity via the registry, but this is risky and can cause boot failures if a driver is truly incompatible. Only do this if you’re comfortable with recovery tools.
- Clean install Windows: If your system is cluttered with old drivers, a fresh install might clear the incompatible driver list. Back up your data first.
- Accept it’s not possible: Some older PCs simply lack the hardware support. In that case, rely on other security features like SmartScreen, Windows Defender, and keeping your system updated.
Frequently Asked Questions
Is it safe to force memory integrity on via registry?
It’s not recommended. If an incompatible driver is present, forcing HVCI on can cause blue screens or boot loops. The registry method exists mainly for enterprise testing. Only use it if you know the driver issue is resolved and you have a backup.
Does memory integrity affect gaming performance?
On CPUs with MBEC, the performance impact is minimal (usually under 5%). On older CPUs without MBEC, it can be significant—up to 20-30% in some workloads. That’s why Windows blocks it on those systems.
Why does Windows say “Incompatible drivers” but doesn’t list them?
Sometimes the driver list is empty because the driver was already removed, but the system hasn’t refreshed. Restart your PC and check again. If it persists, use the Event Viewer (under System logs) to look for HVCI-related errors.
Can I enable memory integrity on Windows 10 Home?
Yes, memory integrity is available on all 64-bit editions of Windows 10 and 11, including Home. The toggle is in the same place. If it’s greyed out, it’s a hardware or driver issue, not an edition limitation.
Do I need to disable Hyper-V to use memory integrity?
No, memory integrity actually uses Hyper-V’s hypervisor. Having Hyper-V enabled is fine. In fact, if you have Windows Sandbox or WSL2, they rely on the same virtualization stack, and memory integrity works alongside them.
What’s the difference between memory integrity and Secure Boot?
Secure Boot ensures that only trusted firmware and bootloaders run during startup. Memory integrity protects the kernel at runtime. They’re complementary; you should have both enabled if possible.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Car Trends Making Cars Worse: 7 Downsides
- Nostalgic Classic Games Revamped on G2A?
- Nvidia RTX 4000 Super GPUs: Full Specs & Buying Guide
- Photoshop vs Lightroom AI Features Compared
- DNF vs DNF5: Which Package Manager?
- Selfie Stick Buying Reasons: 7 Real Benefits