Cannot Disable Windows Hypervisor - Stuck on "A Hypervisor has been detected"

Ev5 · Jan 18, 2026

The Issue:
I am trying to disable Hyper-V, but Windows refuses to unload its own Hypervisor.
In `msinfo32`, it persistently shows:

A hypervisor has been detected. Features required for Hyper-V will not be displayed.

My Hardware:
* **CPU:** i7-12700K
* **Motherboard:** MSI MPG Z690 EDGE WIFI DDR4
* **OS:** Windows 11 25H2
* **BIOS Settings:**
* VT-x (Virtualization): **Enabled**
* VT-d (IOMMU): **Disabled**
* Kernel DMA Protection: **Disabled**

What I have already tried:

Group Policy & Windows Features
GPEDIT: `Local Computer Policy > System > Device Guard` -> **Turn On Virtualization Based Security** set to **Disabled**.
Disabled Features: Virtual Machine Platform, Windows Hypervisor Platform, Hyper-V, and WSL.
BCD / Boot Configuration (Ran as Admin)
bcdedit /set vsmlaunchtype Off
bcdedit /set hypervisorlaunchtype off
bcdedit /deletevalue {current} vsmlaunchtype
Deep Clean Tools: (I wanted to disable VBS, and now Virtualization-based security is not enabled, just as I planned)
- Ran `DG_Readiness_Tool_v3.6.ps1 -Disable -AutoReboot`.
- Confirmed the UEFI black screen prompt to disable Device Guard/Credential Guard upon reboot.
Registry
`HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard` -> Set `EnableVirtualizationBasedSecurity` to **0**.

DISM Feature Removal (Ran as Admin)

Code:

dism /online /disable-feature /featurename:Microsoft-Hyper-V-All
dism /online /disable-feature /featurename:VirtualMachinePlatform
dism /online /disable-feature /featurename:HypervisorPlatform

Software Context (VMware)
- I have VMware Workstation installed, but I have **disabled all VMware services** (set to Manual/Stopped) to ensure they aren't triggering the hypervisor.

Current Status:
Despite all of the above, `msinfo32` still says a hypervisor is detected.

OAT · Jan 18, 2026

Ev5 said:
The Issue:
I am trying to disable Hyper-V, but Windows refuses to unload its own Hypervisor.
In `msinfo32`, it persistently shows:
Despite all of the above, `msinfo32` still says a hypervisor is detected.

What about in Windows features? Are the ones on screenshot below still checked?
You would think that they would be off with the DISM commands you used but double check anyway.
But I see you did not use the powershell command:

Code:

Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All

Again, you would think that was covered with what you did, but it will not hurt to run that one and it will ask for a restart.

May I ask why you want to disable the Windows Hypervisor?

Ev5 · Jan 18, 2026

Already Turned off.

OAT · Jan 18, 2026

Ev5 said:
Already Turned off.

Please refresh the page as I have posted additional content.
I also wanted to add that Hypervisor & Broadcom VMWare can run together as the screenshot below shows.
I never disable the hypervisor as I use Sandbox.
I run 2 Windows VMs & 1 Linux VM without any performance penalty.

Ev5 · Jan 18, 2026

OAT said:
May I ask why you want to disable the Windows Hypervisor?

I need VMware Workstation to run using native VT‑x, and I also want to improve overall system performance.

OAT said:
Code:

Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All

I believe I already ran that command earlier, but I’ll run this specific PowerShell command again now just to be absolutely sure.

Ev5 · Jan 19, 2026

OAT said:
Code:

Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All

Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All

Path :
Online : True
RestartNeeded : False

"A hypervisor has been detected. Features required for Hyper-V will not be displayed."

It's still there even after restarting my PC

Ev5 · Jan 19, 2026

bcdedit /enum {current}
Returns this

Code:

-------------------
Windows Boot Loader
identifier              {current}

device                  partition=C:

path                    \WINDOWS\system32\winload.efi

description             Windows 11

locale                  en-US

inherit                 {bootloadersettings}

recoverysequence        {0e488f09-2290-11f0-b782-93ab5d0521e2}

displaymessageoverride  Recovery

recoveryenabled         Yes

isolatedcontext         No

allowedinmemorysettings 0x15000075

osdevice                partition=C:

systemroot              \WINDOWS

resumeobject            {0e488f07-2290-11f0-b782-93ab5d0521e2}

nx                      OptIn

bootmenupolicy          Standard

hypervisorlaunchtype    Off

Ev5 · Jan 19, 2026

Here is the latest update. I have completely stripped the Secure Boot keys and checked for any lingering drivers.

BIOS Status:
Secure Boot Mode: Custom
Action Taken: Delete All Secure Boot Keys.

Driver Filter Check (fltmc):
I checked for rogue drivers (like VMware) but the list looks clean.

fltmc in CMD Admin

Code:

Filter Name                     Num Instances    Altitude    Frame

[HR][/HR]
bindflt                                 1       409800         0
UCPD                                   10       385250.5       0
WdFilter                               10       328010         0
storqosflt                              0       244000         0
wcifs                                   0       189900         0
CldFlt                                  3       180451         0
bfs                                    12       150000         0
FileCrypt                               0       141100         0
luafv                                   1       135000         0
UnionFS                                 0       130850         0
npsvctrig                               1        46000         0
Wof                                     8        40700         0
FileInfo                               10        40500         0

System Guard Check:
I also checked if System Guard (SgrmBroker) was forcing it, but the service doesn't even exist.

sc query SgrmBroker in CMD Admin

Code:

[SC] EnumQueryServicesStatus:OpenService FAILED 1060:

The specified service does not exist as an installed service.

Current Situation:
Despite deleting winsipolicy.p7b from the EFI partition, deleting all Secure Boot keys in BIOS, and having no active virtualization drivers... msinfo32 still shows "A hypervisor has been detected".

cereberus · Jan 19, 2026

Turn off hardware virtualisation from the bios.

Ev5 · Jan 19, 2026

cereberus said:
Turn off hardware virtualisation from the bios.

Do you mean disabling VT-x (Intel Virtualization Technology)?

If I do that, it will prevent VMware Workstation from running (since VMware requires VT-x to function).

My specific goal is to have Hardware Virtualization (VT-x) ENABLED, but the Windows Hypervisor/VBS software layer DISABLED, so that VMware can use the hardware directly.

Ev5 · Jan 20, 2026

cereberus said:
Turn off hardware virtualisation from the bios.

I just disabled VT-x in BIOS to test, and msinfo32 showed:

Code:

Hyper-V - VM Monitor Mode Extensions    Yes
Hyper-V - Second Level Address Translation Extensions    Yes
Hyper-V - Virtualization Enabled in Firmware    No
Hyper-V - Data Execution Protection    Yes

This confirms the Windows Hypervisor was gone, but "Virtualization Enabled in Firmware" was No, which breaks VMware.

However, the moment I re-enabled VT-x in BIOS and restarted, msinfo32 immediately reverted to:

Code:

A hypervisor has been detected. Features required for Hyper-V will not be displayed.

This confirms that enabling Hardware Virtualization (VT-x) is instantly triggering the Windows Hypervisor to load, ignoring my BCD "off" settings.

Ev5 · Jan 20, 2026

Is there any way to see exactly what hypervisor or feature is being detected? I've checked fltmc for drivers and Event Viewer for Code Integrity policies, and both are clean. What is the next step to trace this?

Ghot · Jan 20, 2026

@Ev5

Did you check to see if virtualization is enabled in the BIOS?
I don't know what it's called on an MSI Intel board.
On my ASUS AMD board it's called SVM

Ev5 · Jan 20, 2026

Ghot said:
@Ev5

Did you check to see if virtualization is enabled in the BIOS?
I don't know what it's called on an MSI Intel board.
On my ASUS AMD board it's called SVM

Yes, Virtualization (VT-x) is definitely Enabled in my BIOS.

That is actually the problem. When I enable it, Windows sees it and immediately loads its own hidden Hypervisor, which locks out VMware from using the hardware directly.

I am trying to achieve this specific state in msinfo32:

Code:

Hyper-V - VM Monitor Mode Extensions    Yes
Hyper-V - Second Level Address Translation Extensions    Yes
Hyper-V - Virtualization Enabled in Firmware    Yes   <-- I need this YES
Hyper-V - Data Execution Protection    Yes

Currently, I get "A hypervisor has been detected," which means the Windows software layer is active and blocking me from that raw hardware access.

Ghot · Jan 20, 2026

@Ev5

As a test... go into the BIOS and DISABLE Virtualization, then save and boot into Windows and see if that affected the hypervisor problem.

If it doesn't help, then go back to the BIOS and re-enable it.

And here's ten points, just for filling out "most" of your computer specs.

Ev5 · Jan 21, 2026

@Ghot
Thanks! I actually tried exactly that earlier in the troubleshooting process.

When I DISABLE Virtualization (VT-x) in the BIOS, the "A hypervisor has been detected" message disappears, and msinfo32 shows this:

Code:

Hyper-V - VM Monitor Mode Extensions    Yes
Hyper-V - Second Level Address Translation Extensions    Yes
Hyper-V - Virtualization Enabled in Firmware    No
Hyper-V - Data Execution Protection    Yes

However, as soon as I go back to BIOS and RE-ENABLE it (which I need for VMware), the message "A hypervisor has been detected" comes back immediately.

This confirms that the Windows Hypervisor is launching specifically because it detects the hardware capability, effectively hijacking it before VMware can get to it.

Ev5 · Jan 21, 2026

Okay, I think I've figured out what's happening. Windows seems to be "healing" itself and forcing these settings back on after every reboot.

I was following Step 6 from this Broadcom guide (https://community.broadcom.com/vmwa...ion/how-to-disable-hyper-v-in-windows-11-24h2) using the official Device Guard and Credential Guard hardware readiness tool.

Here is the pattern I found:

1. I ran the readiness tool script and rebooted. VBS turned "Not Enabled", but the Hypervisor message was still there.
2. I ran the script again immediately after. This time it actually worked! The "Hypervisor detected" message disappeared and everything looked correct.
Like this

Code:

Hyper-V - VM Monitor Mode Extensions    Yes
Hyper-V - Second Level Address Translation Extensions    Yes
Hyper-V - Virtualization Enabled in Firmware    Yes
Hyper-V - Data Execution Protection    Yes

3. But then I did a normal restart (without using the tool), and it completely reverted. Both VBS and the Hypervisor are active again.

This is what msinfo32 shows now after that normal restart:

Code:

Virtualization-based security    Running
Virtualization-based security Required Security Properties   
Virtualization-based security Available Security Properties    Base Virtualization Support, Secure Boot, UEFI Code Readonly, SMM Security Mitigations 1.0, Mode Based Execution Control, APIC Virtualization
Virtualization-based security Services Configured   
Virtualization-based security Services Running   
A hypervisor has been detected. Features required for Hyper-V will not be displayed.

Btw, VT-x was enabled in BIOS throughout all these steps.

DJNelson · Jan 21, 2026

Nothing more frustrating than trying to hack into your own computer to regain control of it. Have you tried booting into safe mode and removing the hyper-v services?

Hopachi · Jan 22, 2026

That msinfo32 line isn't very specific so not sure what to make of it in the end. What hypervisor is detected if all features are disabled...
More important is a stable system and that VMs run fine without hiccups.
After trying all those steps, does VMware Workstation actually work normally or do you get slowdowns and mentions of Hyper-V mode?

spapakons · Jan 22, 2026

Open traditional Control Panel, switch from group to large icons top right, open Add/Remove Programs and then click to open Turn Windows Features On or Off. Scroll down, there is not only Hyper-V, but also Windows Supervisor Platform and Virtual Machine Platform. Make sure you also disable these two:

Cannot Disable Windows Hypervisor - Stuck on "A Hypervisor has been detected"

Member

Attachments

My Computer My Computer

At a glance

Bizarre Member

My Computers My Computers

At a glance

At a glance

Member

Attachments

My Computer My Computer

At a glance

Bizarre Member

My Computers My Computers

At a glance

At a glance

Member

My Computer My Computer

At a glance

Member

My Computer My Computer

At a glance

Member

My Computer My Computer

At a glance

Member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Member

My Computer My Computer

At a glance

Member

My Computer My Computer

At a glance

Member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Member

My Computer My Computer

At a glance

Member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Similar threads

My Computer

My Computers

My Computer

My Computers

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computers

My Computer

My Computers

My Computer

My Computer

My Computer

My Computers

My Computers