Recent content by Ev5

Update: To clarify the timeline: I had updated my BIOS earlier (which caused a boot issue that I fixed separately), but the Hyper-V/VBS problem was still there. To finally fix the virtualization loop, I decided to perform a Repair Install of Windows 11 (reinstalling Windows while keeping files...

--- SUMMARY / CURRENT STATUS UPDATE --- I am trying to completely disable the Windows Hypervisor and VBS to run VMware Workstation in Native Mode. Edit: I Managed to disable VBS but Hyper-V no No matter what I do, msinfo32 persistently shows: --- My Hardware * CPU: i7-12700K * Motherboard...

Yes, Core Isolation / Memory Integrity has been OFF the entire time. I am aware that VMware can run on top of Hyper-V, but that is not what I am trying to achieve. I specifically want Native Mode because I do not want the Windows Hypervisor running in the background, reserving memory and...

Thanks for testing that! I updated my MSI Z690 Edge BIOS to version 7D31v1M. The update changelog notes that it enforces 'Pre-boot DMA Protection, VT-d, and IOMMU' as defaults for a security patch (CVE-2025-14303). After the update, my boot configuration was corrupted (0x00000f). I repaired it...

I have run that specific command dozens of times. It successfully changes the BCD entry (as verified by bcdedit /enum {current} showing hypervisorlaunchtype Off), but the setting is completely ignored by the bootloader during startup. Even with that flag set to Off, the system still boots with...

I tried booting into Safe Mode and disabled every Hyper-V/Virtualization service (vmms, hvhost, SgrmBroker, etc.). sc config vmms start= disabled sc config vmcompute start= disabled sc config hvhost start= disabled sc config hns start= disabled sc config HvcMat start= disabled sc config CimFS...

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...

@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: Hyper-V - VM Monitor Mode Extensions Yes Hyper-V - Second Level Address...

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...

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?

I just disabled VT-x in BIOS to test, and msinfo32 showed: 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...

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...

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...

bcdedit /enum {current} Returns this ------------------- Windows Boot Loader identifier {current} device partition=C: path \WINDOWS\system32\winload.efi description Windows 11 locale en-US inherit...

Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All Path : Online : True RestartNeeded : False It's still there even after restarting my PC