Unable to edit VM settings VMware Workstation Pro 17.0

[alantcy]

Hi,

On Workstation Pro 17.0

Whenever I click 'Edit virtual machine settings', I get the following error and the whole application crashes.
VMware Workstation unrecoverable error: (vmui)
Exception 0xc0000094 has occured.

Please help.

[EricL1]

Same issue here for the VM that were upgraded from 16 to 17

No issue for VM created with 17 directly

Host is Windows 11; Guest is Ubuntu

Error in Windows Event each time I try to open settings for Ubuntu VM:

Faulting application name: vmware.exe, version: 17.0.0.34456, time stamp: 0x6374a93e
Faulting module name: vmwarewui.dll, version: 17.0.0.34456, time stamp: 0x6374a8f2
Exception code: 0xc0000094
Fault offset: 0x001bae05
Faulting process id: 0x0x1394
Faulting application start time: 0x0x1D8FEDD604E0F22
Faulting application path: C:\Program Files (x86)\VMware\VMware Workstation\vmware.exe
Faulting module path: C:\Program Files (x86)\VMware\VMware Workstation\vmwarewui.dll
Report Id: effeed1f-ac53-4578-9139-3d52f0983bb6
Faulting package full name:
Faulting package-relative application ID:

[ShuaiY]

This solves my issue, even for an encrypted win11. Thanks!

[Sandro-B]

---

@sunjwvista wrote:

Just add cpuid.coresPerSocket = "1" to your VMX config file.

---

bingo!

[amclaren]

Just another confirmation - yep, I am also seeing exactly this problem after upgrading to Workstation 17.0. Intensely annoying.

I'll try the workarounds suggested in this thread; but I sure hope this is fixed in 17.0.1

[lturkin]

I have had the same issue as well.   After reading this post, I was able to solve the issue by following the steps in this blog.   Here is the steps that I found work:

1) Downgrade the Hardware to Version 16.2

2) Change the number of processors and cores to 1

3) Upgrade the Hardware to 17.0

It worked.   In addition, I have changed the processor settings to 1 processor and 4 cores.   As well, I have also changed the OS from Windows 10 x64 to Windows 11 x64.   It's still working, and I would say that its solved.   Thanks everyone for the assistance.

[MikeMcC399]

I found a useful answer to this issue in https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-Workstation-17-Crashed-when-edit-a-v.... It confirms what has already been discussed here, provides a link to instructions to downgrade hardware compatibility and says that they are working on a fix.

[Squareball]

Yet again you have to wonder what's going on with the quality of testing of new VMware products.

So no one, not one person, changed the settings of a VM after upgrading the VM version to v17?

[shanemccook]

The fix, according to VMware Technical Support is;

1. Downgrade the HW version to 16.x
2. Increase the number of cores per processor to 2 and keep the processor as 1
3. Upgrade the HW to 17.x
4. Change the processors and number of cores as necessary.

You can also resolve the issue by adding the following to your VMX file.

cpuid.coresPerSocket = "1"

[ssill2]

Per sunjwvista,

Adding cpuid.coresPerSocket = "1" to your.vmx fixes it.

[ShaneWelcher]

Reducing the VM to 1 core before changing from VMware 16 to VMWare 17 allowed me to upgrade with no issues then once I upgraded it I increased the cores again & am fully able to edit the virtual settings now.

Thanks for the help guys

[AbdulrahmanNA]

I did change on Hardware Compatability into 16.2.x and works fine now. 

[NielsGrove]

The official answer to this issue is in another community entry:
https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-Workstation-17-Crashed-when-edit-a-v...

The temporary "solution" is to downgrade the VM capability level to 16.2.x...

[tecnogenco]

Super! thank you

[MikeMcC399]

I updated to VMware Workstation 17 Pro 17.0.1 and the problem no longer occurs.