Forum Discussion
jacopo
May 01, 2026Copper Contributor
Hypervisor still detected even after disabling Hyper-V, VBS, and all related features (Windows 11)
Hi everyone,
I’m experiencing an issue where virtualization / hypervisor features remain active on my system, even after attempting to fully disable them.
System:
- GPU: AMD Radeon RX 6900 XT
- Motherboard: MSI B550M PRO
- OS: Windows 11
❗ Problem description
Even after multiple attempts to disable Hyper-V and related features, my system still reports that a hypervisor is active.
For example:
- Running systeminfo shows:
- “A hypervisor has been detected. Features required for Hyper-V will not be displayed.”
- In System Information:
- “Virtualization-based security: Running”
Additionally:
- Some applications and Android emulators detect Hyper-V as enabled
- Behavior suggests that virtualization is still active at system level
🔧 Troubleshooting steps already performed
I have tried all of the following:
Windows Features
- Disabled:
- Hyper-V
- Virtual Machine Platform
- Windows Hypervisor Platform
- Windows Sandbox
- Windows Subsystem for Linux
Boot configuration
- Executed:bcdedit /set hypervisorlaunchtype off bcdedit /set vsmlaunchtype off
Windows Security
- Disabled:
- Core Isolation
- Memory Integrity
Services
- Stopped and disabled:
- hvhost
- vmcompute
BIOS changes
- Enabled SVM (virtualization)
- Disabled IOMMU
- Disabled Secure Boot (for testing)
Other steps
- Full shutdown (no fast startup)
- Clean GPU driver reinstall
- Multiple reboots
❗ Current situation
Despite all of the above:
- Hypervisor is still detected
- Virtualization-based security remains Running
- Some applications still behave as if Hyper-V is enabled
❓ Questions
- Is there any way to fully disable Hyper-V / VBS on Windows 11?
- Is this behavior expected on certain systems due to security enforcement (e.g. firmware or OS policies)?
- Could this be caused by something outside standard Windows features (e.g. hidden components or drivers)?
Any help or clarification would be greatly appreciated.
Thank you.
No RepliesBe the first to reply