Vmware 17 Pro very slow on Windows 11 22H2

[Ferko]

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. 

[Maksym Roshchyna]

Probably HyperV is installed/pre-configured. 

In order to turn off Hyper-V mode, run the following command at the host in windows command-line with Administrator privileges:

bcdedit /set hypervisorlaunchtype off

Reboot the system to activate your changes.

If you want to go back to Hyper-V mode again, then you can enable it like this:

bcdedit /set hypervisorlaunchtype auto

Note that you also might have to disable Memory Integrity.

Windows Security -> Device Security -> Core Isolation details

[TomBrody]

I have the same issues - it did not fixed the problem on my computer.

[Wilko01]

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

[andrezanna]

Buddy here is right. This solved my issue.

[Maksym Roshchyna]

Windows Server especially might experience such issues. 

[biser]

Hi,

Windows Security -> Device Security -> Core Isolation details

Thanks! This worked for me.

 

[Imtiaz Uddin Mohammed]

Hello,

Am facing the same issue with VMware workstation 17. Looks like it has some serious issues and a bug fix MUST be released.

Any operations we do with 4 or more VMs running will spike the CPU immediately to 100%. This will result in VM hangs.

My specs: 

Running the base OS as Windows Server 2016 Datacenter with latest update, 160 GB RAM and many CPUs.

I hope VMware releases a patch or an update for this. 

[giopebero]

Same here. Win 11 22H2 + VMware 17 Pro. My Win 10 VM is very unresponsive. Even clicks have a 2 seconds delay. Very strange.

[Cloedu72]

I have exactly the same issue. Reverted  now to 21H2 and everything works fine.

- disabled core isolation and HyperV

[v0id1]

In my opinion disabling security features is not a solution, especially when computers are managed centrally and there is no option to turn it off. VMware team should work with Microsoft to solve this issue.

[giopebero]

If you are experiencing very slow performances with Alder Lake CPUs, I solved the issue using

powercfg /powerthrottling disable /path "C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe"

ref. https://community.broadcom.com/vmware-cloud-foundation/communities/community-home/digestviewer/viewthread?MessageKey=f3f8b2ec-09ee-40e7-a5c3-deb3a1929211&CommunityKey=fb707ac3-9412-4fad-b7af-018f5da56d9f#bmf3f8b2ec-09ee-40e7-a5c3-deb3a1929211

[jshu1]

Holy moly, the power configuration change helped...   I'm dumbfounded.  It's still not like before the Windows 11 update, but it's a significant improvement.  I'll test it out some more and see how it goes.

[Buggin]

This solved my issue. Workstation 17.0.1 was previously unusable on my Win11 Pro (Version 10.0.22621 Build 22621) running with a i7-12700H. Now it appears to be working correctly. Thanks !

[Crasucks]

What did you do to solve the issue?

[noxware]

that helps me perfect.

Performance from ssd Nvme is now 4 to 5 times higher !

 

Thanks

[SteveKK]

My Windows 11 VM running under VM Workstation Pro v17 on a Windows 11 guest had been painfully slow to use. I had already applied the settings suggested by maksym007, but it was still just as slow. Adjusting the power throttling setting as suggested by giopebero has made a huge difference to the performance.

I would suggest applying both of these changes to see if it fixed you performance issues.

Regards,
Steve

[giopebero]

I wouldn't change Hyper-V settings, I fixed with the power throttling only. Obviously waiting for an official fix by vmware team.Regards.

[SteveKK]

Having tried Hyper-V to see if that performed better, I'll be sticking to VM Workstation as it is so much more functional. I needed to disable Hyper-V on my system to get the Intel VT-x/EPT enables for my VMs. I will not miss Hyper-V functionality.

 

Regards,

Steve

[leondavi]

Worked for me, Windows 11 22H2, Intel I7-12700

[jasonsenior]

Never would have believed it, but the power throttling change worked on my Surface 5 laptop. Thanks!

[Anderson_Sidney]

You earned your pay today!  Take the rest of the week off!  Thank you!

[smileyofoz]

Yes this helped me too.  It went from being basically unusable to very zippy indeed.  Thank you!

 

[netravert1]

I was experiencing extremely poor performance on a brand new Microsoft Surface Pro Laptop running Windows 11. Disabling Hyper-V did not resolve my issue. Running the following command per  resolved my issues. Thank you  .

powercfg /powerthrottling disable /path "C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe"

[brunofernandez1]

thx! that worked for me with VMWare 17 Pro an Win11 (Host and Guest)

[Zorgluk]

Thx dude it fix the issue for me !!

[TSDGHOST]

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

[ouroboroskys]

i created an account just to say that the powerthrottling fix solved it! so grateful after trying what seems like forever to figure out a solution.

[VMware Community Member]

Thank you.  Thought i waisted money on my new computer.  

[VMware Community Member]

Fixed very slow network troughput for me.
Was around 7-8 MB/s.
After this powercfg change it went to +100MB/s

• VMware® Workstation 17 Pro 17.5.0 build-22583795
• Microsoft Windows 11 Pro 23H2 (10.0.22631.3085)

Thanks!

[Martin Olsson]

Thanks!

My corporate Win11 laptop can't run VMware Workstation in traditional mode (VT-x can't be enabled in the settings).
Every VM was running sloooooooow.

Then I executed the powercfg command and the VM is fast. Yay! :-)

Simple test:
In a powershell in a Win11 guest VM I run:
      Measure-Command {
        $array = New-Object System.Collections.ArrayList
        for ($i = 0; $i -lt 5000000; $i++) {
          [void]$array.Add($i)
        }
        $array.Sort()
      }


This takes roughly 44 seconds.

Then I stop everything, execute the powercfg command on the mother host and start the VM again.

Now the same test takes 3 seconds!!! (the same time it takes when running directly on the mother host)

[Ferko]

Vmware has just released Workstation Pro 17.0.1. Has anyone, experiencing the same issue with W11 22H2, tried if it is still so slow?

 

Thanks.

[jshu1]

It's still slow.  I'm checking for updates on Windows and VMware everyday hoping they found a fix.  No luck.  VMware doesn't make it easy to contact them for support either.  I'm not happy that I can't create a ticket with them without paying for it.

[Crasucks]

I have, my Win11 VMware Workstation pro 17.01 is uselss due to being too slow. I can no longer develop on my VM's. I am thinking of scrapping VMware if I can't get this fixed. 

[VMware Community Member]

Sir 

I have the same problem.  I have disabled Memory Integrity. I have done the hyper V thing also.  

I cannot get it to run at a normal Speed

This is only with VMWARE 17 Server.  If I move the VM to VMplayer then the VM runs just fine.

Stumped   

 

If I don't get this fixed I am going to Oracle's product.

 

[_Phobos_]

Just git a notification of your reply.  
i don’t know if it is applicable for you but did you check this thread?

look for my reply, maybe it will help.

https://communities.vmware.com/t5/VMware-Workstation-Pro/Windows-10-slow-and-laggy-in-VMware-Workstation-17/m-p/2959854/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufExGRUNWN0JXWEJXWkQ1fDI5NTk4NTR8U1VCU0NSSVBUSU9OU3xoSw#

[Sardesai62]

I am now using 17.5.x and yet the same problem.

[Technogeezer]

---

 wrote:

I am now using 17.5.x and yet the same problem.

---

If you have a 12th Gen Intel Core cpu or newer, you must at a minimum change the power throttling settings on the vmware-vmx.exe file as noted in this thread.

powercfg /powerthrottling disable /path "C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe"

If you don't do that, you're guaranteed to have poor performance. You must re-apply this after you apply any upgrades/updates to Workstation.

For 17.5, you should also add

keyboard.allowBothIRQs = "FALSE"

to the .vmx file of the VM to avoid some other issues.

 

[Sardesai62]

Thanks for the response. I tried the two things suggested. However after this change to VMX file

keyboard.allowBothIRQs = "FALSE"

 it worked the first time but after that VMWare WS Pro found the VMX file corrupt. i had to remove this and restore the machine.

[Crasucks]

I am running Win11 and Vmware 17.01,  my VM's are useless now.  I wish I statyed with VMware 14.  

I can no longer develop using my VM's

[biowizard]

I got 17.0.1 (while I was still on Windows 10 Pro), but reverted to 16.(latest) when the Chess Titans program in my Win 7 VM crashed VMware altogether. Not my most important programme, I know, but this told me that WS 17 was not yet ready for prime time.

Then I upgraded (just over a week ago) to Windows 11 Pro. After sorting out some initial device driver issues, everything was running smoothly. Everything, that is, apart from my VMs, which not so much ran, but walked. With a limp.

Playing around with numerous settings, and scanning the web for solution, the ONE trick that DID appear to work, was disabling the Core Isolation's "Memory Integrity" setting. Switched off, and following a restart, my VMs were very much back up to speed.

The obvious question is, am I happy to leave this security feature in Windows 11 Pro disabled, just so my VMs run at full speed? Tricky one, but then again I've survived the past several years running Windows 10 (and before that, WInodws 7), without this particular protection.

I just wonder how to stop the warning exclamation mark on the task bar tray if I do decide to turn this feature off permanently ...

Brian

[DonElder]

I have the same problem. I have Windows 11 22h2 and just upgrade to 17.0.1 to be able to install latest Win 11 Dev in a VM. Now that and my other VM Windows Server 2022 run so slow they cannot be used. Tried the power throttling fix but it did not help my system

[Cloedu72]

Are there any news, info or at least a rumor from VMWARE about this topic?
=> VMWARE at least gives us the sign that you are working on it!

[SAngeli]

Hi,
just wanted to let you know I have the same issue. Windows 11 Pro 22H2 and latest ver. of VMware Workstation 127.0.1 build-21139696

It is crazy working with this Hypervisor. Impossible to work.
Please VMware support: give us a fix, please!

Thanks

[biowizard]

Thanks to all who are reporting these same issues.

Simply, for now, I have reverted to VMWare 16, which is not ideal, and also is a lot slower on Windows 11 than ever it was on Windows 10.

Such a shame - up until now, I have been very impressed with VMWare, both Workstation on the PC and Fusion on the Mac.

Now, for the first time, I'm beginning to consider alternative solutions.

Please, VMWare, wake up and respond to these issues!

Brian

[TomBrody]

I found the solution for my PC setup here: https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-16pro-on-alder-lake-system/td-p/2880327

-->

Just tell Windows to not "optimize" the application. With that setting the process will never be moved on e-cores when backgrounded.
Tested with W11 22H2

powercfg /powerthrottling disable /path "C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe"

 

powershell commands as admin:

https://www.youtube.com/watch?v=U8EGr6Ex7OI

100% Fixed VMware Workstation Slow Performance Issue Windows 11/10

Step-By-Step Guide:
1) Open a administrator PowerShell or CMD and type "bcdedit /set hypervisorlaunchtype off".
2) Search for "Core Isolation" and turn it offf.
3) Restart your computer

Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Hypervisor

 

--> sad that  this helpful solution is not comming from the VMWare support which I contacted and also payed for....

[Xavier101]

Hi,

I think, by installing VMware tools the problem was fixed for me.

Can someone else confirm this because I am not sure.

[Pierre Schellner]

• VMware Workstation slow when HOST Windows 11
• powercfg /powerthrottling disable /path "C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe"
• To change the power mode, select Start > Settings > System > Power & battery. For Power mode: "best performance"
• keyboard.allowBothIRQs = "FALSE"
• Disabling Hyper-V and everything made a small difference, but after disabling memory Integrity my vm was back at full speed.
• Installed Vmware Tools [fixed it]

[Ferko]

Hi all,

 

thanks for all your proposals. I have fixed it for myself so that I have checked how many P Cores I have on my CPU and then set some lower limit on the virtual guest. With maximum number of P Cores for the guest it was unstable and slow. But with half of P Cores for virtual machine it behaves now as before.

[Roger Hanna]

Here's where I go to get current builds of Windows 11.  https://uupdump.net/.  I use the Windows 11 dropdown and select 22H2 (Moment 3) which BTW is the only current distros (even moreso that what Microsoft shows on their website)  It will not throw you into the Insider as their Canary and Dev versions will (I've tested multiple vm's with each option and the Moment 3 builds are the best) I then used this build  

Windows 11 Insider Preview 10.0.22624.1610 (ni_release) amd64 within the Moment 3 on my live machine WITH Vmware 17 Pro running and 1 VM of Windows 11 Enterprise (for testing) and the overall performance of both the main machine as well as the VM's improved over 20%  

[Felix213]

This can‘t be it…

Disabling Hyper-V and everything made a small difference, but after disabling memory Integrity my vm was back at full speed…

it‘s okay when it works, but it feels wrong to disable safety features just for my workstation 17 to work.

[DavidSvoboda007]

The first, I have switched off Hyper-V for the booting Windows 11.

But by disable Power Throttling works for me, returned speed for my VMWARE 17 Workstation Pro images. 

 

powercfg /powerthrottling disable /path "C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe"

 

[AlexTram]

This worked for me as well. I spent two days wandering what happens and how to fix it. I was fiddling with the power option in the UI of Windows but it wasn't working. This fixed it in a moment:

 

powercfg /powerthrottling disable /path "C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe"

 

[WinArchitect]

The powercfg command fixed mine. My VMs are moving right along now. Thank you!

[hellerim]

I experienced the same symptoms. But disabling power throttling for VMware Workstation did not change much. However, somewhere I found the advice to update to the latest nVidia graphics driver (my machine has an RTX2050 GPU). (The source is FIX: Computer is Slow after Windows 11 22H2 Update.) In fact, this works fine, my vms now run smoothly. The driver I'm using now is NVIDIA Studio Driver – WHQL (driver version: 536.23, published 2023, June 14). Hope this helps at least those having nVidia GPU in their machine. I find this solution preferable since I don't need to change anything of the machine's security settings.

Apparently, this solved also the reported problem of downloading large files for me (Microsoft Confirms Windows 11 2022 Update Causes Performance Issues When Copying Large Files). When I setup one vm recently with MS Visual Studio (download payload of more than 7 GB) this took an eternity of more than one hour, but downloading an update today (0.5 GB), after installation of the new driver, run fast as usual - merely one minute. I suppose for quite a while I've been the only user on my VDSL2 vectoring line since my neighbours appear all to have switched to glass fibre. That is why I exclude busy connections as a cause for low download rates.

[gbohn]

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?

[hellerim]

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

[shaunhey]

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.

[ChHi]

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"

[RJKREIDER]

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.

[VMware Community Member]

Thanks!!!!

The setting

monitor_control.disable_apichv = "TRUE"

fixed the issue.

I also tried not adding

mks.enable3d = "FALSE" and I see no difference since I already disable 3D acceleration from the VMWare GUI so probably setting mks.enable3d to FALSE in not necessary

[PeKor]

Hi, I don't know if this is helpfull but let me tell: Windows 11 Guest was painfull slow after Updating. I tried to go back with my snapshots. At least I reached the first one - a fresh installed Win11. I could do a update without problems. But: "a snapshot later" (40 Minutes later to the very first one): Win11 goes slow down again. My guess: KB5027231 from 2023-06. I could remove it on two snapshots and Win11 was ok again. Try this: Try NOT to get Win11 Update KB 5027231 (Disable Internet or use a update blocker (sordum tools) OR: Try to deinstall it. And let me know (Looking for confirmation)

[_Phobos_]

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

[TQLeaman]

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.

[WazzyD]

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.

 

 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

 

 

 

 

 

 

[TQLeaman]

Thank you for saving me the effort.

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

[TSDGHOST]

THX Saved my Day

i Saved this Batch in my Cloud  

[PatrickHume]

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

[RDPetruska]

---

 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!

[PatrickHume]

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 

[RDPetruska]

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

[PatrickHume]

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!

[RDPetruska]

Well, right in the paragraph you posted is the statement "on each Mac computer that you own or control" - there it is in black and white.  They do not allow their software to run on non-Apple hardware!  And, the only way to make Workstation for Windows/Linux load an Apple OS-based VM is to illegally hack/modify the software!  If you want to run an Apple OS in a virtual environment on an Apple computer, there is ALREADY a product which allows this - Fusion!

[Technogeezer]

And if you re-read the Apple bounty program T&C, the safe harbor provisions referring to  “applicable Apple license provisions which provide that a user of Apple software may not copy, decompile, reverse engineer, disassemble, attempt to derive the source code of, decrypt, modify, or create derivative works of such Apple software“ is language taken specifically out of section 2 N of the Apple macOS EULA.  This says nothing about overriding EULA provisions in sections 2 A, B, C, D, J (and maybe others) of the EULA that specifically state that macOS is only licensed to run on Apple-branded computers. 

 

[MikeLowrie]

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

[TQLeaman]

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.

[johnymutton]

I was having the same problem. Luckily I came across this article that solved it for me. Basically run vmware workstation in administrator mode. There is other stuff, but that was the big improvement for me.

https://williamlam.com/2023/11/heads-up-performance-impact-with-vmware-workstation-on-windows-11-with-intel-hybrid-cpus.html

Hope that helps you

I have a 13th gen intel hybrid but this is supposed to work on 12th gen too.

[Sardesai62]

I have exactly the same problem. I am breaking my head for the past several days and unable to get it working. I am neither able to do what I want with VMWare and I am also not able to do my normal work as I am tied up and totally worked up to make VMWare work.

[tjpsnj]

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?

------------------------------
TJPSNJ
------------------------------

[nicknack661]

Hi, same problem here. However, that was caused by a policy change from my company, that removed my admin rights. So the difference for me was pretty evident since the beginning and I started using VMWare as Admin as soon as that happened.

However, there is still an issue even when running as Admin and I realized that it can still be the same cause only recently, after 2 years I have this problem. I guess you can try because I think it is a general problem, since I had it on my previous laptop and I have it on my new laptop, that has just one month.

Try this: start your VM as admin and check performances are fine (having a small performance test is the best option, I use a complex query on Oracle, which is installed on my VM, which when things are fine requires only 0.22s to execute). Then, SUSPEND the VM (do not shut down) by using the "pause" button of VMWare Workstation. Close everything and restart your computer. Resume the VM. Now the performances of the VM dramatically drop (for example, the same query as above takes from 5 to 7 seconds). The only way I have is to shutdown the VM, close VMWare, open it again and restart the VM.

Anyone noticed it? Any clue on the solution? My VM is filled with services and shutting it down every time that I shut down or restart my laptop requires 20 minutes for me to recover the current status of my work. In order to use it I put my laptop to sleep or hybernate it, in that case there are no issues with the suspended VM. However, that is not always possible (for instance, when restarting because of Windows updates).

[nicknack661]

Quick update. I confirm that simply restarting the VM is not enough. Shut down is required. However, there is no need to restart VMWare.

[ZackInMA]

I tried everything to get VMWare Workstation Pro to run well on Windows 11. I had no Hyper-V or Windows virtualization components installed. I did the BCEdit thing, disabled core isolation, side channel loading, etc. disabling the E processor cores. Nothing, absolutely nothing, worked. I spent days trying to find a solution, to no avail. I even tried different versions of VMWare Workstation Pro. They all ran like trash. 

I was trying to run Kali in a VM and it just ran like dog doodoo. So did my Windows 11 VM. I didn't have this egregiously bad performance on my 2 year old machine, also Windows 11. Just the brand new one. So it does seem like something related to new hardware. But - nothing fixed it. Despite machines being practically identical from an OS and VMWare config standpoint. 

I ended up having to abandon VMWare. I uninstalled it and installed and went with Hyper-V. The Hyper-V performance blew VMWare out of the water - even on my older machine that I thought had been fine... Plus, I didn't have to disable a bunch of security just to get it to work. Now I can also use WSL if I want as well. 

Hyper-V has come a long way, and I don't think VMWare has been keeping up. For those struggling on Windows with VMWare, like I was.... I would suggest that now - Hyper-V is the way.... It may take some getting used to if you're new to it. In the end you will be glad you made the move.... 

As for running Kali specifically in Hyper-V, OffSec now published the virtual machines on various platforms, ready to import, with all the tools, extensions, etc. already baked in. Literally download it, run it, and you're cooking with gas in minutes.... 

[backend@dat]

Yeah but that's not because Hyper-V is brilliant now but because MS did everything in W11 to throw out alternatives like VMware Workstation...

[ZackInMA]

Regardless of the reason for VMware's egregiously poor performance in Windows 11, it is a reality in which we currently live. It has been for some time now as well - a year+ based upon this thread. 

Hyper-v suffers no such performance issues. It runs circles around VMWare Workstation. Regardless of the reasons of such, these are the facts. If you want to have a good and productive experience on Windows, then hyper-v is now the way.

You can be pissed at MS if you like - for whatever reason. But based on this discussion, which involved disabling security, disabling Windows virtualization features, and disabling the use of CPU cores on modern processors, it is clear to me that VMWare just has not been keeping up with the evolution of the technology upon which their software runs. 

That was a business decision VMWare made, and those chickens have now come home to roost. As someone who has used VMWare for years, and paid for Workstation Pro before they made it free for personal use, it saddens me to see it come to this. But it is what it is. Honestly, I'm done trying to fight it with hack around band aid "fixes". How much investment is VMWare going to make into modernizing Workstation now that it's largely free? IDK, but it's been a year+ and here we are, still suffering the same issues. That tells a story. You don't have to like it, but it is what it is. 

Hyper-V is easy to use, runs circles around VMWare's performance, and in 2024, has full support for any GuestOS - Linux distros of choice included. Hyper-V has come a long long way since its release on Server 2008 R2. If you haven't given it a look recently - you should. It has its nuances and differences. But you get acclimated to them quickly.

I'm glad I made the move and will not be looking back. When it comes to virtualization on Windows, Hyper-V is the way. 

[goldeneye_007]

While I agree with some of your sentiments, I have an office full of Workstation, paid licenses, near the end you simply come across as a Microsoft shill. Windows performance on Workstation has always been lackluster and as you have stated I do not expect it to get better but rather worse with extensive delays between releases. In a setting such as ours, the host/base OS is Linux and our guests are Windows so Hyper-V is not going to work. We run Workstation mostly for convenience and interacting with ESX, but since we have now abandoned ESX due to Broadcom shenanigans, Workstation is now less compelling. Virtualbox or KVM will suffice but we will continue to use Workstation until it becomes as anticipated, utter shite. In this environment it is the second tier virtualization providers business to lose, nobody is sticking with VMware voluntarily.

[ZackInMA]

I'm not a "shill" for anybody and I do not know that throwing around insults advances the conversation. You use what works for you and go with god. This thread is for people struggling with running VMWare Workstation on Windows 11. You, by your own description, are not doing that. Your banter thereafter contributes nothing to the conversation or to helping users with the aforementioned struggle. All you did here is **** oxygen out of the discussion. Don't do that. If you have something to contribute to the users here in the struggle - then do that. That would be helpful. But if all you offer is insults and irrelevant talk, do everyone here a favor and save it.

[goldeneye_007]

Right, because recommending Hyper-V is constructive. Got it.

And if you 'are not looking back', why are you in the Broadcom forum getting support for Workstation?

Doesn't add up. 

[RaSystemlord]

"I tried everything to get VMWare Workstation Pro to run well on Windows 11."

Well, there is no try, just do. Maybe 22H2 is too old for current versions, who wants to use it anymore?

I tried with 5 different OS'ses, 2 Linux, 3 MS, and with 24H2 VMware 17.5.2 works just fine without doing anything about it - just following what VMware suggests during runtime.

Just install 24H2 and don't do any of those things and VMware 17.5.2 will probably run just fine.

As for promoting uSoft products on a VMware Forum, perhaps not the best of ideas - but yes, I'm sure Microsoft development is very competent. After about 25 years they could make a demanding software like Notepad better. It must have required lots of their brainpower to do that. Well, without going into details, it still has just one minor clitch - perhaps people cannot get their work saved with its braindead default workflow - who has important information in a text file anyway - so I think it is just fine.

Other than that uSoft has been slowing down IT development for some decades, in some other things like: .bmp format, wav format, boot procedures, loading OS procedures, file system availability - just to name a few areas. 

As for having a virtualization platform, no Windows is good, use Linux, like Kubuntu or any other brand. Having said that Win 10 has worked just fine on decent hardware, if you can run it with uSoft defaults.

[ZackInMA]

The problem with your post is that - nothing in it is true. 

I'm running the latest version of Windows 11. VMWare Workstation Pro 17.5 and 17.6 both run like poop on a skillet. I did EVERYTHYING suggested to fix the issue, and nothing worked. 

You make assumptions about how things should run for me without knowing anything about what hardware I'm running it on, etc. 

It's easy to say "use Linux" to run VMs. But in reality, many of us need to run Windows on our primary workstations because we work in an enterprise that runs on this thing called Active Directory. Maybe you've heard of it? It's pretty common. 

I'm glad Linux is easy for you to run your VM environments on. But for the rest of us, it's not always that easy. Suggesting your solution is a practical one size fits all for everyone suffering here - is ignorant. 

The simple fact is that VMWare hasn't been keeping up with the evolution of the Windows OS, or the hardware it runs on. That is how we got to where we are today. 

[tjpsnj]

Wow, that's a lot to unpack.  Which message are you replying too?

I do have a linux box running.  I downloaded Dabian to learn python.  clunky a fair amount to the time.  I find it difficult to run VMTools and have it fix random video issues.  

As for windows I run 10 and whatever 11 keeps itself updated too.  Which processor do you have?  What video card in your machine?  On the host can you turn off any windows energy saving features?  You need to run in high performance mode to start with.  You may also be under some limit set by AD in your environment.  Much can be imposed by security.  Which in now way id VMWare's fault.  

I do agree VMWare often seems like they dropped the ball.  However, the product is full of settings and so is windows.  You can make it work if you take the time.  You may need more administrative access to alter settings.  If you cannot access those it is frustrating but nobody's fault.

------------------------------
TJPSNJ
------------------------------

[tjpsnj]

I have a 12th Gen Intel(R) Core(TM) i9-12900KS chip.

 

I used # 12 and #79.  #12 turns of the energy saving stuf that does not save energy or promote productivity in any way.  #79 turns off all of the "performance" cores in the processor.  Performance cores are pretty much a half core simulating a full core with more "energy saving" features built in.  Disabling use of the performance cores by any host running as a virtual machine had the most effect.  #12 makes the performance smooth, not fast sometimes slow fo no reason the next.

 

#12

powercfg /powerthrottling disable /path "C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe"

 

#79

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"

------------------------------
TJPSNJ
------------------------------

[Pierre Schellner]

I did all these things to fix it at least. The "VM-Ware Tools" did help at the end.

• VMware Workstation slow when HOST Windows 11 23H2
• powercfg /powerthrottling disable /path "C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe"
• To change the power mode, select Start > Settings > System > Power & battery. For Power mode: "best performance"
• keyboard.allowBothIRQs = "FALSE"
• Disabling Hyper-V (again)
• Installed Vmware Tools [fixed it]

[Marc Marcsson]

Hi everybody,

There is just one pragmatic thing to do to solve the "slow"-issue of Broadcom Workstation Software. 

-> You must accept that Broadcom has fucked up Vmware Workstation; which now should be called Broadcom Workstation.

This includes all the VM-slow and VM-graphics issues

Solution:

--> uninstall Broadcom Workstation Software

--> uninstall Windows Hypervisor Platform -Addon from Windows

--> reboot

--> Download Vmware Workstation Software V 17.5.1 (the latest, before Broadcom took it over)

--> Install

--> All issues are gone !

Have a nice day !

[RaSystemlord]

Sure, but I think 17.5.2 works well, too. I have a business version of it with zero problems.

I understand that an Upgrade is something that you should do often and with a new computer you always take the latest version to start with ... those being 17.6.x versions.

That is the normal way, for many. But what is REALLY the reason to use them now, meaning 17.6.x versions? People think that they are somehow a REQUIREMENT.

By whom? They are not required for the latest Win 11. Are they required by the corporation ICT department? If so, educate them. Use a version that is known to work and do not spend time with versions that "should" work. ICT world is full of things that "should" work, but never do.

[Marc Marcsson]

Please don't do me. 

This is not a normal behavior.

Software should always be updated to the latest version because... many things.

I have spent hours (if not days) reading all the recommendations and trying the get Broadcom Workstation Software running as it should; but at the end gave up.

Broadcom Workstation Software is fucked up as I said allready. Only solution is to keep good old Vmware Workstation Software. If you do not want to change to Microsoft Hyper-V.

Allthough I might will do this step; and break completely with good old software, because of Broadcom.

Recommendations I can give to anybody:

• Don't use Broadcom Workstation on a laptop.
• Don't use Broadcom Workstation if you have an old CPU.
• Don't use outdated software, it has bugs.
• Don't use Broadcom Workstation, it's fucked up.
• Don't complain. And don't expect good support. 

-> see where this leads ?

Use the Broadcom Workstation Software only on Workstation with Xeon CPU that has the superior hardware support for virtualisation!

Now it all makes sense; doesn't it ?

[RaSystemlord]

Yes sure. I don't understand how you can get a disagreement of my direct agreement what is typically "normal behavior" with software.

You can obviously do what you recommend. You can also do:

• use 17.5.2 with Win 11 with regular Intel i5. I have a thread here where I tested 5 different OS's with this. Although briefly.
• use 17.5.2 with Win 10 and Ryzen 9 on a laptop. Everything works just fine. I have used something like 30 different VMs during the last calendar year.

I understand that there is a myriad of other possible combinations, which I haven't tested. And then there is nested virtualization, which is of no interest to me. However, some things that you say that don't work, are not true, generally speaking.

My main point was that 17.5.1 is not the latest that works.

You can also take some other virtualization software, which have their own problems, but those need to be dealt with elsewhere. Don't think for a second that the new Win 11 schemes don't affect other virtualization outside Microsoft world.

[Marc Marcsson]

Your mind seems wandering around, though keep repeating the same words.