Hi;

> The driver I'm using now is NVIDIA Studio Driver – WHQL (driver version: 536.23,

Going to the Nvidia driver pages today I only see a 'Game ready driver' for version 536.23.

The newest studio driver I see listed is 535.98 (at https://www.nvidia.com/Download/index.aspx?lang=en-us).

Maybe I'm just missing it (or maybe it's no longer available?).

Do you have a link to the 536.23 Studio driver page?

@gbohn: The driver I downloaded appears to not be available anymore. However, my old driver was older than 535.98 (I did not note the exact version). Since my GPU card GeForce RTX2050 does not appear on the drop down list as of today, I suppose that support for it has been dropped meanwhile. Anyway, you can select "Studio" instead of "Game ready" from their drop down list. Then, I would try the current version offered by them, i.e. 535.98, in your place. Since nVidia drivers generally seem to be high quality, I would not expect a major risk. So don't expect to create problems by installing it, and if you are lucky, this even solves said performance problems as it did for me.

Is anyone else still having occasional issues even after the powercfg change?  The powercfg change made a huge difference, but occasionally one of my VMs will start having the issue again.  If I power down the VM and power it back up, then it is fine.  Same exact symptoms, CPU at 100% inside the VM with no single culprit, etc.  Lately I've noticed that it seems like the issue happens when the VM I'm using was resumed from suspend and not fully shut down.  I've tried to leave it sit for hours (or even overnight) to see if it will work itself out, but only powering it off and back on will fix it.

Thx dude it fix the issue for me !!

Did you try already the latest 17.0.2 version?

Additional you can try to add these rows in your .vmx

monitor_control.disable_apichv = "TRUE"
mks.enable3d = "FALSE"

mks.enable3d = "FALSE" did it for me.  I noticed the GPU > 80% (Intel UHD 630 version 27.20.100.8783 on Windows 10 22H2 with VMWare Workstation 17.0.2)... never put the two together until your hint.  Thanks!

ETA: Disabled Accelerate 3D Graphics in the VM settings also.  Works for my situation.

Had the same without HyperV installed. I removed player / workstation 17 and installed version 15. Is now running perfectly

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-Worksta...

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...

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!!

Thanks for the help here.

My Linux Host and Windows 11 Guest setup was suffering strange stutters when in Visual Studio and just scrolling through code.

(Other VM guests on the same host were fine.)

Changing the client settings to disable the Hypervisor / Core Isolation (not Power Config as that is for a Windows Host machine) worked to resolve the issue. I re-enable each to see which was at fault and it's the Core Isolation of Memory that was doing it.

I get there are security reasons when disabling such things but in my case everything is done natively on Ubuntu, except Visual Studio so I'm happy with the compromise.

Thanks again.

I battled with this issue for a long time and slowly built up tweak by tweak until I combined everything into a bat file that I run after a Windows update (Because Windows has 0 respect for your settings and changes them back to default after every little update). Use the below and save as .bat and run as administrator and your slow VMs should be a thing of the past. You'll notice that virtualized-based security will show as not enabled and your VMs won't even have the side channel mitigation option anymore.

You will need to download the dgreadiness_v3.6 tool and modify the below to the path where you save it. Run the file and you might see an error from the dgreadiness tool depending on if settings are controlled by registry or GPO but it will finish. Restart and you will be prompted to hit the Windows key to confirm disabling virtualized security.

@Echo off 
powershell.exe Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Hypervisor
powershell.exe Disable-WindowsOptionalFeature -Online -FeatureName "Microsoft-Hyper-V"
bcdedit /set hypervisorlaunchtype off
dism /online /disable-feature /featurename:Microsoft-hyper-v-all
bcdedit /set vsmlaunchtype off
bcdedit /set '{0cb3b571-2f2e-4343-a879-d86a476d7215}' loadoptions DISABLE-LSA-ISO,DISABLE-VBS
powershell.exe C:\dgreadiness_v3.6\dgreadiness_v3.6\DG_Readiness_Tool_v3.6.ps1 -Disable
powercfg /powerthrottling disable /path "C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe"
exit /b

Thank you for saving me the effort.

(As I too expect Microsoft to ignore my settings and reset this again in the future! )

I upgraded the VM to HW version 17 which fixed the issue.

I upgraded all 7 of my VM Guest machines when I moved to WorkStation 17 but the problem with the Windows 11 guest didn't happen straight away, it was running fine for several months before the problem kicked in.

None of the others - (Windows 10, Windows Server 2019 and various Linux flavours) have experienced the problem.

Maybe you've had better luck and whatever the issue was (or is) has been resolved without us ever actually getting a response from VMWare or Microsoft about what they broke!

For reference:

The Host OS is Ubuntu 22.04LTS running on a Ryzen 5900x (12 Core) with 64GB RAM and the Windows 11 guest runs with 1 CPU (4 cores) and 16GB RAM. (Used for Visual Studio based development).

The host is solid state storage only (NVMe) and the guest has a pre-allocated 100GB disk and VMWare is configured to allocate 32GB RAM on startup for running guests and not virtualize memory at all.

**bleep** YES

you made my Day it works 

Disable HYPER V and using your line and it WORKS  
i Have a I9 13gen on Dell Precision Workstation Notebook

THX Saved my Day

i Saved this Batch in my Cloud  

power fix after a system reboot also seems to work for those who may use MAC OS on VM Ware 

---

@PatrickHume wrote:

Does anyone have a fix for this that would work for a Mac OS image running inside VM Ware 17 on Windows?

I'm running Mac OS Sonoma, in the latest version of VM Ware 17, but it's painfully slow and almost unable, I can't disable hyper-v functionality as a developer I need that for Docker 

I tried the power throttling fix helped a little but its still painfully slow. All the fixes mentioned are for Windows OS and a not Mac OS , I am hoping someone has one that works for a Mac image as although I can use Docker to run Mac OS it currently only supports Ventura and not Sonoma

thanks in advance 

 

 

---

Not at all - it is a violation of Apple's licensing to run their OS on non-Apple hardware.  So we cannot help you here as VMware could get into legal trouble.  Plus the only way to even attempt to run macOS VMs on Workstation is to hack the software... so you've come to a vendor's site admitting you modified their software and are asking for help!

There are plenty of solutions that do just that,sickcodes, hackintosh to new but a few and there are some on GitHub that are open source and widely supported, The many, many videos or tutorials on how to get Mac OS running on VMware also suggest its clearly commonly done. From what I saw in this post no one from VMware actually helped solve the issue rather it was the community who had to resolve it with one post even saying what a shame no one from VMware bothered to help or respond so I was asking the community not the vendor and assuming the only way to make MAC OS work on VMwaree is to hack the software is presumptuous, as there are other ways and someone PM me a solution so clearly it was worth asking but thanks for the helpful reply 

I'm not saying it is or is not commonly done.  I am saying it is illegal, and nobody will help you on here.

but they did and Apple explicitly states that they do not consider a violation of the EULA, under the terms of their program, provided that you participate in the program in good-faith, that you do not disrupt Apple services, and that you do not access anyone else’s data

also 

You can run up to two (2) additional copies or instances of the Apple Software
within virtual operating system environments on each Mac Computer you own or control that is
already running the Apple Software, for purposes of: (a) software development; (b) testing during
software development; (c) using macOS Server; or (d) personal, non-commercial use. source: https://www.apple.com/legal/sla/docs/macOSCatalina.pdf

also 

As long as you abide by the Apple Bug Bounty rules, you can conduct security research on Apple systems and are entitled to Safe Harbor. Apple Pay's upwards of 100k for bugs!

https://developer.apple.com/security-bounty/

So  It is not exactly illegal in a in a strictly legal sense provided you get the OSX installer from your own mac. It is just a violation of the user agreement and you will get no support nor will you get any guarantee that you will be able to use all the services or that all features will even work

Also, I could be running a Windows VM on a Mac and in that Windows VM I could be running a Mac VM is side of it, for any number of reasons, in which case wouldn't be illegal as it still be on mac hardware so claiming it's illegal is again presumptuous .just saying!