Introduction
If you’re encountering errors like “This host does not support AMD-V” or “Intel VT-x is unavailable” when using VMware Workstation, VirtualBox, or other virtualization software, you likely need to disable Windows 11’s VBS (Virtualization-Based Security).
Critical Update: On some Windows 11 24H2 systems, disabling VBS can be more complex. Based on personal testing, traditional methods were not sufficient unless I also disabled the Windows Hello-related registry switch described in Step 5.3.
What is VBS and Why Does It Interfere with Virtual Machines?
VBS (Virtualization-Based Security) is a Windows 11 security feature that creates an isolated security environment using the Hyper-V virtualization layer (Microsoft, 2025c, “Virtualization-based security (VBS)”). While this sounds beneficial, there’s a problem:
- VBS uses the Hyper-V virtualization layer, which changes how hardware virtualization features (AMD-V or Intel VT-x) are exposed
- Third-party virtualization software like VMware typically needs direct access to these hardware features
- When VBS/Hyper-V is running, VMware may be forced into a compatibility mode (WHP), or it may fail to start depending on configuration
In simple terms: VBS can block or limit VMware’s access to hardware virtualization unless you use a supported compatibility mode.
The 24H2 Change: Windows Hello and VBS (Observed Behavior)
Starting with Windows 11 24H2, I observed that Windows Hello-related components can keep VBS enabled on my system. This is based on personal testing and is not an official Microsoft statement.
Note (personal testing, not an official statement): On my 24H2 system, even after disabling VBS using traditional methods, VBS would re-enable after reboot unless I also disabled the Windows Hello-related registry switch described in Step 5.3. Your results may vary depending on device, edition, and policy settings.
This is why some users found that (Cumar, 2024, “VBS is not disabled on Windows 11, version 24H2, OS Build 26100.2161”):
- Turned off Memory Integrity ✅
- Ran
bcdedit commands ✅
- Modified registry settings ✅
- After reboot, VBS still shows “Running” ❌
Complete Disabling Steps (For 24H2)
Prerequisites
- Windows 11 (any edition: Home/Pro/Enterprise)
- Administrator privileges
- Virtualization enabled in BIOS (AMD-V or Intel VT-x)
Step 1: Check Current VBS Status
- Press
Win + R, type msinfo32, press Enter (Microsoft, 2025a, “Configure Credential Guard”)
- In the System Information window, scroll down
- Find the “Virtualization-based security” row
- If it shows “Running” → needs to be disabled
- If it shows “Not enabled” → no action needed
Step 2: Disable Tamper Protection
- Open Settings (Win + I)
- Go to Privacy & security → Windows Security
- Click Virus & threat protection
- Click Manage settings
- Toggle Tamper Protection to Off
Step 3: Disable Memory Integrity
- Open Settings (Win + I)
- Go to Privacy & security → Windows Security
- Click Device security
- Click Core isolation details
- Toggle Memory integrity to Off
If you want VMware to run in WHP compatibility mode (with VBS/Hyper-V enabled), do not disable HypervisorPlatform and VirtualMachinePlatform (Zongmin, 2020, “VMware Workstation 15.5 now supports Host Hyper-V mode”).
The commands below are for fully disabling Hyper-V/VBS to maximize performance.
Open Command Prompt as administrator (search for cmd, right-click and select Run as administrator), then run these commands sequentially:
bcdedit /set hypervisorlaunchtype off
dism /online /Disable-Feature /FeatureName:Microsoft-Hyper-V-All /NoRestart
dism /online /Disable-Feature /FeatureName:HypervisorPlatform /NoRestart
dism /online /Disable-Feature /FeatureName:VirtualMachinePlatform /NoRestart
Policy note: If VBS or Credential Guard is enforced via Group Policy or MDM, local registry toggles may be overridden. In that case, disable it in policy (DeviceGuard/VirtualizationBasedSecurity) first (Microsoft, 2025b, “Policy CSP - DeviceGuard”).
Step 5: Modify Registry (Critical!)
⚠️ This step was crucial in my 24H2 testing
5.1 Disable VBS Main Switch
- Press
Win + R, type regedit, press Enter
- Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard
- Find or create EnableVirtualizationBasedSecurity (DWORD 32-bit value)
- Double-click and set the value to 0
5.2 Disable Credential Guard (if exists)
Continue in the registry and navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\CredentialGuard
If an Enabled key exists, set its value to 0
5.3 🔥 Disable Windows Hello VBS Dependency (personal testing)
This step is based on personal testing and is not an official Microsoft requirement.
Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\WindowsHello
Find Enabled (DWORD 32-bit value) and set its value to 0
Important Notes (personal testing):
- On my system, Windows Hello (including PIN login) still worked after this change
- Windows Hello no longer used VBS as its security backend (based on observed VBS state)
- Your experience may differ, especially in managed/enterprise environments or Hello for Business setups
Step 6: Restart Your Computer
Close Registry Editor and restart your computer.
Step 7: Verify Results
After reboot:
- Press
Win + R, type msinfo32, press Enter
- Check if “Virtualization-based security” shows “Not enabled”
- Open VMware Workstation and try starting a virtual machine
- The “AMD-V/VT-x not supported” error should typically no longer appear
FAQ
Q1: Why does VBS automatically re-enable after reboot?
A: (Personal testing) Most likely because the Windows Hello registry switch was still enabled. On my 24H2 system, disabling it stopped VBS from re-enabling after reboot:
HKEY_LOCAL_MACHINE\...\DeviceGuard\Scenarios\WindowsHello\Enabled = 0
Q2: Can I still use Windows Hello and PIN login after disabling?
A: (Personal testing) Yes on my system. But it may vary by device, Windows edition, and enterprise policies (Hello for Business). Treat it as a best-effort outcome, not a guarantee.
Q3: Do I need to disable virtualization in BIOS?
A: No! Absolutely not! Disabling virtualization in BIOS will make VMware completely unable to run. The correct approach is:
- ✅ Enable virtualization in BIOS (AMD-V or Intel VT-x)
- ❌ Disable VBS and Hyper-V in Windows
Q4: What are the security risks of disabling VBS?
A: VBS provides an additional security protection layer. After disabling:
- Some advanced security features will be disabled (like Credential Guard)
- Malware protection capabilities will be slightly reduced
- The real-world impact varies by usage, threat model, and environment
If your computer is primarily used for development, virtualization testing, etc., the performance gains from disabling VBS may outweigh the security loss depending on your threat model.
Q5: What about games (like VALORANT) that require VBS?
A: Some games’ anti-cheat systems (like Riot Vanguard) do rely on VBS. You need to choose between:
- Enable VBS → Can play these games, but VMware may need WHP compatibility mode and could be limited
- Disable VBS → VMware works with full performance, but these games may not run
There’s no perfect solution unless you use dual-boot.
Q6: I have Windows 11 Home, which doesn’t have Group Policy Editor. What should I do?
A: No problem. This tutorial’s methods are entirely based on command line and registry - no Group Policy Editor needed. Home edition works fine.
Compatibility Note: VMware with Hyper-V/VBS Enabled
If you prefer to keep VBS/Hyper-V on, VMware Workstation can still run using Windows Hypervisor Platform (WHP) compatibility mode. This typically has performance or feature limitations compared to direct hardware virtualization (Zongmin, 2020, “VMware Workstation 15.5 now supports Host Hyper-V mode”). The steps in this article focus on maximizing VMware performance by fully disabling VBS/Hyper-V instead of using WHP.
Registry Modification Summary (Quick Reference)
If you want to directly see the registry locations that need modification, here’s the complete list:
| Registry Path |
Key Name |
Value |
Description |
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard |
EnableVirtualizationBasedSecurity |
0 |
Disable VBS main switch |
HKEY_LOCAL_MACHINE\...\DeviceGuard\Scenarios\CredentialGuard |
Enabled |
0 |
Disable Credential Guard |
HKEY_LOCAL_MACHINE\...\DeviceGuard\Scenarios\WindowsHello |
Enabled |
0 |
Windows Hello VBS switch (observed on my system, not official) |
All value types are DWORD (32-bit) Value.
Understanding the 24H2 Documentation Gap
The Windows Hello-related VBS behavior I observed on 24H2 may represent an undocumented change or a device/policy-specific interaction. The specific registry setting (DeviceGuard\Scenarios\WindowsHello) is not prominently mentioned in mainstream documentation, which can confuse users following traditional VBS disabling methods (Microsoft, 2025c, “Virtualization-based security (VBS)”; Cumar, 2024, “VBS is not disabled on Windows 11, version 24H2, OS Build 26100.2161”).
Community forums and discussions (such as Microsoft Q&A) have been helpful in identifying possible workarounds. This tutorial consolidates those findings and personal testing to provide a more complete path for systems where VBS re-enables after reboot (Cumar, 2024, “VBS is not disabled on Windows 11, version 24H2, OS Build 26100.2161”).
Conclusion
The VBS disabling process in Windows 11 24H2 is more complex than before, but with the correct steps, it can usually be disabled (Cumar, 2024, “VBS is not disabled on Windows 11, version 24H2, OS Build 26100.2161”).
Key Points Summary:
- BIOS virtualization must remain enabled ✅
- Windows VBS should be disabled for maximum VMware performance ❌
- You may need to disable the Windows Hello VBS switch (personal testing) ❌
- Verify results after reboot
If you have any questions, feel free to discuss in the comments. Happy virtualizing!
References: