17.5.1 update and the old vmx86.sys version error

[VMware Community Member]

I allowed the software to run the update from within its own updater. Upon reboot I find I can't launch any VMs because of the ol' "Version mismatch with vmx86 driver" error. It seems like this is a problem that just won't go away even after all these years. 

Brilliantly, I cannot run the "repair" function from the Windows Control Panel's Programs menu because what's installed is incapable of asking for elevated privileges in order to do so.  Accordingly, the attempt fails.

 

[VMware Community Member]

oh, after being forced to give up my personal information (without any opt-out) and agreeing to share my information with your "affiliates" for marketing purposes.... as well as overcoming a badly broken CAPTCHA, I was eventually able to download the update from your website and re-run that to fix the issue. 

(and currently it says I'm not signed in? brilliant, Broadcom...)

Now if anyone can point me to where I can opt-out of having my personal info sold that would be great.

[VMware Community Member]

You are not kidding getting registered is a pain!.  Did you ever get this fixed?  If so can you detail what you did.  I get the same error: "Version mismatch with vmx86 driver: expecting 416.0, got 308.0. You have an incorrect version of driver 'vmx86.sys'. Try reinstalling VMware Player. Failed to initialize monitor device. ".  I also can't use the "repair" option and when I downloaded the 17.5 it also would not install even though I am an admin.  What a pain that ever time I upgrade VMWare I get this type of error and have to spend days looking for a fix!. I'm sick and tired of VMware not being able to get upgrades right!.  Your help is appreciated.

[VMware Community Member]

Ok, after searching I finally found the file correct file  (they don't make it easy) Here it is: 17.5.1 build-23298084.

I went to products, VMware Workstation Player, then Download for free, then downloaded VMware Workstation Player 17.5.1

Here is the link

https://customerconnect.vmware.com/en/downloads/details?downloadGroup=WKST-PLAYER-1751&productId=1377&rPId=117008

After a reinstall as administrator it works.  Why it takes two times to install a file for an upgrade is beyond understanding.  Please VMWare get it right next time. 

JamesStewartnyc Thanks for starting the thread and getting me pointed in the right direction.

[Chaim Simcha]

I think it's time to ditch the expensive, licensed vmware and go with virtual box instead.  This is so ridiculous.  Is there a product manager? Who does the QA on this product?  Does it even get QAed at all?  What kind of weed are the devs smoking?  Apparently not the right kind because this just keeps happening over and over again and again ad infinitum, ad nauseum ad bullsh1ttium.  

 

[Dhairya Tomar]

 Requesting you to share the support bundle of the affected VM in this thread which is not getting powered on using below steps-

Help->Support->Collect Support Data

[Greg Duvall]

A year later, still happening. And I foolishly thought maybe Broadcom would improve the product. I also foolishly applied the update from the "Update available" button and am now right back to this for about the 10th time in almost as many years.

I've been using VMWare since it was first released in the late 1990s, installed many an ESX on bare metal and was a member of the local ESX users group.

[RaSystemlord]

Yes, I agree that you might think that things are improved.

But according to my experience, from any bigger software package, it is safe to assume that Upgrade Version never works. Sometimes you think they worked, but in the end there is some mess behind the scenes that will start to bug you later on.

The only exception to this is a Linux distro. But that is build up in a completely different way, where the distro ACTUALLY understands the dependencies (I mean, it COULD understand them, if they haven't screwed it up). Windows is such a mess of dll's and controls that a software vendor cannot guarantee anything if you don't use a default Microsoft installation  ... which nobody in the business world uses.

That is the reason why I used to have VMware on a "technical workstation", where no other potentially harmful software packages, like full Microsoft Office, were installed. And for heaven's sake, no adding to company Domain and not letting other people screw it up. I understand that many corporations like to deny those kinds of privileges to have a technical computer that actually works as it is intended to work.

[Greg Duvall]

It seems this has been going on for almost a decade, going back to the EMC or Dell days if memory serves. Finding the download link is the most frustrating part. Clearly, they either can't or won't fix the issue despite the software being free. I am having to do this for about the 30th time. From now on, I'm skipping a few versions AND downloading it manually, never on the apps recommendations. 

Here's the link I used if it helps anyone else shortcut the process. VMware Workstation Download