Thanks so much for your assistance and I will try those things you said and if it doesn't work I've been a little puzzled as to how to elevate to a support issue with VMware, if you can post a link t...
See more...
Thanks so much for your assistance and I will try those things you said and if it doesn't work I've been a little puzzled as to how to elevate to a support issue with VMware, if you can post a link that I can submit a support request, please let me know. Allan
re. The original question. What guest OS are you running? PC- Device name ??? Processor Intel(R) Xeon(R) W-11855M CPU @ 3.20GHz 3.19 GHz Installed RAM 32.0 GB (31.2 GB usable) Device ID BAC2B...
See more...
re. The original question. What guest OS are you running? PC- Device name ??? Processor Intel(R) Xeon(R) W-11855M CPU @ 3.20GHz 3.19 GHz Installed RAM 32.0 GB (31.2 GB usable) Device ID BAC2B41F-8EED-4700-997C-4E7?? Product ID ??? System type 64-bit operating system, x64-based processor OS- Edition Windows 10 Pro for Workstations Version 21H2 Installed on 12/20/2021 OS build 19044.1526 Experience Windows Feature Experience Pack 120.2212.4170.0 Does it help if you disable 3D acceleration? Disabled now Have you tried to lower the amount of virtual CPU's? was 1 CPU and 6 cores, lowered to 1 CPU and 2 cores Did you check any of the options in the CPU configuration for "virtualization engine"? If so, have you tried removing all checkboxes there? No Virtualization -- Allan
I can check all that stuff, just to be sure you understand. These VMs ran perfectly fine on V16.0 but started having problems with V16.1 onward. Does this fact change any of your recommendations>
Why does my guest VM's become unresponsive without affecting ProV16.1 and V16.2 or my host OS (Win10 latest). I cannot power off the guest OS or close it without rebooting my host PC. This did not o...
See more...
Why does my guest VM's become unresponsive without affecting ProV16.1 and V16.2 or my host OS (Win10 latest). I cannot power off the guest OS or close it without rebooting my host PC. This did not occur with the same VMs with V16.0 or prior.
