_Phobos_'s Posts

Maybe you forgot to stop the VMware SVGA helper service? I'm just saying, for many this will be obvious. But since I also temporarily made this mistake for like 10 seconds. I can imagine that in some cases it might be overseen although it is mentioned in more posts. Disabling this service (prevent it from automatically restarting.) is not enough. (Unless you restart your guest maybe.) You must also stop it manually. When the service is still running it will not have the positive effect on expanding to multiple monitors! Can anyone tell me what are the cons of disabling this service? Which functionalities may drop?    

I had the same problem. Alle the usual fixes you see did not help me a lot!   I found out that within VMware workstation pro 17 there may be problems with the guest Hardware for version 17. While creating a new virtual machine you can choose the hardware compatibility. Now I use (on a win11 host) win10 and win11 installed within VMware WS 17 but I created the guests with hardware compatibility version 16.2.x. For both win10 and win 11 this speeds up my guests with a factor of 6-7! see my earlier posts: https://communities.vmware.com/t5/VMware-Workstation-Pro/Vmware-17-Pro-very-slow-on-Windows-11-22H2/m-p/2989094#M182933 https://communities.vmware.com/t5/VMware-Workstation-Pro/Windows-10-slow-and-laggy-in-VMware-Workstation-17/m-p/2948560/highlight/true#M179563 I hope this helps you. as for the answer to your question. I think the cause is the VMware guest hardware V17! It is much slower than V16.2.x

Hi Graham,   Thx for the kudo. If you want to run WIn11 on VM workstation 17. You can do it also by making a virtual machine with Hardware compatiblity 16.2.x! It When selecting the windows version WIN11 it will tell you that it will not work, but it does work fine for me now for 2 days. If you want to try it see this post. https://communities.vmware.com/t5/VMware-Workstation-Pro/Vmware-17-Pro-very-slow-on-Windows-11-22H2/m-p/2989094#M182933 I hope I've helped someone with this. Maybe I try to start a new topic to give this more attention.

Hi there, I tried all of the above when installing Win11 on VMware workstation 17 when I just installed my new computer in january this year. Nothing worked for me, so I settled with running WIN 10 on WS17 with hardware compatibility WS16.2.x. See my post https://communities.vmware.com/t5/VMware-Workstation-Pro/Windows-10-slow-and-laggy-in-VMware-Workstation-17/m-p/2948560#M179563 Now I tried win11 again, still none of the above worked for me. BUT now the good news!!!!!! I SOLVED IT... Just try the VMware HW compatibility WS16.2.x for installing WIN11 as a guest in WS17!! I figured, if win 10 is running better on HW16.2.x why not win11? and it does!! how to do it? Just follow this old link how to install win11 on VMware WS 16 : https://us.informatiweb-pro.net/virtualization/vmware/vmware-workstation-16-15-virtualize-windows-11.html Be aware that: You can choose Microsoft windows version 11. It will trigger a warning that HW16.2 is not compatible with win 11 but just continue. After creating the new virtual machine you will see that acces control is already encrypted and the TPM hardware is also added because you chooese the version win11. (It will ask you how to ecrypt the data just after you selected it.) And that's it!!! I have my own benchmark tool with a VBA running in excell and on HW version 17 it takes 54 seconds to complete. With HW version 16.2.x it completes in 9 seconds in win11. I hope you will profit from this tip. Let me know if it helped you!!

Hi, I just started with win11 host and workstation 17 this year. I noticed that win10 guests are slow when installed with hardware compatibility = workstation 17! I ran an excell VBA code with some database queries as a benchmark and it took about 75 seconds to finish. When I downgraded the HW compatibility of this Win10 guest to workstation 16.2 the same macro took only 9 seconds to finish!!!! 7 times faster on the same guest on the same host only changing the guest Hardware compatibility So for me I stay working on WS17 with WIN10 guest @ Compatibility = WS16.2!! I stay away from running a win11 guest (needs HWcomp = WS17) this is also a verry slow combo for me.  (Even though I speeded all up with regard to disabling Hypervisor mode ULM an all other win11 tweaks.)