VMware Workstation

I experienced this issue like this.

I moved a v16.2 win10 vm from VMWv17.1 on win10 to VWM17.5.2 on Win 11.

hypervisorlaunchtype is set from install as 'auto'. The vm is 2-4 core CPU for 8 processors 32GB RAM.

Both the source and destination hosts are i9-12900KS processors. The destination is 128GB DDR5, a superior mother board and the updated Intel Graphics UHD770.

I saw a thread about P and E cores and from resource monitor could see that most activity on my system is on parked e-cores.

I added the lines To the VMX file:

processor8.use = "FALSE"

processor9.use = "FALSE"

processor10.use = "FALSE"

processor11.use = "FALSE"

processor12.use = "FALSE"

processor13.use = "FALSE"

processor14.use = "FALSE"

processor15.use = "FALSE"

No real significant change after reboot. It did crash several times before it actually started.

System thread exception not handled was the reason for most of them. The second one was processor not supported.

I am also unsure if those are the correct settings. As in resource monitor windows shows a CPU for each thread and there are 24 total threads. I have not been able to find more information about the VMX file.

The other change I read was to run VMWare WS Pro as Admin.

With the previous changes in place [since the machine was booting stable again] the results are amazing.

So far so good. But I can't figure out how to use the new feature to run vm on startup. I can't load VMware as Admin.

If there are moderators here, what does running as admin have to do with it?

Hi,

I decided to finally upgrade to Windows 11 22H2 on my host machine. Upgrade was smooth and all seems to be running fine until I started Vmware Workstation Pro 17. All my Windows guests booted very slow and they even froze so I had to shut them down. Restart did not help and what was running smoothly before was extremely slow and unresponsive. I had to downgrade my host machine Windows back as I did not find any workaround. I found something mentioning Microsoft introduced its own Hypervisor or something but there were just some questionable workaround to uninstall/disable something.

ANyone else is experiencing the same on the latest Workstation 17 Pro and Windows 11 22H2?

Thanks.