Peter1226
Contributor
Contributor

I resolved this issue by using the same disk files to re-create the VM.

This error occurred on a Win 11 host and W10 guest with VMWare WS Pro 17 which is upgraded from 16.2. I have many VM guests and all work OK except for this one Win10 guest. The odd thing is that I can run it without problem. Once it started, I can view the VM settings. The error surfaces only when the guest is off and I try to Edit VM "settings". After I got the error, VMWare WS Pro will quit. Restarting Host is no help. This makes me think it is VM configuration files that are corrupted and caused the problem

Reply
0 Kudos