Workstation Pro 17.6 extremely slow on Windows 11 23H2

[mascf]

After upgrading from Workstation Pro 17.5.2 to 17.6 my VM is painfully slow to respond to anything, even a right click in the guest takes a long time to respond.  The guest and host OS version are the same, Windows 11 23H2.

[louyo]

Is it affecting the host?

What does task manager show (more details) for host and guest? Perhaps the VM is paging, or the host OS is paging (use perfmon)?

[mascf]

The slowness only affects the Guest not the Host.

[mascf]

The slowness never occurred with any prior version of VMware Workstation
and nothing has changed on the host or the guest. Workstation Pro was
upgraded from 17.5.2 to 17.6, it's just 17.6 that's causing the slowness.

[mascf]

Uninstalled 17.6 and installed 17.5.2, this resolved slowness issue.  I'll wait for version 17.6.1 before I'll update again.

[Dave Tudor]

Same issue with 17.6.1

[mascf]

There's no paging happening and all resources are low utilization. The
host has 64GB RAM and the guest is allocated 16GB RAM. As this never
occurred prior to upgrading to 17.6 this is an issue with this version of
Workstation Pro for Windows 11 23H2 guests only. Doesn't happen with older
Windows 11 guests or Windows 10 guests. At times the slowness for the
Windows 11 23H2 guest is crippling and there's still very low utilization
on the system.

[kasper]

Did you check the Windows event logs on both host and guest?

[mascf]

I gave up on this issue and reinstalled 17.5.2 and that resolved the
slowness issue. So many people are having multiple issues with 17.6. Rule
of thumb for all software is never install any release that ends in 0, it's
full of bugs. I'm not upgrading again until they release 17.6.1.

[Dave Tudor]

I experienced exactly the same. Reverting to 15.5.2 fixed it as well. Likewise I'll wait for 17.6.1.

[Dave Tudor]

Tried 17.6.1 but exactly the same issue. Begs the question what the point was. 

[Karan Malhotra]

I have the same behavior with VMWare Workstation Pro 17.6 and guest OS Windows 11+ Windows 10. Screen tearing when moving windows + sluggish input and missed keys when I type quickly. Its a disaster. I will downgrade later today. Such a waste of time.

[Jaroslav Cihal]

I had to return on 17.5.2. Upgrade 17.6 is unusable.
I lost a lot of valuable time with this update.
Do not install 17.6. version.

[Dodge DeBoulet]

Also downgraded to 17.5.2 and the performance level returned to normal. Before downgrading, I tried disabling side channel mitigations and saw immediate improvement, but it didn't last.

Lets hope that our new virtual overlords figure out what's going on and get it fixed...

[piggyz]

+ 1

17.6, for me, it is not that slow, then it messed up CPU and power states, so it act weird sometimes. I have to say I didn't try Windows guests, then with Linux guests it happen the virtual machines freeze when not in use and ALWAYS when the machine is running and you put the host in hybernation (I didn't try standby); when you resume the session, you can find your running guests freezed or extremely slow. In that case you can suspend them and when you resume them they become responsive again. In the case they freeze under load, you just can turn them off and still in this cases they messed up with real hardware (like blocking keyboard) until you kill them.

Reverting to 17.5.2 everything is back to normal.

Reading the 17.6 changelog I can see they mostly just removed things and also they supposedly solved a slow issue on windows hosts for user mode. I think - IMHO - maybe this caused all those timing problems I experienced with 17.6, they probably messed up with emulated cpu power states.

Hope they solved, then this first realease completely made under the broadcom name is disappointing, IMHO.

[tieske]

I'm having the exact same thing! For what it's worth, I'm having an Ultra 7 155H CPU.

[stanhelp]

I'm getting the same issue with host Ubuntu 20.04 and guest is Windows 11 Pro version 24H2.  My host CPU's are maxing out every minute.  I'm going to try to go back to 17.5.2 to see how this works. VmWare 17.6.0 is very disappointing.

Update: After upgrading to 17.5.2 shortly after the above post no more freezes on the Windows 11 Pro guest.

[stanhelp]

I uninstalled 17.6.0 and used 17.5.2 it worked better then started freezing again.

I then reduced the number of CPU's on the guest from 16 to 4 and it got slightly better but not by much.

Here are the host and guest specs.

Host Specs:

Name        : Precision 5770
Vendor        : Dell Inc. (Dell Computer, www.dell.com)

-BIOS-
Date        : 08/06/2024
Vendor        : Dell Inc. (Dell Computer, www.dell.com)
Version    : 1.27.0

Processor        : 12th Gen Intel(R) Core(TM) i9-12900H
Memory            : 65519MB (8156MB used)
Machine Type        : Notebook
Operating System    : Ubuntu 20.04.6 LTS (Dell)
Date/Time        : Wed 09 Oct 2024 01:46:48 PM MDT
-Display-
Resolution        : 8960x1440 pixels
OpenGL Renderer    : Mesa Intel(R) Graphics (ADL GT2)

Guest VM Specs:

Window 11 Pro

Version 24H2

2 processors and 2 cores = 4

Memory 16GB

Network adapter NAT

Display 8GB (recommended) 

3D Graphics is Off

[Philipp Seifert]

We had the same issue and the situation improved for us when running VmWare Workstation as administrator. This is only a workaround and it should not be run as admin because of security risks, but not being able to use the VM at all is worse

[Dhairya Tomar]

mascf and other users who are seeing this issue, please share the processor details of the Host machine where slowness is observed.

mascf Please share support bundle of the affected VM where slowness is observed using Help->Support->Collect Support Data

[Wayne Lefrancois]

atleast you have it. I am still trying to get the upgrade file to upgrade to it. Can anyone assist me with that ?

[Dodge DeBoulet]

Processor    11th Gen Intel(R) Core(TM) i9-11950H @ 2.60GHz   2.61 GHz
Installed RAM    128 GB (128 GB usable)
System type    64-bit operating system, x64-based processor
Edition    Windows 11 Pro
Version    23H2
Installed on    ‎12/‎30/‎2022
OS build    22631.4169
Experience    Windows Feature Experience Pack 1000.22700.1034.0

[mascf]

I gave up on 17.6 and reinstalled 17.5.2. The slowness only impacted the
Windows 11 Pro guest VM and not the host.

HOST Specs:
Processor 13th Gen Intel(R) Core(TM) i9-13900K 3.00 GHz
Installed RAM 64.0 GB (61.7 GB usable)
System type 64-bit operating system, x64-based processor
Windows 11 Home Version 23H2
Installed on ‎2024-‎01-‎10
OS build 22631.4169
Experience Windows Feature Experience Pack 1000.22700.1034.0

VM Specs:
Processor 13th Gen Intel(R) Core(TM) i9-13900K 3.00 GHz (2 processors)
Installed RAM 16.0 GB
System type 64-bit operating system, x64-based processor
Windows 11 Pro Version 23H2
Installed on ‎2024-‎09-‎11
OS build 22631.4169
Experience Windows Feature Experience Pack 1000.22700.1034.0

[Dhairya Tomar]

mascf Requesting you to share support bundle of the VM where slowness is observed using Help->Support->Collect Support Data

[Bill Maxwell]

Adding my system detail. Primary issue is lagging keyboard entry and have seen "ghost" windows when closing apps in the guest since V17.6 was installed.

Continuing use is identifying additional sluggish response in addition to the keyboard lag issue. 

Device specifications

Processor Intel(R) Core(TM) ¡7-10750H CPU @ 2.60GHz 2.59 GHz

Installed RAM 16.0 GB (15.7 GB usable)

System type: 64-bit operating system, x64-based processor Pen and touch support with 10 touch points

 

•• Windows specifications

Edition Windows 11 Home

Version 23H2

os build 22631.4317

Experience Windows Feature Experience Pack 1000.22700.1041.0

[Marc Antheunis]

please check task manager of the host: is the vm itself running in efficiency mode?

[BERNARD MARTRON]

Hello,

I have a performence issue with lastest version of processe from adler lake.

Try this to disable vmware execution on efficency core. (don't understand why this is not alwaerdy solve in release).

 

To activate

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

liste the activation

powercfg /powerthrottling list

 

to desactivate

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

[BERNARD MARTRON]

Try this 

Activation

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

 

List des activations

powercfg /powerthrottling list

 

Desactivation

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

This disable efficency core for vmware workestation.

[mascf]

I tried that and it made zero difference.


On Thu, Oct 10, 2024 at 7:05 PM BERNARD MARTRON via Broadcom <
[e-mail]> wrote:

> Try this Activation powercfg /powerthrottling disable /path "C:\Program
> Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe" List des...
> [image: Broadcom] <https: community.broadcom.com>
> VMware Workstation
> <https: community.broadcom.com vmware-cloud-foundation communities community-home digestviewer?communitykey=fb707ac3-9412-4fad-b7af-018f5da56d9f>
> Post New Message <[e-mail]>
> Re: Workstation Pro 17.6 extremely slow on Windows 11 23H2
> <https: community.broadcom.com vmware-cloud-foundation discussion workstation-pro-176-extremely-slow-on-windows-11-23h2#bmdc4ec541-1380-48dc-b1d8-0192752952a6>
> Reply to Group
> <[e-mail]?subject=re:+workstation+pro+17.6+extremely+slow+on+windows+11+23h2> Reply
> to Sender
> <https: community.broadcom.com vmware-cloud-foundation communities all-discussions postreply?messagekey=dc4ec541-1380-48dc-b1d8-0192752952a6&ListKey=1b0a16ce-2127-4fae-a840-018f5da56726&SenderKey=fc95ea62-82da-4fef-a11d-0191d72e3885>
> [image: BERNARD MARTRON]
> <https: community.broadcom.com network members profile?userkey=fc95ea62-82da-4fef-a11d-0191d72e3885>
> Oct 10, 2024 7:04 PM
> BERNARD MARTRON
> <https: community.broadcom.com network members profile?userkey=fc95ea62-82da-4fef-a11d-0191d72e3885>
>
> Try this
>
> Activation
>
> powercfg /powerthrottling disable /path "C:\Program Files
> (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe"
>
>
>
> List des activations
>
> powercfg /powerthrottling list
>
>
>
> Desactivation
>
> powercfg /powerthrottling reset /path "C:\Program Files
> (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe"
>
> This disable efficency core for vmware workestation.
> *Reply to Group Online
> <https: community.broadcom.com vmware-cloud-foundation communities all-discussions postreply?messagekey=dc4ec541-1380-48dc-b1d8-0192752952a6&ListKey=1b0a16ce-2127-4fae-a840-018f5da56726>*
> *Reply to Group via Email
> <[e-mail]?subject=re:+workstation+pro+17.6+extremely+slow+on+windows+11+23h2>*
> *View Thread
> <https: community.broadcom.com vmware-cloud-foundation discussion workstation-pro-176-extremely-slow-on-windows-11-23h2#bmdc4ec541-1380-48dc-b1d8-0192752952a6>*
> *Recommend
> <https: community.broadcom.com:443 vmware-cloud-foundation discussion workstation-pro-176-extremely-slow-on-windows-11-23h2?messagekey=dc4ec541-1380-48dc-b1d8-0192752952a6&cmd=rate&cmdarg=add#bmdc4ec541-1380-48dc-b1d8-0192752952a6>*
> *Forward
> <https: community.broadcom.com vmware-cloud-foundation communities all-discussions forwardmessages?messagekey=dc4ec541-1380-48dc-b1d8-0192752952a6&ListKey=1b0a16ce-2127-4fae-a840-018f5da56726>*
> *Flag as Inappropriate
> <https: community.broadcom.com vmware-cloud-foundation discussion workstation-pro-176-extremely-slow-on-windows-11-23h2?markappropriate=dc4ec541-1380-48dc-b1d8-0192752952a6#bmdc4ec541-1380-48dc-b1d8-0192752952a6>*
>
> -------------------------------------------
> Original Message:
> Sent: Sep 09, 2024 03:21 PM
> From: mascf
> Subject: Workstation Pro 17.6 extremely slow on Windows 11 23H2
>
> After upgrading from Workstation Pro 17.5.2 to 17.6 my VM is painfully
> slow to respond to anything, even a right click in the guest takes a long
> time to respond. The guest and host OS version are the same, Windows 11
> 23H2.
>
>
>
>
> You are receiving this notification because you followed the 'Workstation
> Pro 17.6 extremely slow on Windows 11 23H2' message thread. If you do not
> wish to follow this, please click here
> <https: community.broadcom.com higherlogic common unfollow.aspx?userkey=15699092-d28e-48f1-a321-0191d8298360&sKey=KeyRemoved&ItemKey=fa4a8d9e-897d-41d2-a3e0-0191d837eff4>.
>
>
> Update your email preferences
> <https: community.broadcom.com go.aspx?c=Preferences§ion=email> to
> choose the types of email you receive
>
> Unsubscribe from all participation emails
> <https: community.broadcom.com higherlogic egroups unsubscribe.aspx?userkey=15699092-d28e-48f1-a321-0191d8298360&sKey=KeyRemoved&mClass=Social>
>

[Joe Tan]

Just received an upgrade to 17.6.1 today 12/Oct (WIndows 11) but keyboard entry remains sluggish as before.

[Marc Antheunis]

i have the same issue with 1 vm, win10 client os, i have another similar, w10 who does not has this behavior

[Dave Tudor]

Seeing that 17.6.1 is now out I gave it a go. Same deal as with 17.6 for me. Video judders and stutters. 

------------------------------
Dave T
------------------------------

[emerson67]

17.6.1: same issue on Win10 guest on Win10 host. Both x64 22H2.

Host AMD 5950X, 128GB RAM, 16GB VRAM

Guest 32GB RAM, 2GB VRAM

No effect on issue:

• Disabling 3D acceleration
• Updating VMware Tools

[Joshua Pilkington]

17.6.1 does not fix the video slowness issue.

The video slowness is weird.  It appears that not all of the screen is updated, even though drawing updates are taking place in the background.  I can test this by performing a right-click and then immediately moving the mouse to the right and down.  If I click and move immediately, I will immediately see the right click menu appear.  If I don't move the mouse or move the mouse in the opposite direction, the right click menu will not appear until I move my mouse over where it should be.

There is a temporary fix (other than downgrading).  Simply disable 3D acceleration for the VM (while it is powered off) and it is responsive again like it was in the previous version.

[Dave Tudor]

Just a note that I've found the same as Joshua with the video tearing. The screen refresh is out of whack. 

This is with Linux Mint guest. My guess would be it will be the same with all guests OS.

[Marketing Xeorg]

I am having the same screen refresh issues on Ubuntu 24.04 guest. This is with 3D acceleration on a Windows 10 host.

[Shibdas Bandyopadhyay]

Does it get fixed when you disable 3D acceleration. Can you please attach and log and also see post 35. Thanks!

[Marketing Xeorg]

The sync issue only happens with 3D acceleration. The VM runs normal with 3D acceleration disabled.

When I add "mks.enableDX12Presentation=FALSE" and "mks.enable3d=TRUE", the sync is fixed. So it seems like the DX12 presentation is making the trouble.

[Shibdas Bandyopadhyay]

Can you please attach the logs (vmware.log and mksSandbox.log) ? Also try with 3D on but mks.enableDX12Presentation=FALSE in the vmx config file (while it is powered off)

[Shibdas Bandyopadhyay]

I have looked at the logs sent and nothing jumped out. Couple of things

1. The missing screen update when you do something and it does not seem to appear on screen until you somehow cause a refresh is something that has been reported internally. We are looking into it.
2. There seems to be multiple issues in this thread with different hosts and guest. So for all who is seeing a slowness on a windows host with 3D on but the slowness goes away when 3D is turned off, can you please do the following while keeping 3D on and report back?
   
   1. 1. mks.enableDX12Presentation=FALSE and check if things improve.
      2. mks.enableVulkanRenderer=FALSE and check if things improve.

[Marketing Xeorg]

Host: Windows 10 22H2, Ryzen 7 5800H, NVIDIA 3060M

Guest: Kubuntu 24.04, X11, KDE

VMWare: 17.6.1 build-24319023

3D Acceleration + default => missing screen update

3D Acceleration + mks.enableDX12Presentation=FALSE => normal screen update

3D Acceleration + mks.enableVulkanRenderer=FALSE => missing screen update

[Iveco Martin]

When hotfix? You cant even use UAC on any Windows VM anymore. Do you guys dont have Q&A ?

[Stefano Ska]

Me too.  Uninstalled 17.6.1, reinstalled 17.5.2 and works again.

mks.enableDX12Presentation=FALSE and mks.enableVulkanRenderer=FALSE did not work for me.

[Fese]

Hello,
I have the same issue as all the others in this thread with 17.6.x. None of the proposed VMX configuration options fixed my problem. At the end I was downgrading again to 17.5.2, which is working like expected. With all newer VMWare versions the input is very slow. 

I have Windows 11 23H2, Intel i7-10875H CPU and Nvidia Quadro T2000 GPU.

My Guest VM is a Ubuntu 24, but it also occurs with previous Ubuntu versions. 

This is very frustrating, as it seems this topic get's no attention and there are many other threads describing the same problem. 

[mascf]

I've now completely given up on 17.6.x until they come out with an absolute
fix for the repeated blue screen crashing. It was stable for a while after
disabling 3D Acceleration and today it was back to crashing after a few
minutes, totally unusable. I reinstalled 17.5.2 and it's stable again.
Broadcom needs to put more effort into resolving this issue!

[kasper]

The sad truth is that not having the right hardware, not having the right hardware updates and not updating the firmware may be part of the issue.   Not VMWare.   Check yourself.

[Frank Kosztelnik]

Me too.  Uninstalled 17.6.1, reinstalled 17.5.2 and works like a charm again.

[Melvin McEvoy]

I can confirm that having tried several recommended adjustments, downgrading to 17.5.2 fixed the issue for me.

[Joe_Wulf]

Same here.  Significant slowdown of Windows and Linux VMs once 'upgraded' to v17.6.1;  Reverting back to 17.5.2 returned performance to normal.

[flox04]

Hello.

Same problem for me, solve by disable "memory integrity" option in "core isolation" on Windows 11 host. You can find help here :

https://knowledge.broadcom.com/external/article/368989/vmware-workstation-vm-does-not-start-aft.html

go to Step 5

[Richard Poulter]

Having the same problem after moving from W10 to W11. Doing any VM work is now impossible. 

W11 23H2

AMD Ryzen 9 5900HX 8 Core(s), 16 Logical Processor(s)

Done all the above tweaks except core isolation as I can't turn it off being In a NHS trust.

[thewul]

Had the same issue (Windows 10 x64) with 17.6.1.
Well, I gave it a try to re-install 17.5.2. Completely uninstalled 17.6.1 including registry settings and everything (using an uninstaller, that removes all leftovers). Installing 17.5.2 did not work. Used the full version, tried three times, each time, at the end , install was 'rolled back', immediately after "Installing virtual network drivers". 
Tried 17.5.0, same issue.

Does anyone out there have a suggestion?

Thanks.

[Dave Tudor]

Just a suggestion. Have you checked in Device Manager. Are the VMWare network items still listed? You might want to show hidden as well.

------------------------------
Dave T
------------------------------

[thewul]

Yes I did, but then again, I am not sure as to what is 'correct' or 'missing'...

Leaving out the 8 'WAN Miniport' entries the Network Adapter list is as follows:

--
Bluetooth Device (Personal Area Network) #2
Broadcom 802.11ac Network Adapter
Intel(R) Ethernet Connection (2) 1218-V
Intel(R) 1211 Gigabit Network Connection
Microsoft Hosted Network Virtual Adapter
Microsoft Kernel Debug Network Adapter
Microsoft Wi-Fi Direct Virtual Adapter
Microsoft Wi-Fi Direct Virtual Adapter #2
RAS Async Adapter
VMware Virtual Ethernet Adapter for VMnetl
VMware Virtual Ethernet Adapter for VMnet8

-

VMware Network is set to NAT, which corresponds with VMNet8 in my case(?)

[Bill Maxwell]

Unfortunately, this solution as well as others suggested made no noticeable difference on my VM :-(

[Robert Tyler Woods]

Shutting down the VM, going to settings and disabling 3d Acceleration fixed it for me. 

[Robert Tyler Woods]

I had like a 120ms input lag that is now gone/fixed by disabling 3d acceleration when the VM is shutdown in settings. Running on latest version 17.6.2

[Marc Antheunis]

seems to work for me to at this moment... i also had lockups of the entire vm (visually the vm didn't respond anylonger, but in the background it did - found that out by suspending en starting)

[Marc Antheunis]

version 17.6.2?

[Bill Maxwell]

I had tried turning off 3D acceleration back in October without success. So thought I would try it again and for whatever reason it eliminated the keyboard entry lag this time.

I do still have memory integrity enabled and do not have any of the "mks.xxxxxx" entries as suggested by others.

So for now 17.6.2 appears to be working as expected without the keyboard delay - fingers crossed....

[Joe Tan]

Hello,

For Windows version I'm unable to locate the 17.6.2, the highest version listed is 17.6.1. Any idea why? , how long ago since 17.6.2 came out?

Thanks

[RaSystemlord]

It didn't.

[AEglinton]

It most certainly did as I'm running it. However don't pin your hopes on that, it doesn't resolve the problem.

[Dave Tudor]

I must admit that personally I've come to the end of trying workarounds for these issues with 17.6.x. There is something fundamentally broken. It is just not on that Broadcom should have not fixed this yet. In fact even worse that 17.6.2 was touted as a fix but seems just as broken. I'll be sticking to 17.5.2 until a true fix is released (if that ever happens).

------------------------------
Dave T
------------------------------

[Dodge DeBoulet]

Dave, have you upgraded to 24H2 yet? I'm on 23H2 with Workstation 17.5.2 but Windows is nagging me about upgrading to 24H2. I had the same issues with Workstation 17.6.1 as everyone else in this thread and don't see a need to "upgrade" if 17.5.2 will work OK on 24H2.

[Joe_Wulf]

I followed steps 1-5, as recommended here:  https://knowledge.broadcom.com/external/article/368989/vmware-workstation-vm-does-not-start-aft.html
I've then tested installation of the latest VMware Workstation update (17.6.2), again with painful slow-down experienced; and no change to the pain based on enabling/disabling 3D-accelleration.  I've a Centos7 VM which has been a long-term, consistent, stable workhorse for many years of development; as well as many other VMs, which include RHEL8, RHEL9, CentOS8, CentOS9, and Fedora39/40/41, among others.  Though I've not exhaustively ran-through testing every one under 17.6.2, those which I have--experience the slowdown problem.
I've reverted back to 17.5.2 and again all works as it should.  I also re-enabled memory integrity under core isolation as I didn't like disabling that in the first place; then rebooted.

My primary desktop is a custom-built system, Dual-XEON SuperMicro motherboard (X11DAi-N), a pair of Silver 4214 CPU's with 256GB RAM, and my primary drive is a 1TB M.2 NVME (970 EVO).  My Windows 11 Pro is at 24H2, build 26100.2605; last updated Dec 24th.
I can relate to the expressed sentiment of being at the end of my rope with testing 17.6.2 any further.   This is twice now I've gone down that road and its been a waste of my time.  I'll remain at 17.5.2 while awaiting a stable version (18.x??) to be released and even then, I'll wait for wide-spread expressions of 'this one works', before I do adopt it.

[RaSystemlord]

I have this thread "VMware and Win 11" from 18 days ago.

There I have tested with 17.5.2 with DEFAULT options of Win 11 Pro Host and several Guest OS'ses, Windows and Linux. I found no problems on Intel platform. Computer was newly built Asus ROG Strix with a fast Intel i5. Just the prompts and suggestion laid out by VMware needed to be followed. Certainly, I did not have any AD group policy or ANY of these changes as suggested for 17.6.x versions. I did not try nested virtualization.

With that observation, you could check what is different with you and then try to deduct why it doesn't work for you ... or maybe it does work for you personally, but I'm talking now in generic terms since many here doubt that it never works.

[ZackInMA]

I've tried all the recommended solutions and the latest versions of VMWare Workstation Pro just do not perform on modern processors and Win11. The network performance was egregiously bad. 

I ended up switching hypervisors from VMWare to Hyper-V, which, for my work, is working out well. I was running Windows and Linux guests in VMWare and they both ran like dog doodoo. In hyper-V they're Johnny Blaze fast. 

It just is what it is..... I tried to get the old version of VMWare, but Broadcom is now denying me access to download the software I paid for and denying me access to my license entitlement. I filled out the web form, saying I should have an account, license, etc. even provided receipts. They still denied me!

F- this company... 

[RaSystemlord]

I don't know what this company is doing and why, but ...

If you follow my postings, you can see that there is nothing wrong with Win 11 or x.Ubuntu-versions running on different Intels - from 15 years old to brand new. There is also nothing wrong with Win 10 and a couple of years old Ryzen.

Version is always 17.5.2, licensed.

If you follow my postings, you can get it "from anywhere". Latest try-out by me was from archive.org.

I haven't done ANY forking of any of the OSses (of course with Linux you have to do something for compiling). And I DO know what AD (Domain) is and in one of my tests I used that in Win 11 Client. However, that was my own Domain, created in Win S 2022 by me, where I had done nothing to prevent VMware from running.

There are many other configurations and architectures - but those are meaningless for me. I hope somebody else, who has those, would test them ... in the correct way.

But yeah, whatever your configuration is, it might be something where VMware does not work - however, based on your writing 17.5.2 would work.

[Dhairya Tomar]

mascf Requesting you to upgrade to WS 17.6.3 and update if the issue still persists

[Dave Tudor]

All the iterations of 17.6 have a variety of issues (including the one you are experiencing). There are have been endless threads about this over the last 6 or 7 months none of which seem to come up with a practical solution. My feeling is the issues are in the guts of the product and there are no solutions other then Broadcom sorting this out at source.

Unless you have a specific requirement for 17.6 you can save yourself hours of grief simply be reverting back to 17.5.2. If there is a specific requirement then you'll just have to take the hit on the issue you've got.

Sorry to be the bringer bad news.

------------------------------
Dave T
------------------------------