If you have tried to configure Hyper-V on your Windows PC and encountered the message “VBS HVCI is still enabled. Please disable it and try again,” you are dealing with a conflict between two Windows security features. This VBS/HVCI error in Hyper-V is frustrating, but it is entirely fixable with the right steps.
This guide explains exactly what causes the error, how to resolve it quickly, and how to prevent it from returning.
What Causes the VBS/HVCI Error in Hyper-V
This error occurs because Virtualization Based Security (VBS) and Hypervisor Protected Code Integrity (HVCI) are active on your system. These features use the Windows hypervisor to protect core system processes. However, when Hyper-V tries to initialize its own virtualization layer, it conflicts directly with VBS and HVCI.
Common triggers include:
- Windows 11 enabling VBS and HVCI by default on compatible hardware
- Recent Windows updates re-enabling these security features silently
- OEM systems shipped with Core Isolation turned on out of the box
- Group Policy enforcing HVCI regardless of manual settings
Understanding the cause helps you apply the correct fix without disabling security features you still need elsewhere.
How to Fix VBS/HVCI is Still Enabled Error in Hyper-V
Fix 1: Disable Memory Integrity (HVCI) Through Windows Security
This is the fastest and most straightforward fix for the VBS/HVCI Hyper-V error.
Steps:
- Press Win + I to open Settings and navigate to Privacy and Security
- Click Windows Security, then select Device Security
- Under Core Isolation, click Core Isolation Details
- Toggle Memory Integrity to Off
- Restart your PC and attempt to use Hyper-V again
Fix 2: Disable VBS via the System Information Tool
If the Memory Integrity toggle appears greyed out or does not persist after a restart, use this method to disable VBS at a deeper level.
Steps:
- Press Win + R, type msinfo32, and press Enter
- Scroll down and locate the Virtualization-based Security row
- If it shows Running, proceed with the steps below
- Press Win + R again, type gpedit.msc, and press Enter
- Navigate to Computer Configuration, then Administrative Templates, then System, then Device Guard
- Double-click Turn On Virtualization Based Security and set it to Disabled
- Click Apply, then OK, and restart your system
Fix 3: Disable HVCI Using the Registry Editor
For Windows Home users who do not have access to Group Policy Editor, the Registry Editor provides a direct alternative to fix the VBS/HVCI Hyper-V error.
Steps:
- Press Win + R, type regedit, and press Enter
- Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard
- Locate the EnableVirtualizationBasedSecurity DWORD and set its value to 0
- Additionally, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity
- Set the Enabled DWORD value to 0
- Close the Registry Editor and restart your PC
Fix 4: Disable Core Isolation via BIOS/UEFI Settings
Sometimes VBS is enforced at the firmware level, meaning Windows-side changes do not stick. In that case, you need to address it through BIOS.
Steps:
- Restart your PC and enter BIOS/UEFI by pressing the appropriate key during boot (usually F2, Delete, or F10 depending on your motherboard)
- Navigate to the Security or Advanced tab
- Look for settings labeled Virtualization Based Security, Secure Core, or Memory Integrity
- Disable any of these that are active
- Save changes and exit BIOS, then allow Windows to boot normally
Fix 5: Use DISM Command to Disable HVCI
If GUI methods have not worked, a command-line approach using DISM gives you more direct control over the VBS/HVCI configuration causing the Hyper-V error.
Steps:
- Right-click the Start button and select Windows Terminal (Admin) or Command Prompt (Admin)
- Type the following command and press Enter: mountvol X: /s
- Then run: bcdedit /set hypervisorlaunchtype off
- Additionally, run: reg add “HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard” /v “EnableVirtualizationBasedSecurity” /t REG_DWORD /d 0 /f
- Restart your PC after all commands complete successfully.
Frequently Asked Questions
Is it safe to disable VBS and HVCI for Hyper-V?
Disabling VBS and HVCI reduces a layer of kernel-level protection. However, for development machines, test environments, or systems not exposed to high-risk network activity, this trade-off is generally acceptable. Re-enable them when Hyper-V work is complete if security is a priority.
Why does the VBS/HVCI error come back after a Windows update?
Windows 11 updates are designed to re-enable security features like Memory Integrity automatically. As a result, you may need to repeat the disable process after major updates. Using the Group Policy or Registry method provides more durable results than the Windows Security toggle alone.
Can I run Hyper-V and VBS at the same time?
Not in standard configurations. Both features compete for the Windows hypervisor layer. Microsoft does not officially support running them simultaneously on the same instance, which is precisely why this error appears.
Does this error affect WSL 2 or other virtualization tools?
This specific error targets Hyper-V directly. However, WSL 2, VMware Workstation, and VirtualBox can also behave unexpectedly when VBS or HVCI is active, since they all depend on hardware virtualization access.
Conclusion
The “VBS/HVCI is still enabled. Please disable it and try again” error in Hyper-V is a direct conflict between Windows security features and the virtualization stack. Fortunately, every fix in this guide addresses that conflict at a different system level, so at least one solution will work for your specific setup. Start with Fix 1 for the quickest result, and work through the remaining methods if the error persists.
