Hi Roshan Lanjewar,
Based on the System Information output, the key detail is that Virtualization-based Security (VBS) is still shown as "Running", which means the Microsoft hypervisor is still active even though Hyper-V may already be disabled. This would explain why VMware or VirtualBox continues to detect a hypervisor and may experience reduced performance.
You can try the following:
- Open Windows Security > Device Security > Core Isolation and turn Memory Integrity off.
- Run
gpedit.mscand navigate to: Computer Configuration > Administrative Templates > System > Device Guard Set Turn On Virtualization Based Security to Disabled. - Open an elevated Command Prompt and run:
bcdedit /set hypervisorlaunchtype off - Then restart the PC.
Since your screenshot also shows App Control for Business policy entries, the device may still have security policies configured that rely on VBS. If the issue remains after the steps above, please share the output of bcdedit /enum particularly the hypervisorlaunchtype entry, as that can help determine what is still keeping the hypervisor active.
I hope this helps point you in the right direction. Let me know if you need further assistance, feel free to ask me by clicking "Add Comment" or "Add Answer" if you cannot add comment so your response will be visible. Thanks for your effort.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.