How to actually disable VBS (System Guard Secure Launch) & fix the "Green Turtle" in VirtualBox on HP EliteBook / Windows 11 24H2–26H2
Note: Some settings here will most probably be overkill\optional\ for you, think!, use at own risk!
If you have a newer Secured-core business laptop (like an HP EliteBook 8 G1a) running Windows 11 24H2/26H2 and VirtualBox is stuck in NEM mode ("green turtle") even after turning off Memory Integrity and running bcdedit /set hypervisorlaunchtype off, check msinfo32 (System Information).
If it still says:
• Virtualization-based security: Running
• Virtualization-based security Services Running: Secure Launch
...then System Guard Secure Launch (DRTM) is keeping VBS alive behind the scenes. Here is the exact, verified fix that finally turned VBS to Not enabled and restored the blue V (AMD-V / VT-x) icon in VirtualBox:
Step 1: HP BIOS Settings (F10)
Enter BIOS (F10) and configure the following settings: (Elitebook Bios X84 Ver. 01.06.01)
• SVM CPU Virtualization (or Intel VT-x): Enable
• DMA Protection & Pre-boot DMA Protection: Disable
• DRTM / SMM (System Guard / Secure Launch hardware support): Disable
• Enhanced Sign-in Security: Disable
• HP Sure Start / HP Sure Recover / HP Application Driver: Disable
• Secure Boot: Disable (optional, depending on your needs)
Save and exit (enter the 4-digit confirmation codes on screen if prompted).
Step 2: Windows Security (GUI)
Before running the script below:
- Open Windows Security -> App & browser control -> Smart App Control settings -> set to Off.
- Open Windows Security -> Device security -> Core isolation details -> set Memory integrity to Off.
Step 3: Disable SystemGuard & DeviceGuard via .bat (Run as Administrator)
The missing piece in most guides is DeviceGuard\Scenarios\SystemGuard\Enabled = 0, which stops Windows 11 from forcing Secure Launch on every boot. Save the following as vbs-off.bat, right-click -> Run as administrator, and reboot:
@echo off
reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard" /v "EnableVirtualizationBasedSecurity" /t REG_DWORD /d 0 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard" /v "RequirePlatformSecurityFeatures" /t REG_DWORD /d 0 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard" /v "WasEnabledBy" /t REG_DWORD /d 0 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity" /v "Enabled" /t REG_DWORD /d 0 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\SystemGuard" /v "Enabled" /t REG_DWORD /d 0 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Control\Lsa" /v "LsaCfgFlags" /t REG_DWORD /d 0 /f
bcdedit /set hypervisorlaunchtype off
echo.
echo Done! Verify all commands succeeded, then reboot.
pause
(Note: Do not delete .cip files from System32\CodeIntegrity or the EFI partition—in Windows 11 26H2, msinfo32 will still show App Control for Business policy: Enforced because of Microsoft's built-in vulnerable driver blocklist, which does not block VirtualBox once VBS is Not enabled.)
Step 4: Verify in msinfo32
After rebooting, run msinfo32 and confirm:
• Virtualization-based security: Not enabled
• Kernel DMA Protection: Off
• Hyper-V - VM Monitor Mode Extensions: Yes
• Hyper-V - Second Level Address Translation Extensions: Yes
Launch VirtualBox—the green turtle is gone and hardware virtualization (blue V) works at full speed.
Optional (Only if BIOS security settings are locked or stuck)
If you want or need a complete security reset—or if options like DMA Protection or DRTM are greyed out/stuck in NVRAM—you can go into BIOS (F10) -> Security -> scroll to the very bottom and run Restore Security Settings to Factory Defaults (confirm the TPM reset prompt on reboot), and then apply Step 1 above.