Go to Windows Features and turn OFF:
Hyper-V
Virtual Machine Platform
Windows Hypervisor Platform
Reboot
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
How is it possible to disable Virtualization for my surface book 3 ?
I have type cmd (Administrator) : bcdedit /set hypervisorlaunchtype off
any other ideas ?
Go to Windows Features and turn OFF:
Hyper-V
Virtual Machine Platform
Windows Hypervisor Platform
Reboot
AI answer
To fully disable virtualization-related features on a Surface Book 3, there are several layers that may need to be turned off, depending on what is enabled and what behavior is desired.
The command already used:
bcdedit /set hypervisorlaunchtype off
stops the Hyper-V hypervisor from launching at boot for that boot entry. This is one key step, but other Hyper-V–based components can still keep virtualization active.
Use the following additional options as needed:
Third‑party virtualization apps and some scenarios require Hyper‑V and its dependent security features to be disabled.
Options to disable Hyper‑V:
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Hypervisor
DISM /Online /Disable-Feature /FeatureName:Microsoft-Hyper-V-Hypervisor
If the goal is to block Hyper‑V entirely on the device, it is also possible to remove the broader Hyper‑V feature:
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
bcdedit /set hypervisorlaunchtype off
To confirm whether the Hyper‑V hypervisor is active:
A hypervisor has been detected. Features required for Hyper‑V will not be displayed.
If this line is present, Hyper‑V is still running. If it is absent after using the steps above and rebooting, Hyper‑V is not active.
Some Windows features (for example WSL2, some security features, and other virtualization stacks) rely on Virtual Machine Platform and similar components. To reduce virtualization usage further:
If gaming performance is the concern, also consider turning off Memory integrity (Hypervisor‑protected code integrity) from Core isolation in Windows Security, as it is Hyper‑V–based and can affect performance.
If frequent switching between virtualization on/off is needed, create an alternate boot entry with the hypervisor disabled:
bcdedit /copy {default} /d "Hypervisor Off"
Note the returned identifier. bcdedit /set {identifier} hypervisorlaunchtype off
On next boot, select the Hypervisor Off entry to start Windows without the hypervisor.
Be aware that disabling these features can reduce security (for example, disabling Memory Integrity and Credential Guard) and will prevent Hyper‑V, WSL2, and other virtualization‑dependent features from working until re‑enabled.
References: