What Memory Integrity Does and Why It Fails
Memory Integrity is a core Windows Security feature that uses virtualization-based security, or VBS, to help protect sensitive processes from malicious code.
When it cannot be turned on, the cause is usually an incompatible driver, disabled hardware virtualization, or an outdated Windows configuration.
If you are searching for how to fix memory integrity cannot be turned on, the right answer depends on whether Windows is blocking the feature because of software, firmware, or a platform setting.
The checks below cover the most common failure points in Windows 10 and Windows 11.
Check for incompatible drivers first
The most common reason Memory Integrity cannot be enabled is an old kernel-mode driver that Windows considers unsafe.
These drivers often come from printers, audio devices, RGB tools, VPN clients, virtual machine software, or older motherboard utilities.
How to identify blocked drivers
- Open Windows Security.
- Go to Device security and then Core isolation details.
- Look for any message that names one or more incompatible drivers.
If Windows lists a driver, note the file name, such as a .sys file.
Search for that file name in Settings or Device Manager, then remove or update the associated software.
What to do with the driver
- Update the device software from the hardware vendor.
- Uninstall the related app if it is no longer needed.
- Use Device Manager to uninstall the device and check Delete the driver software for this device if available.
After removing the conflicting driver, restart the PC and try enabling Memory Integrity again.
Confirm that virtualization is enabled in BIOS or UEFI
Memory Integrity depends on hardware virtualization features exposed by the CPU and enabled in firmware.
On Intel systems, this is usually Intel VT-x or Intel Virtualization Technology; on AMD systems, it is typically AMD-V or SVM.
How to check virtualization in Windows
- Press Ctrl + Shift + Esc to open Task Manager.
- Select the Performance tab.
- Choose CPU and look for Virtualization: Enabled.
If virtualization is disabled, enter the BIOS or UEFI setup during boot and enable the relevant setting.
Save changes, reboot, and check Windows Security again.
On some systems, Memory Integrity also depends on Secure Boot and TPM 2.0.
These are especially important on modern Windows 11 devices, where security features are more tightly integrated with firmware.
Make sure virtualization-based security components are available
Memory Integrity is part of Microsoft’s virtualization-based security stack.
If the platform does not meet the requirements, Windows may leave the toggle unavailable or immediately switch it back off.
Review these system requirements
- A 64-bit CPU with hardware-assisted virtualization
- Second Level Address Translation, often called SLAT
- UEFI firmware with Secure Boot support
- Windows 10 or Windows 11 with current security updates
Most PCs made in the last several years support these requirements, but some older desktops and laptops do not.
In that case, the feature may not be practical to enable without upgrading the hardware.
Update Windows and install pending security patches
Outdated Windows builds can cause Core isolation settings to behave unpredictably.
Microsoft regularly improves driver compatibility, virtualization support, and security enforcement through cumulative updates.
What to update
- Install the latest Windows Update patches.
- Check for optional updates in Advanced options.
- Update chipset, storage, and GPU drivers from the PC or motherboard vendor.
After updating, restart the device and revisit Windows Security > Device security > Core isolation details.
In many cases, a fresh driver or firmware update resolves the issue without further changes.
Remove virtualization conflicts from third-party software
Some applications install low-level drivers or virtualization hooks that interfere with Memory Integrity.
This is common with older antivirus products, sandboxing tools, disk encryption utilities, and virtual machine platforms.
Apps that can interfere
- Third-party antivirus and endpoint protection suites
- VirtualBox, VMware Workstation, and older Hyper-V workarounds
- System tuning or overclocking utilities
- Legacy printer, scanner, or USB controller software
If you recently installed software before the problem started, uninstall it temporarily and test Memory Integrity again.
If the feature works after removal, the app likely loaded an incompatible component.
Use Device Manager to clean up hidden or duplicate devices
Sometimes the active hardware is fine, but an old hidden device entry continues to load a problematic driver.
This happens after hardware replacements, Windows upgrades, or repeated docking and undocking on laptops.
Cleanup steps
- Open Device Manager.
- Use View > Show hidden devices.
- Look for grayed-out devices under Network adapters, Sound, video and game controllers, and System devices.
- Uninstall any obsolete hardware entries tied to old drivers.
Reboot after cleanup.
Windows may stop flagging the driver once the stale device entry is removed.
Check whether Group Policy or registry settings are blocking it
On managed PCs, an organization may enforce security policies that disable or control Memory Integrity.
This is common in enterprise environments using Microsoft Intune, Group Policy, or endpoint management tools.
Where restrictions can come from
- Group Policy settings for virtualization-based protection
- Microsoft Defender for Endpoint baselines
- Registry policies applied by IT
If this is a work device, contact IT instead of changing policy settings yourself.
On personal devices, review whether a system-tweaking utility or optimization tool added a policy that conflicts with Windows Security.
Try a clean boot to isolate the cause
A clean boot helps determine whether a background service or startup app is preventing Memory Integrity from staying enabled.
It is useful when no specific incompatible driver is shown, but the toggle still fails.
Clean boot checklist
- Open System Configuration.
- Hide Microsoft services, then disable the remaining services.
- Disable startup apps in Task Manager.
- Restart the PC and test Memory Integrity.
If it works in a clean boot state, re-enable items in batches until the problematic service or app is found.
Reset Windows Security settings if the interface is stuck
In rare cases, the Windows Security app or its related services may display stale status information.
The feature might actually be compatible, but the interface fails to update correctly after a driver change or update.
Practical reset actions
- Restart the computer.
- Run Windows Update again.
- Repair or reset the Windows Security app from Installed apps.
- Make sure the Security Center service is running automatically.
These steps often clear false warnings after system maintenance or device migrations.
When to assume the hardware is the limit
Some older systems simply do not support the requirements for Memory Integrity, especially if the CPU lacks SLAT or the firmware does not provide modern virtualization controls.
In that situation, there may be no software fix.
If your PC is older but still within the supported Windows hardware range, check the manufacturer support page for a BIOS update.
Firmware updates occasionally add or improve virtualization options that were missing at launch.
Quick checklist for fixing Memory Integrity
- Identify and remove incompatible drivers in Windows Security.
- Enable virtualization in BIOS or UEFI.
- Install Windows and driver updates.
- Remove conflicting third-party security or virtualization software.
- Clean up hidden legacy devices in Device Manager.
- Check for enterprise policies on managed PCs.
- Use a clean boot to isolate background conflicts.
By working through these checks in order, you can usually solve the problem without reinstalling Windows or replacing hardware.
The most effective path is to start with the driver report in Core isolation details, then verify firmware and update status before moving on to deeper troubleshooting.