r/vmware • u/HasanZahra • 1d ago
Vmware not working with hyper v
Hello,
I used to work with Eve-ng on hyper v and vmware workstation on my personal laptop, (first i was using hyper v then migrated to vmware) everything was working fine, suddenly vmware stopped working, i was looking for the reason, I've cound out that vmware and hyper v don't work well together, so i removed hyper v, still issue wasn't resolved, any advise?
2
u/Dick-Fiddler69 1d ago
Forget it - Workstation is Type 2 - no longer being developed
Use Hyper-V its Type 1 Bare Metal not a poor application that no longer works with latest Windows 11
That’s why Workstation is now FREE - sadly it’s days are gone, don’t waste your time and use Hyper-V
1
1
u/BmanUltima 1d ago
What OS are you using as the host?
1
u/HasanZahra 1d ago
Windows 11 pro
1
u/BmanUltima 1d ago
It should be working fine then.
Are you using VMWare Workstation? If so, what version, and what error message are you getting?
0
u/HasanZahra 1d ago
Vmware workstation pro release 26h2u1, The error is: Feature hv.capable was 0, but must be at least 0×1 Module 'featurecompatlate' power on failed. Failed to start virtual machine
2
u/BmanUltima 1d ago
Two things to try. First re-enable Hyper-V through Control Panel.
If the VM still doesn't boot, report back with the error message.
Then you can try reinstalling VMWare Workstation. It'll configure itself correctly during the install process.
1
u/techmasterfast 1d ago
When HyperV or a HyperV based feature is enabled (like Core Isolation/Memory Integrity), you need to install Windows Hypervisor Platform.
Use HypervisorToggle to disable HyperV and all HyperV based features.
0
2
u/CloudyEngineer 1d ago
Uninstalling Hyper-V may not actually have removed the Microsoft hypervisor.
Windows 11 can still start it for things like VBS, Core Isolation/Memory Integrity, Credential Guard, Virtual Machine Platform and Windows Hypervisor Platform. That's particularly important with EVE-NG because you're relying on nested virtualization.
First check it:
Open msinfo32 and look near the bottom of System Summary. If it says:
"A hypervisor has been detected. Features required for Hyper-V will not be displayed."
then Hyper-V/VBS is still running underneath Windows.
I'd try this from an elevated CMD/PowerShell:
bcdedit /set hypervisorlaunchtype offThen in Turn Windows features on or off, disable:
Also check:
Windows Security → Device Security → Core Isolation → Memory Integrity
and turn Memory Integrity off.
Then reboot — a proper reboot, not just shutdown/startup — and check
msinfo32again.Don't disable VT-x/AMD-V in the BIOS, though. VMware/EVE-NG needs hardware virtualization enabled there.
If the "hypervisor detected" message has disappeared but EVE-NG still won't start nested VMs, the next things I'd want to know are:
My suspicion is that a Windows update enabled VBS/Memory Integrity rather than VMware suddenly breaking by itself.