What To Do When Windows Security Isolation Fails To Start
Core Isolation is a built-in Windows security feature that creates a safe, virtual memory zone to protect core system processes from harmful software. Inside this system, a setting called Memory Integrity blocks unverified apps and bad drivers from messing with your computer memory.
When Windows Security Isolation fails to start, it usually means an older hardware driver or a leftover piece of software on your PC is not compatible with virtual security. Windows turns the feature off to keep your system from crashing or freezing.
When Windows Security isolation fails to start, it is usually caused by outdated or incompatible hardware drivers blocking Memory Integrity. To fix this, open Windows Security, go to Device security, click Core isolation details, check for any listed problem drivers, and update that software from the manufacturer website.
Checking Your Security Settings
Checking your security settings in Windows Security lets you see the exact status of your Core Isolation and Memory Integrity features. Open the Start menu , type Windows Security, press Enter, click Device security, and select Core isolation details to find out which specific security blocks are stopping your computer from starting properly.
Follow these steps to check your settings:
- Click the Start button on your taskbar and type Windows Security, then press Enter.
- In the security dashboard, click on Device security on the left side of the window.

Windows Security › Device security - Look for the section titled Core isolation and click on the link that says Core isolation details.
- On this screen, look at the toggle switch for Memory integrity.

If the Windows Security isolation switch is turned off and refuses to stay on, or if the Windows Security isolation switch shows an error message right underneath the switch, you have confirmed the failure. Take note of any warning messages or driver names listed on the Windows Security screen, as warning messages and driver names point directly to the culprit causing the startup failure.
Finding and Removing Incompatible Drivers
Finding and removing incompatible drivers prevents old software translations from blocking your Core Isolation settings. You can check your Windows Security dashboard to spot problem drivers, which are usually outdated files from printers or graphics cards that fail modern memory protection rules and prevent Windows from turning on security isolation.
Your Windows Security screen often lists the exact problem driver. Common examples include old security software, storage utilities like Western Digital tools, or outdated printer software.
To find and handle these drivers:
- Open the Core isolation details screen in your Windows Security settings using the steps from the previous section.

Windows Security › Device security › Core isolation - Look for a section called Review incompatible drivers or look for a list of problematic files.
- Note the names of the drivers causing the issue.
- Go to the official website of the hardware manufacturer (such as Western Digital, HP, or your printer brand) to download the newest version of their software or driver.
- Install the updated driver and restart your computer.
Updating your drivers often clears the block immediately, allowing you to turn Memory Integrity right back on.
How to Force Uninstall Stubborn Problem Drivers
When standard updates fail, you must manually hunt down and remove these leftover files using administrator rights so they stop blocking your Windows Security isolation features.
When standard updates do not work, you must remove these stubborn files manually. You will need administrator rights on your computer to complete these steps.
Follow these steps to remove stubborn drivers:
- Right-click the Start button and select Terminal (Admin) or Command Prompt (Admin). Note: This step requires administrator privileges.
- Type the following command to see a list of third-party drivers on your system, then press Enter:
pnputil /enum-drivers - Look through the list to find the published name of the problem driver (it looks like oem12.inf).
- Once you identify the correct file name, type the following command and press Enter (replace oem12.inf with your actual driver file name):
pnputil /delete-driver oem12.inf /uninstall /force - Restart your computer and try turning on Memory Integrity again in your Windows Security settings.

Checking Virtualization Settings in Your Computer BIOS
Core Isolation needs this special CPU technology to build secure virtual environments, so if virtualization is disabled in your main system firmware, Windows Security isolation will fail to start.
To check and enable virtualization:
- Save your work and restart your computer.
- 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.
- Look through the menus for a setting named Intel Virtualization Technology, Intel VT-x, or AMD-V (sometimes listed under "CPU Configuration" or "Security").
- Change the setting to Enabled.
- Save your changes and exit the BIOS (usually by pressing F10). Your computer restarts normally into Windows.

Once you are back in Windows, open your security settings and try turning on Memory Integrity again.
Advanced Fix: Using Windows Features for Virtualization
Using Windows features for virtualization lets you turn on built-in system tools that support secure security layers and virtual machines. If these background features are turned off or corrupted, Core Isolation fails, but you can easily re-enable them through the classic Windows features menu from your Start search bar.
Follow these steps to check your Windows features:
- Click the Start button, type Turn Windows features on or off, and press Enter.
- In the window that pops up, scroll down and look for Virtual Machine Platform.
- Check the box next to Virtual Machine Platform.
- Also look for Windows Hypervisor Platform and check its box if it is available.
- Click the OK button. Windows searches for files and applies the changes.
- Restart your computer when prompted.
Enabling the core platform files gives Windows the tools Windows needs to run security isolation features properly. Windows security isolation creates a safe, hidden space in your computer memory to protect vital system programs from harmful software and hackers. Turning on these core files matters because Windows security isolation stops working if the core files are missing or turned off, which leaves your computer open to dangerous cyber threats and malicious attacks.
Unique Expert Tip: Fixing Corrupted Security Policies with DISM
Fixing corrupted security policies with DISM repairs damaged operating system files that stop Windows Security isolation from starting after failed updates or power outages. You can run built-in system repair commands using administrator rights to scan your computer and restore the core files needed for proper security functions.
You can use built-in Windows repair tools to scan your system and fix damaged security policies. You will need administrator rights to run these commands.
Follow these steps to repair your system:
- Right-click the Start button and select Terminal (Admin) or Command Prompt (Admin). Note: This step requires administrator privileges.
- Type the following command and press Enter:
DISM.exe /Online /Cleanup-image /Restorehealth - Wait for the process to reach 100 percent. This may take a few minutes as it downloads clean system files from Microsoft servers.
- Next, type the following command and press Enter:
sfc /scannow - Let the system scan finish. If it finds corrupted files, it repairs them automatically.
- Restart your computer and check your security settings.
Unique Expert Tip: Addressing Registry Conflicts Without Direct Edits
Addressing registry conflicts without direct edits involves resetting security services using standard administrative tools to clear out bad configuration data. Instead of risking manual registry changes, you can use PowerShell commands to safely clean out leftover files and get your Windows Security isolation running again.
Follow these steps to reset security policies:
- Click the Start button, type PowerShell, right-click it, and choose Run as administrator. Note: This step requires administrator privileges.
- 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 - Wait for the command to finish running. It reapplies the original default security settings across your operating system.
- Restart your computer to apply the fresh security baseline.
Summary
Fixing Windows Security isolation and Memory Integrity failures involves checking your settings, removing incompatible drivers, enabling hardware virtualization in the BIOS, turning on virtual machine features, and running system repair commands. This comprehensive guide gives everyday users all the steps needed to restore full computer security.
Was this guide helpful?
About the Author
Richard
Tech Writer, IT Professional
Richard, a writer for Geek Rewind, is a tech enthusiast who loves breaking down complex IT topics into simple, easy-to-understand ideas. With years of hands-on experience in system administration and enterprise IT operations, he’s developed a knack for offering practical tips and solutions. Richard aims to make technology more accessible and actionable. He's deeply committed to the Geek Rewind community, always ready to answer questions and engage in discussions.
No comments yet — be the first to share your thoughts!