VMware Communities
tymchenko
Contributor
Contributor
Jump to solution

Crash on opening VM settings

1. Vm state is turned off

2. RMB ->Settings

Actual result

Crash of application

Log Name: Application
Source: Application Error
Date: 23.11.2022 12:19:32
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: HyperV01.domain.com
Description:
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: 0x2bc8
Faulting application start time: 0x01d8ff250ecdc9e6
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: 2ecca1ac-5adf-4f1e-9d71-ebf13c0d3b06
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-11-23T10:19:32.781331000Z" />
<EventRecordID>1704924</EventRecordID>
<Channel>Application</Channel>
<Computer>HyperV01.domain.com</Computer>
<Security />
</System>
<EventData>
<Data>vmware.exe</Data>
<Data>17.0.0.34456</Data>
<Data>6374a93e</Data>
<Data>vmwarewui.dll</Data>
<Data>17.0.0.34456</Data>
<Data>6374a8f2</Data>
<Data>c0000094</Data>
<Data>001bae05</Data>
<Data>2bc8</Data>
<Data>01d8ff250ecdc9e6</Data>
<Data>C:\Program Files (x86)\VMware\VMware Workstation\vmware.exe</Data>
<Data>C:\Program Files (x86)\VMware\VMware Workstation\vmwarewui.dll</Data>
<Data>2ecca1ac-5adf-4f1e-9d71-ebf13c0d3b06</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Reply
0 Kudos
1 Solution

Accepted Solutions
RDPetruska
Leadership
Leadership
Jump to solution


@tymchenko wrote:

 

Just try to open settings of different vm's based on workstation 17 and you will get crash


There is another thread (or several) here describing the issue, with an answer by one of the developers.  They are aware, and are fixing.  Current workaround is to downgrade the virtual hardware of the VM.  See https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-Workstation-17-Crashed-when-edit-a-v...

 

View solution in original post

Reply
0 Kudos
5 Replies
tymchenko
Contributor
Contributor
Jump to solution

It is a worst support service I ever seen.

Reply
0 Kudos
Technogeezer
Immortal
Immortal
Jump to solution


@tymchenko wrote:

It is a worst support service I ever seen.



It may be that people in this forum don’t know why this is happening or have never experienced this issue. This is a user-to-user community discussion board. People here are knowledgeable, but they are not VMware’s technical support organization.

Can you provide any more details on the system you’re running this on? You appear to be running Workstation 17, but there’s little info beyond that. 

Your computer name appears to be HyperV01.domain.com. Is this computer a Hyper-V VM (seems strange that a computer would have “HyperV” in its name, that’s why I’m asking) 

- Paul (Technogeezer)
Editor of the Unofficial Fusion Companion Guides
Reply
0 Kudos
tymchenko
Contributor
Contributor
Jump to solution

No it is not hyper-v server (don't mind the name).  Repro can be easily achieved on any server OS and even home os.

Just try to open settings of different vm's based on workstation 17 and you will get crash

Reply
0 Kudos
RDPetruska
Leadership
Leadership
Jump to solution


@tymchenko wrote:

 

Just try to open settings of different vm's based on workstation 17 and you will get crash


There is another thread (or several) here describing the issue, with an answer by one of the developers.  They are aware, and are fixing.  Current workaround is to downgrade the virtual hardware of the VM.  See https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-Workstation-17-Crashed-when-edit-a-v...

 

Reply
0 Kudos
tymchenko
Contributor
Contributor
Jump to solution

Thanks!!!!

Reply
0 Kudos