I create a question in [Windows Server forum](Question, Windows Server 2022 21H2 after trying to install 2022-07 KB5015827 CU get BSOD on VMware, ...) too.
It looks like this just happened to me on Workstation 16.3.4, but this time with Windows 10 as the guest OS (Windows 11 as the host OS)
Exactly the same error after it had just done the latest MS updates and it is currently automatically uninstalling and cleaning up after booting into repair mode briefly. Really hope it works as this is a fairly critical VM for me that I (stupidly) had not backed up for a little while and had never had issues with updates before.
Has anyone else had this happen with Windows 10 as the guest OS?
This just happened to me. I'm running VMware Workstation 15 Pro (15.5.7 build-17171714) with guest OS of Windows 10 version 1809.
Dropping my core count down to 1 allowed the VM to boot and I was able to uninstall the recent batch of updates and return my core count to 4.
Yes. I have now gotten this applying a pending update to Win11 and with Win10 22H2.
VERY frustrating, but I was "pleased" to see that at least I'm not the only one seeing this problem.
I see that Workstation 17 has just been released. No mention of this issue in the release notes I can see, so is anyone able to say if it resolves it before I decide whether or not to upgrade?
All my issues went away. I tried with the latest versions of Windows 11, 10 and Server 2022. So far so good...for now. I hope future Windows upgrades don't cause the same problems.
confirmed that the "1 vcpu" workaround did not work on Workstation 16 on Windows 11 with a Windows 10 guest (using a new i7-12700 cpu here, tried even disabling the e-cores to no avail)
after upgrading to Workstation 17 Player, the update suceeded and everything is back to normal. 4 vCPUs and the VM is happy.