Unable to Fully Disable Hyper-V – “A hypervisor has been detected” Still Appears in systeminfo

Question

Hi everyone,

I'm facing a persistent issue where the line “A hypervisor has been detected. Features required for Hyper-V will not be displayed.” still shows up when I run the systeminfo command, even after trying every method commonly recommended to disable Hyper-V.

I do not want to use any virtualization (e.g., Hyper-V, VBS, WSL, etc.), and my goal is to completely remove all traces of any hypervisor so other virtual machines (e.g., VirtualBox) can run without conflicts.

Here’s what I’ve already tried (all successfully executed):

1. bcdedit commands:

bcdedit /set hypervisorlaunchtype off
bcdedit /set vm No

2. Disabled Windows Features via DISM & PowerShell:

DISM /Online /Disable-Feature:Microsoft-Hyper-V-All /NoRestart
DISM /Online /Disable-Feature:HypervisorPlatform /NoRestart
DISM /Online /Disable-Feature:VirtualMachinePlatform /NoRestart
DISM /Online /Disable-Feature:Containers /NoRestart
# PowerShell alternative
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All -NoRestart
Disable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform -NoRestart
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux -NoRestart
Disable-WindowsOptionalFeature -Online -FeatureName Windows-Hypervisor-Platform -NoRestart

(Note: Last command says “Feature name Windows-Hypervisor-Platform is unknown.”)

3. Group Policy:

Disabled Virtualization Based Security (VBS) via:

• Computer Configuration > Administrative Templates > System > Device Guard
  • Set “Turn On Virtualization Based Security” to Disabled

4. Registry:

Modified the registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard
- EnableVirtualizationBasedSecurity = 0

5. Windows Features GUI:

Manually unchecked everything related to:

• Hyper-V
• Virtual Machine Platform
• Windows Hypervisor Platform
• Containers
• Windows Subsystem for Linux

6. Device Manager:

Uninstalled suspicious drivers under Network Adapters:

VMware Virtual Ethernet Adapter for VMnet1

  VMware Virtual Ethernet Adapter for VMnet8
  
  Uninstalled from **System Devices**:
  
     Microsoft Hyper-V Virtualization Infrastructure Driver
     
        Microsoft Hypervisor Service
        
           Microsoft Virtual Drive Enumerator
           

7. Disabled Memory Integrity (Core Isolation):

Turned OFF from Windows Security > Device Security > Core Isolation > Memory Integrity

8. Fresh Windows Installation:

• This is a fresh install of Windows and I made sure not to install anything Hyper-V related during or after the setup.

Still, the result from systeminfo says:

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

Also:

Virtualization-based Security: Running

System Info:

• OS: Windows 11 (fresh install) Platform: Laptop, x64

  No Hyper-V visible in Windows Features or Services
  
     - VirtualBox & other tools say VT-x is not available or conflict detected  
  
     **My goal:** **Completely remove Hyper-V and any virtualization layer** so I can use third-party virtualization (VirtualBox, VMware, etc.) without errors.
  
     Please help if you know of **any deeper-level method or hidden config** that may still be causing the hypervisor to be detected.
  
     Thank you!
  

Answer 1

Rabiko,

After reading https://learn.microsoft.com/en-us/troubleshoot/windows-client/application-management/virtualization-apps-not-work-with-hyper-v, I interpret this that your BIOS/UEFI have virtualization enabled.  The system info on my PC states exactly what you see with all virtual services are disabled.  

I rebooted and disabled virtualization in the BIOS and system info is reporting something different.

Because virtualization is enabled on the hardware, Microsoft reads this that virtualization is possible, the hypervisor engine is enabled. My interpretation. Regardless, if you disable virtualization in BIOS/UEFI, your message will change.

Justin