Skip to main content

Unable to open kernel device . global vmx86 windows 7

Suddenly I encounter a weird problem with VMware 9 version. I install different OS for my education and testing purposed. Like MAC os, Ubuntu, CentOS, BT, WinXP, Win-server 2003. When I tried to run one of this OS a error message appear.



unable to open kernel device "\\.Global\vmx86": The system cannot find the file specified. Did you reboot after installing VMware Workstation?
Failed to initialize monitor device.

Click ok you can see this window



After googling I found one solution in developer forum but thread starter never use that method. So I tried it and here is my finding.



Go to the directory of vmware installed 
(In my case I run it as Administrator)
C:\Program Files (x86)\VMware\VMware Workstation>   ( I've 32-bit apps on 64-bit OS, your may be different)

Run this command
vnetlib -- uninstall vmx86 
reboot

Go to the same directory and check net start command - this time it should say "service name  is invalid"

This command run perfect and no error message is appear, if that so then I think VMware OS must run, I tried it but, shows same error message

then run
vnetlib -- install vmx86 
and reboot again

TA DA !!!!! its run.

Comments

  1. Absolutely thank you! You rescue my lesson!!!

    ReplyDelete
  2. how to run vnetlib -- install vmx86

    ReplyDelete
  3. Thanks, my vm backtrack run again.

    ReplyDelete
  4. it's showing now- Unable to open kernel device "//. /vmci: The system cannot find the file specified. Did you reboot after installing VMware player?

    ReplyDelete
  5. Crazy tip But Worked for me . Thx bro

    ReplyDelete
  6. wow it worked thank you. I think this vnetlib should display messages, because it is very like guessing. No help and not sure if the parameters had to have space between the double --.

    ReplyDelete
  7. in my case no need to reinstall vmx86. it just need to be restart. So use this command :

    net start vmx86

    ReplyDelete

Post a Comment

Popular posts from this blog

Simple Failover Mikrotik

Simple fail-over Mikrotik router configuration. Most of the user wants backup link (Fiber link with Wireless backup), in case fiber down wireless link auto up. No downtime for the user. Here is simple setting on Mikrotik for fail-over. I'm very great full to Anton to point out the mistake in src-address. It has been corrected now. ****default routes for new outgoing traffic.**** /ip route add dst-address=0.0.0.0/0 gateway=ISP-GW-ADDR-1 distance=1 check-gateway=ping add dst-address=0.0.0.0/0 gateway=ISP-GW-ADDR-2 distance=2 ++masquerade both WAN connections++ /ip firewall nat add chain=srcnat src-address=192.168.0.0/24 out-interface=WAN-1 action=masquerade add chain=srcnat src-address=192.168.0.0/24 out-interface=WAN-2 action=masquerade Thats it.

MongoDB Failed to start lsb an object/document-oriented database

After long gap I'm going to post new blog. Due to the work load and research I have little time.  MongoDB could not started after installation of 3.6 version, However downgrade to the 3.4, still the Mongodb couldn't start and show below error message. Search don't help to resolved the issue. After so much hit and trail nothing work. One Chinese forum posted this command and its works for me.  cd /var/lib sudo rm -rf ./mongodb sudo mkdir mongodb sudo chown -R mongodb mongodb/ sudo serivce mongodb restart