What to Do When Windows Security Isolation Fails to Start

Checking Your Security Settings

Start by checking the exact status of Core Isolation and Memory integrity in Windows Security. This shows whether the feature is off or whether Windows is actively blocking it, and the warning text often names the cause. These steps apply to current Windows 11, and the screens are the same on Home and Pro.

First, check the hardware requirements. Memory integrity needs a 64-bit processor with virtualization support and Second Level Address Translation (SLAT), a CPU feature that helps virtual machines manage memory. On many PCs it also relies on Secure Boot or a TPM (Trusted Platform Module, the security chip on the motherboard) being enabled. If the PC does not meet these requirements, the feature may stay unavailable even after you follow every step below.

1. Click the Start button on your taskbar🖥️, type Windows Security, and press Enter. The Windows Security dashboard opens.
2. Click Device security on the left side of the window. The Device security page opens, with a list of security features for your PC.

   

3. Find the section titled Core isolation and click the Core isolation details link. If you do not see this section, your device may not support it, or virtualization is off in the firmware (see the BIOS section below).
4. Look at the toggle switch for Memory integrity. Note whether it is On or Off, and whether any text appears under it.

That’s it for the status check. You now know whether Memory integrity is on, off or blocked, and you have any warning text in front of you.

If the Memory integrity switch is off and will not stay on, or if an error message appears right underneath it, you have confirmed the failure. If you turn the switch on and Windows reports that something is incompatible, it usually shows a Review incompatible drivers link.

Finding and Removing Incompatible Drivers

Incompatible drivers are the most common reason Memory integrity will not turn on. They are usually outdated files from printers, graphics cards or storage tools that do not meet modern memory protection rules. Updating or removing them clears the block.

Your Windows Security screen often lists the exact problem driver. Common examples include old security software, storage utilities such as Western Digital tools, and outdated printer software. On Windows 11 24H2 and later, the incompatible drivers list also shows the driver file names. You can copy those names into the pnputil steps in the next section.

Before you download anything by hand, try Windows Update. It sometimes carries a newer version of the driver. Open Settings › Windows Update, click Check for updates, and install what it offers. Then look under Settings › Windows Update › Advanced options › Optional updates for any driver updates.

To find and update these drivers:

1. Open the Core isolation details screen in Windows Security, using the steps from the previous section.

   

2. Try to turn on Memory integrity. If Windows finds a problem, click the Review incompatible drivers link or look for the list of problem files. You should now see a list of driver names.
3. Write down the name of each driver causing the issue. A screenshot or a photo of the screen works too.
4. Go to the official website of the hardware manufacturer (such as Western Digital, HP, or your printer brand) and download the⬇️ newest version of their software or driver. If the device is old and no newer driver exists, uninstalling the software or the device is often the only fix.
5. Install the💿 updated driver, then restart your🔄 computer.
6. Return to Core isolation details and switch Memory integrity to On.

That’s it for the driver update. Updating a driver often clears the block immediately, and Memory integrity then turns on. If the same driver is still listed after the update, move on to the next section.

How to Force Uninstall Stubborn Problem Drivers

Sometimes a driver stays on the system after you uninstall the program that installed it. These leftovers keep blocking Memory integrity, and standard updates will not remove them. In that case you remove the driver package by hand. You need administrator rights for this.

Be careful: the force option removes a driver package even if Windows is still using it. Remove only the driver you identified as the problem. If it belongs to a device you still use, that device may stop working until you reinstall its software.

Create a restore point before you delete anything. A restore point is a saved snapshot of your system files and settings that you can roll back to. This works on both Home and Pro.

1. Click the Start button, type Create a restore point, and press Enter. The System Properties window opens on the System Protection tab.
2. Under Protection Settings, select your Windows drive, which is usually C:. If protection shows as Off, click Configure, choose Turn on system protection, and click OK.
3. Click the Create button, type a short description such as Before removing driver, and click Create again.
4. Wait for the message that says the restore point was created successfully, then click Close.

You should now have a restore point to fall back on. To roll back later, open System Properties again and click System Restore.

Now remove the driver package:

1. Right-click the Start button and select Terminal (Admin) (or Command Prompt (Admin) if that is what your menu shows). Click Yes if User Account Control asks for permission. This step requires administrator privileges.
2. Type the following command to list the third-party drivers on your system, then press Enter: pnputil /enum-drivers
3. Scroll through the list and find the published name of the problem driver. It looks like oem12.inf. Match it to the driver name you wrote down earlier, using the provider and original name shown in the list.
4. Once you identify the correct file name, type the following command and press Enter, replacing oem12.inf with your actual driver file name: pnputil /delete-driver oem12.inf /uninstall /force
5. Check the message that appears. It should confirm the driver package was deleted. If it says the driver is in use, close the related software or restart and try again.
6. Restart your🔄 computer and try turning on Memory integrity again in Windows Security.

That’s it for the manual removal. The leftover driver package is now gone from the system, so it can no longer block Memory integrity. If the removal caused problems, use the restore point you created.

Checking Virtualization Settings in Your Computer BIOS

Core Isolation needs hardware virtualization on the processor. If it is disabled in your BIOS or UEFI firmware, Memory integrity cannot start. Many PCs ship with it on, but some boards, especially older or custom-built ones, have it off. Menu names vary by manufacturer, so treat the names below as a guide.

To check and enable virtualization:

1. Save your work and restart your🔄 computer.
2. As the computer turns back on, press the key required to enter the BIOS or UEFI settings. This key is usually F2, F12, Del, or Esc, depending on your computer brand. If you miss the moment, restart and try again. The key is often shown briefly on the startup logo screen.
3. Look through the menus for a setting named Intel Virtualization Technology, Intel VT-x, or AMD-V. It is sometimes listed under CPU Configuration or Security. Some AMD boards call it SVM Mode.
4. Change the setting to Enabled.
5. Save your changes and exit the BIOS (usually by pressing F10). Your computer restarts normally into Windows.

That’s it for the firmware change. Hardware virtualization is now enabled, which Memory integrity needs in order to start.

If you cannot find any virtualization setting, check your manufacturer’s support page for your exact model. Some machines hide it, and a few older processors do not support it at all. To undo the change, go back into the BIOS and set it to Disabled.

Once you are back in Windows, open Windows Security, go to Device security and Core isolation details, and try turning on Memory integrity again. If it now switches on, restart when prompted to finish the change. If it still will not stay on, check that Secure Boot or the TPM is enabled in the same firmware menus, since many PCs need one of them.

Advanced Fix: Using Windows Features for Virtualization

Windows has optional features that support virtualization and the security layers built on it. If these are turned off or damaged, Core Isolation can fail. You can check them in the classic Windows features dialog. This works on both Home and Pro editions of Windows 11.

1. Click the Start button, type Turn Windows features on or off, and press Enter. The Windows Features window opens.
2. Scroll down and look for Virtual Machine Platform.
3. Check the box next to Virtual Machine Platform.
4. Also look for Windows Hypervisor Platform and check its box if it is available.
5. Click the OK button. Windows searches for files and applies the changes, and you will see a progress message.
6. Restart your🔄 computer when prompted.

That’s it for the Windows features. The virtualization components are now switched on, and the restart finishes the change.

The full Hyper-V feature is not needed for this fix, and it is only offered on Pro and higher editions. If the boxes are already checked, leave them as they are and move on. To undo this change, clear the boxes and restart.

These platform files give Windows the tools it needs to run security isolation properly. Isolation creates a protected area in memory for vital system programs. If the required components are missing or turned off, isolation stops working, and your system loses that layer of protection against malicious software.

Unique Expert Tip: Fixing Corrupted Security Policies with DISM

Damaged system files can stop Windows Security isolation from starting, often after a failed update or a power outage. Windows includes built-in repair commands that scan the system and restore the files it needs. Administrator rights are required to run them.

1. Right-click the Start button and select Terminal (Admin) (or Command Prompt (Admin)). This step requires administrator privileges.
2. Type the following command and press Enter: DISM.exe /Online /Cleanup-image /Restorehealth
3. Wait for the process to reach 100 percent. This may take a few minutes, because it can download clean system files from Microsoft servers. Make sure you are online, and do not close the window even if the progress bar seems stuck for a while.
4. Next, type the following command and press Enter: sfc /scannow
5. Let the system scan finish. If it finds corrupted files, it repairs them automatically, and a message at the end tells you what it found.
6. Restart your🔄 computer and check your security settings.

That’s it for the repair. Windows has now scanned the system and replaced any damaged files it found, so isolation has a clean base to start from.

Unique Expert Tip: Addressing Registry Conflicts Without Direct Edits

If a bad configuration is the problem, there is no need to edit the registry by hand. A mistake there can cause bigger problems than the one you started with. Instead, reset the security policies to their defaults using a built-in administrative command in PowerShell.

Back up first, because the reset has no undo button. The simplest safety net is a restore point. Follow the restore point steps in the driver removal section above, and create a new one now.

If you want a copy of the current policy as well, use the /export option of the secedit tool to save it to a file. Keep that file somewhere safe. It records what your settings were before the reset.

1. Click the Start button, type PowerShell, right-click it, and choose Run as administrator. This step requires administrator privileges.
2. Type the following command to reset security policies to their default state and press Enter: secedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verbose
3. Wait for the command to finish running. It reapplies the original default security settings across your operating system, and you will see the prompt return when it is done.
4. Restart your🔄 computer to apply the fresh security baseline.
5. Open Windows Security and try turning on Memory integrity one more time.

That’s it for the policy reset. Your security policies are now back at their defaults, and Memory integrity has a clean configuration to work with. If the reset caused trouble, restore the restore point you created.

Summary

To fix Windows Security isolation and Memory integrity failures, work through the causes in order: check your settings, remove incompatible drivers, enable hardware virtualization in the BIOS, turn on the virtual machine features, and run the system repair commands. Restart and retest Memory integrity after each fix, so you know which step solved it. If it still will not turn on, the driver list in Core isolation details is the best place to look next.