My VM Workstation Player v17.0.2 came with system file vmx86.sys v410.0. However, every time I attempt to open a virtuat machine (openSUSE), an error pops up requesting system file vmx86.sys v416.0; please see attachment 155225. Once this error pop-up is acknowledged, it is followed by another pop-up, this one for VMDB error -14, as presented in attachment 155528. What does this all mean?
It is frustrating to seek an answer, as most remedies crowding the web either fail to address the lack of this file or worse, they address a long-deprecated version. This is not to mention the ones with poor production values such as blurriness or going silent at the worst possible moment. Does system file vmx86.sys v416.0 even exist? Is this a glitch in the code such 410 being correct but the code is wrong? Does VMware have an actual solution buried deep in the website?
What is the host operating system (the operating system that you running Workstation on)? I assume that since it's asking for "vmx86.sys" that it's running on some version of Windows?
Are your virtual machines powered off, or suspended?
Did you upgrade this Workstation Player from earlier versions?
Have you tried uninstalling Workstation Player, rebooting, then reinstalling Workstation 17.0.2 from a fresh copy downloaded from VMware?
Q: What is the host operating system (the operating system that you running Workstation on)? I assume that since it's asking for "vmx86.sys" that it's running on some version of Windows?
A: It is Windows 10 Home, 22H2
Q: Are your virtual machines powered off, or suspended?
A: The error messages pop up whenever I try to start a virtual machine.
Q: Did you upgrade this Workstation Player from earlier versions?
A: I had Player 17.0.0 earlier. I uninstalled it and installed a fresh copy of 17.0.2 from the VMware site.
Q: Have you tried uninstalling Workstation Player, rebooting, then reinstalling Workstation 17.0.2 from a fresh copy downloaded from VMware?
No, no pro, and certainly not any of those exotic flavors. Since you mentioned hardware, this is a 2016 Pavilion HP 17-g121wm (yes, a Walmart special). Yes, the one with the Radeon CPU that has since been remarketed as a GPU.
If you uninstall Workstation Player 17 and look in c:\Windows\System32\Drivers, are there copies of the following files still there:
Yes, they are all there, dated 07/11/2022. I remember installing VMware Workstation Player for an Ethical Cybersecurity Hacking course in the spring of last year, but the dates don't fit.
Should I delete these drivers by hand? And once removed, should I repair the app, or uninstall and reinstall fresh?
It sure sounds like that driver didn't get updated - I have an install of 17.0.2 on Windows 10, and the timestamp on vmx86.sys is 9-apr-2023.
First, open a command prompt running as administrator. Then run the setup program exe file of 17.0.2 that you downloaded from VMware in the command line.
When prompted, choose the option to remove the product. :Then reboot and see if the drivers are still there. If not, then reinstall. After re-install, check the time stamp on the vmx86.sys file.
I was more brutish than that. First, I uninstalled Player 17. Good. Then I went into C:\Windows\System32\Drivers and deleted the aformentioned system files except vmx86.sys. It kept saying that some other application was using it, so I got rid of my openSUSE VMs. Still wouldn't budge, so I moved it. I tried to move it to the Recycle [sic] Bin, but it dug in and I wound up putting it in OneDrive. Then I tried destroying the file by selecting all text and deleting it, but no, it was in use by another app! Being that I'm stubborner than stubborn system files, I flushed out every single iteration of vmx86.sys in drive C:. That actually did it. I was able to delete vmx86.sys for good. Then I installed VMware Workstation Player 17.0.2 without a hitch. Same thing with my openSUSE VMs. Thank you, Technogeezer, for the guidance.