Britwick
Contributor
Contributor

Crash after upgrade to Workstation 10.0.6-2700073

Jump to solution

Upgraded to 10.0.6-2700073 this morning, and Workstation crashes as soon as I start it.

Details are in the attached ZIP file:

- screen shot of crash

- screen shots of three application event log entries at the time of the crash

- vminst.txt which was updated at the time of the crash

The .xml file mentioned in one of the event log entries does not exist on my system.

I'm running on a Windows 8.1 host, and have been running previous versions of Workstation for over a year on this PC.

PC is a Lenovo Thinkpad T503

I'm going to uninstall this version and try re-installing the previous version.

Anyone any ideas about the cause of these problems?

Tags (3)
1 Solution

Accepted Solutions
aryour
Contributor
Contributor

Had the same crashing issue after upgrading and after some research I found this post that gives some details why the crashing is happening.

To fix the issue simply do the following;

Search for the file libcurl.dll in your VMware Workstation installation folder.

(I found 3 instances on my windows 8.1 machine)

C:\Program Files (x86)\VMware\VMware Workstation\x64

C:\Program Files (x86)|VMware\VMware Workstation

C:\Program Files (x86)\VMware\VMware Workstation\OVFTool

Make a copy of the files in the first 2 folders having a modified date of 28/04/2015

Replace with a copy of the file in the 3rd folder (\OVFTool) with modified date of 04/02/2015

Start up VMware Workstation

This fixes the issue and no uninstall or reinstall required, I've tested it and have not experienced any issue.

I take no credit for this as the issue was discovered in the post below which has more details on the exact issue.

http://blog.rewolf.pl/blog/?p=1167

View solution in original post

22 Replies
Britwick
Contributor
Contributor

Successfully uninstalled 10.0.6 and re-installed 10.0.5, this version runs for me.

My colleagues have no problems with 10.0.6 (all installed from the same binary).

The only difference we can see is I'm on a Windows 8.1 64bit host, and they are still on Windows 7.

0 Kudos
TheSquire
Contributor
Contributor

I also upgraded to 10.0.6 this morning and it is also crashing with the same error.

I'm on Win 7 Sp1 64-bit

0 Kudos
Bonsucesso
Contributor
Contributor

It occurred to me too.

Only worked when performed as "Administrator".

It is not the solution, but it worked.

0 Kudos
MikaVirtanen
Contributor
Contributor

Hello, I can confirm this problem. Yesterday tried to install with build-in upgrade, then remove - full download/install - still crashed on start.

Error message was related to libcurl something...

Reinstalled previon version.

My Windows version is Win 7 Pro 64-bit on HP Elitebook 8770w

0 Kudos
marbffm
Contributor
Contributor

Looks like I was taking part of the same beta test as you all? 😞

Just updated to 10.0.6 from inside VMware Workstation on my Lenove W530 running Windows 8.1 64bit and VMware Workstation does not start at all.

After uninstalling 10.0.6, reboot and installing a seperately downloaded 10.0.6 everthing worked fine for me until VMware workstation crashed in the middle of my work and could not be started again 😞

The error is related to libcurl.dll according to the system aplication log

0 Kudos
ChrisThomasIdap
Contributor
Contributor

Me too. "VMWorkstation has stopped working" crash after following the built-in upgrade notification. Running Windows 8.1 64bit. I'm downloading VMWare 10.0.3 from the MyVMware account, but I can't find anywhere to download the previous working version 10.0.5. Any ideas? Hope the 10.0.5 VMs are backwards compatible with 10.0.3. Can't do any work until this is resolved!

0 Kudos
TheSquire
Contributor
Contributor

I had the same thing but found the 10.0.5 download here

https://my.vmware.com/web/vmware/details?productId=362&downloadGroup=WKST-1005-WIN

ChrisThomasIdap
Contributor
Contributor

You sir, are a genius! Downloading as I type. Thankyou so much! I'll be downloading 'updates' manually from now on, so I can always revert to the previous version, rather than be left with a broken application!

Update:

Uninstalling 10.0.6 and replacing with 10.0.5 works just fine. Phew! Thanks again!

0 Kudos
Syntux
Contributor
Contributor

VMware 10.0.6 seems to be unstable and not well tested. Upgrading from Windows 7 64 Bit first failed from within VMware 10.0.5. Afterwards I succeeded to fully download and install 10.0.6, but now I am getting a "VMware has stopped" error. I guess I rather go back to 10.0.5 ...

0 Kudos
aryour
Contributor
Contributor

Had the same crashing issue after upgrading and after some research I found this post that gives some details why the crashing is happening.

To fix the issue simply do the following;

Search for the file libcurl.dll in your VMware Workstation installation folder.

(I found 3 instances on my windows 8.1 machine)

C:\Program Files (x86)\VMware\VMware Workstation\x64

C:\Program Files (x86)|VMware\VMware Workstation

C:\Program Files (x86)\VMware\VMware Workstation\OVFTool

Make a copy of the files in the first 2 folders having a modified date of 28/04/2015

Replace with a copy of the file in the 3rd folder (\OVFTool) with modified date of 04/02/2015

Start up VMware Workstation

This fixes the issue and no uninstall or reinstall required, I've tested it and have not experienced any issue.

I take no credit for this as the issue was discovered in the post below which has more details on the exact issue.

http://blog.rewolf.pl/blog/?p=1167

View solution in original post

1006sucks
Contributor
Contributor

Confirmed on my Leonvo T440p.

Have advised everyone at my company not to upgrade to 10.0.6 (we all use Lenovo).

0 Kudos
inetbas
Contributor
Contributor

Hello,

I upgrade from VM workstation 10.0.5 to 10.0.6 and after that my VMware Workstation software didn't start but crashed with a fatal error.

I did a reinstall of VM workstation 10.0.6 and then it started.  However.....

I disovered i.e. that the Virtual Network Editor only has the 3 default VMnets.  I had about 7 specific VMnets configured.

All gone 😞

Brgds,


Bas.

0 Kudos
torti42
Contributor
Contributor

The replacement of libcurl.dll fixed the issue for me as well.

Dell Latitude E6530 running Windows 7 Pro 64bit.

Thank you so much, saved me a lot of time!

0 Kudos
Britwick
Contributor
Contributor

Aryour fix worked for me.

I've marked it as the correct answer.

0 Kudos
christianschroe
Contributor
Contributor

Thanks for citing rewolf's blog solving a pretty pervasive problem.

Wondering, how it could escape VMware's thorough testing before releasing the update, and also why that issue is unknown in the KB.

:smileyplus:

0 Kudos
Bascisco
Contributor
Contributor

Hello,

I am wondering that too.  Also all My VMnets were gone. See other post I did on that when you add VMnets it crashes again. That was my main trigger causing the 10.0.0.6 crashes.

I am back on 10.0.5 and I had to rebuild a couple of things.

Brgds,


Bas.

0 Kudos
fa2lerror
Contributor
Contributor

PLease be aware that the recommended fix to roll back DLL is not the best solution. you should1st attempt to use the newer dated file making all three DLLs the same current patched versions not a prior revision. the act of making the DLL version the same is most likely the true fix not stepping back to a broken version. chances are the old/flawed DLL was missed during the update while the other 2 where successfully updated.

different resolution than above to similar crashing after upgrading from 10.0.5 to 10.0.6. My problem was fixed by unchecking (disable) use 3d acceleration. my graphics card doesn't support the advanced hooks, etc. now I have never enabled this option so it would have to been enabled after. though root cause could be due to discrepancy of DLL.

0 Kudos
mmoser
Contributor
Contributor

Thanks for posting this! Saved my day!

0 Kudos
mmoser
Contributor
Contributor

I tried the forward approach (i.e. change all curllib.dll to use the new version), but that kept crashing at me.

Changing all 3 locations to use the "old" version on the other hand worked for me - so that's my workaround for now!

0 Kudos