VMWare Workstation 10.0.3: Unable to open kernel device "\\.\Global\vmx86: The system cannot find the file specified."

7,542

Solution 1

Even though this is not exactly a clean solution, it seems like I found a workaround for this problem. Running the command vnetlib -- install vmx86 in the Workstation directory reinstalls the deleted service and the vm can be powered on again (even without rebooting the host - but that's why I consider it only a quick'n'dirty solution and not a permanent fix). Still, if anybody has got a better solution I would be really thankful.

Solution 2

I tried @Andreas's solution but running the command didnt seem to result in anything, and I wasn't able to start my vm still.

In the end my solution was to run net start vmx86 in an administrator cmd prompt.

Share:
7,542

Related videos on Youtube

dudenr33
Author by

dudenr33

Updated on September 18, 2022

Comments

  • dudenr33
    dudenr33 almost 2 years

    VMWare Workstation keeps displaying me the error "\.\Global\vmx86: The system cannot find the file specified." when I try to start a VM. I am using Workstation on a computer with multiple users. Directly after installing Workstation it runs the VM just fine, but after switching users a few times (each of the users also uses the same installation of Worksation with the same VM) it displays this error, followed by "Internal error". The host system is Windows 7 Enterprise 64Bit.

    What I have found out so far: - the registry entries HKEY_LOCAL_MACHINE -> SYSTEM -> CURRENT_CONTROL_SET -> ENUM -> ROOT -> LEGACY_VMX86 and HKEY_LOCAL_MACHINE -> SYSTEM -> CURRENT_CONTROL_SET -> services -> vmx86 get deleted at some point

    • in C:\Windows\System32\drivers, the file vmx86.sys gets deleted

    • when I run lusrmgr.msc, the formerly present entry Groups -> vmware is gone

    What I have tried: - reinstalling Workstation - helps, but is too time consuming and the problem will occur again soon

    • Running Workstation as admin -> doesn't help

    • renaming vmware.exe (found this tip on the internet) -> no change

    • adding all users who log on to this computer and use the VM in lusrmgr.msc -> Groups -> vmware directly after installation -> seemed to work a bit longer than before, but problem still persists

    I am not completely positive that this problem is directly related to switching users, but it only happened after logging out and back in so far. Any help would be much appreciated.

    • Kevin Versfeld
      Kevin Versfeld over 9 years
      What do the vmware people say? BTW VMWare Workstation current release is 11.0.
    • dudenr33
      dudenr33 over 9 years
      Haven't asked at the VMware community yet, but will do that right now. But I googled a lot and summarized the suggested work arounds above. Mostly the problem is solved after reinstalling workstation, but not for me. I know Workstation 10 is not the current release but at the moment I have to use it.
    • dudenr33
      dudenr33 over 9 years
      It seems that this is a problem specific to the pc I'm using. I installed worksation on another computer with (at least almost) identical specs and operation system and the registry entries etc. are still there after multiple switches of users and reboots.
  • Артур Гудиев
    Артур Гудиев over 4 years
    Thanks! It works for me!