VMware Workstation has stopped working!!

[samjegal]

I've updated windows 10 redstone 2 (1703 version, OS Build 15063.13), and vmware workstation 12.5.5 pro reinstalled.

But, it's not working for sometimes with the error message.

Attached event viewer error log.

And, reinstall several times vc++ redistributed packages. It's SO frustrated.

[bonnie201110141]

Hello all,

We are aware of this issue and it is identified as a bug in Windows 1703. Currently we are actively working with Microsoft to resolve the issue. Sorry for the inconvenience!

[munrobasher]

Thanks for this - although it's hard for companies to admit there is a problem, it's far better to know it's been identified as a known bug. Saves us all worrying that it's some other change on our PCs have has caused the problem.

[plumeria]

The VmWare crashes also with 12.5.7 when resuming previously stored VM (here: host = Windows 10 Pro 64bit 1703, guest = Linux). Additional problem is, that after the crash the host needs to be rebooted.

[munrobasher]

Sometimes I can open background VMs from the system tray icon and it works but like the poster above, sometimes it says it's in use and the only solution is to reboot. I guess one could considering trying to kill some VM related tasks but rebooting is safer because the inaccessible VMs are still paused before the reboot as opposed to just being crashed.

[munrobasher]

Any update on this? It's now nearly four months since the bug was reported

[bonnie201110141]

Thank you for your patience! Actually Microsoft fixed this issue in Windows 10 Insider Program build, and the next release of Windows 10 should contain this fix.

[munrobasher]

Ahh didn't appreciate that this was a bug that Microsoft introduced. That's different...

[silverlox]

Hi,

I'm running Workstation Pro 12.5.7 and have the same problem. I'm running VMware workstation in the normal Creators edition 1703 Build 15063.483

My VM's, three of them are running in separate VMware instances.

One is the Windows 8.1-1 and does not seem to have any problems

One is the normal Creators edition 1703 Build 15063.483 and does not seem to have any problems

The other one that always crashes is, has just crashed and is still live in the Library view is the latest Preview issue.

That one I cannot access, Taking Ownership does not work.

I have deleted all .lck files and still cannot open that VM

I have tried to run the VMX file but still get the Cannot take ownership.

Using the Notification icon I've used that to shutdown all VM's and then tried to re-start the relevant VM but I instantly get the VMWare Workstation has stopped working message

I cannot get the minidump as Windows states that Workstation has stopped responding.

The .lck files are back again but deleting them I'm back to the virtual mac=hine is in use and VMware has stopped working

Any suggestions?

[silverlox]

Addendum to the above.

Just tried the notification area icon, used that to access the VMWare icon, used that to "open all background virtual machines" and the failed vm is usable again

All without re-starting the host PC.

[silverlox]

Sorry forgot to add the vm is running V1703 (Build 16241.1001)

[wila]

Hey Silverlox,

You really should have opened your own thread.

Anyways, just drop to one vCPU and there's a good chance your crashes go away.

--

Wil

[silverlox]

Hey Wila

My initial comment was:--

I'm running Workstation Pro 12.5.7 and have the same problem

So unsure why I should have created yet another thread on the same problem, maybe that would be better but it seemed easier to have lots of info for the same problem.

You say use one vCPU and the problem might go away, how do you know I'm using more than one, presuming you mean one virtualCPU per VM?

Regards

Mike

[wila]

Hello,

Yes I saw your initial post and your 2 other posts.

The problem with tagging onto another thread is that quite often the original thread gets difficult to follow. Everybody puts in their own little differences and instead of making it easier to find a common denominator, it just gets more difficult.

We also don't know what 'common info' your problem shares beyond "my VM crashes" so providing more complete information about your specific issue usually tends to give the best chances for finding a solution.

I hope you also saw the post where it was mentioned that the fix will be in the next Windows Release (Re: VMware Workstation has stopped working!!)?

Meanwhile my suggestion to drop to one core was based on similar reported issues in the past with that particular Windows Release where using more than one core caused the VM to crash. That was just a guess as you had not supplied much information beyond the windows version of the VM that crashed.

--

Wil

[bonnie201110141]

Hello all,

Microsoft has fixed this issue in this KB:

https://support.microsoft.com/en-us/help/4032188/windows-10-update-kb4032188

Please try it and let us know if it does not work for you.

[munrobasher]

Update installed but not been using workstation today so later...

[munrobasher]

Looking good so far!

[thewul]

Seems this issue has been solved?
No "VMware Workstation has stopped working"-errors anymore recently.

Out of curiosity: has this really been fixed now, or have i just been lucky for a while?
If so, how?
I haven't downloaded a VMware Workstation update

Using 12.5.7 build 5813279 on Windows 10 x64 build 15063.540

=

[bonnie201110141]

This issue is fixed by Microsoft KB4032188.

[thewul]

Thanks! I did look into the updates of Windows, searching for something like 'Virtual' or VM or so, but could not find anything.

Anyway, glad it is solved.

Thanks again!

=

[munrobasher]

See a few messages above from VMware. Microsoft released the KB with lots of fixes inc. this one. One had to manually download it initially but I suspect it's now been rolled out to everyone on patch Tuesday. The fix possibly didn't specifically mentioned VMware or VMs as it was problem some sub-system changed that simply effected VMware Workstation.