vm doesn't start anymore after windows 11 update

[rene_link]

Today my windows 10 notified my that the windows 11 update is available. The windows 11 update perfectly worked, but some of my virtual machines do not start anymore.

The virtual machines themself use virtualization. I'm running docker inside the Windows 10 based vm. Therefore I enabled all three virtualization engine settings in the processor configuration:

Everything worked fine before the Windows 11 update. When I try to start the vm now I get

So I disabled the "CPU performance counters" setting.

Now I get

If I click "No" I get

If I click "Yes" I get

But even if "Continue without virtualized Intel VT-x/EPT" would work, I'm pretty sure that the docker installation inside the vm will not work.

I also checked if "Hyper-V" is enabled on my host, but it isn't

What should I do to get my "vmware workstation 16.2.2 build-19200509" virtual machines to work again?

[bluefirestorm]

Have a look at this thread
https://communities.vmware.com/t5/VMware-Workstation-Pro/Failed-to-power-on-virtual-machine-This-hos...

[tnvkzcdyc]

Can you assist? I have the same issue but nothing in that thread helped. VMWare (and the guest vm) worked fine until the host did an in-place upgrade to Windows 11. Now I get the "Disk" power on failed error. Hyper-V is disabled.

[wila]

Hi,

---

@tnvkzcdyc wrote:
Now I get the "Disk" power on failed error. Hyper-V is disabled.

---

Attach the vmware.log file from the VM that you can't start to a reply here.

--
Wil

[tnvkzcdyc]

Here you go! Thank you for the assistance!

I checked that CredGuard / Core Isolation are off, hypervisorlaunch is set to off, the Hyper-V windows feature is disabled, and hyper-v is off (before taking those steps "Hyper-V detected" did show up in the vmware.log and now it doesn't). The vm worked fine with Windows 10 and didn't experience any unexpected power outages.

[wila]

Hi,

It's not a Hyper-V issue or a Windows 11 one. That's all just accidental.
The error you posted already hinted at that, but the vmware.log file helps to rule things out.

Here's the relevant snippet:

2023-02-25T21:41:08.323Z In(05) vmx DISK: OPEN scsi0:0 'C:\Users\[username]\Documents\Virtual Machines\Kubuntu 18.04\Kubuntu 18.04-000003.vmdk' persistent R[]
2023-02-25T21:41:08.495Z In(05) vmx DISKLIB-SPARSE: "C:\Users\[username]\Documents\Virtual Machines\Kubuntu 18.04\Kubuntu 18.04-000001.vmdk" : failed to open (14): Disk needs repair.
2023-02-25T21:41:08.495Z In(05) vmx DISKLIB-LINK : "C:\Users\[username]\Documents\Virtual Machines\Kubuntu 18.04\Kubuntu 18.04-000001.vmdk" : failed to open (The specified virtual disk needs repair). 

Somehow the virtual disk is broken and needs repair.
However before you start ANY repair actions I strongly recommend to make a full copy of the VM.
Preferably to an external disk. This because the damage to the VM might be because your physical disk is failing and in that particular case a copy on a failing disk might be just as good as not having that copy at all.

--
Wil