Solution to a problem where VMware cannot start due to forced power outages

First, warn you not to arbitrarily shut down the machine, VMware is a complex mechanism of software. All sorts of situations are easy to come by.

A virtual machine works just like a real computer, such as installing an operating system, installing applications, accessing network resources, and so on. For you, it's just an application running on your physical computer, but it's a real computer for an application running in a virtual machine. So, when you are evaluating software in a virtual machine, it could crash like a system, but only the operating system on the virtual machine, not the operating system on the physical computer, and, using the virtual machine's Undo (restore) function, you can immediately restore the virtual machine to the state before the software was installed. A friend in the running virtual machine when the phenomenon of panic, forced shutdown, the original did not normally shut down the virtual system can not start normally, what causes the virtual machine crashes . Against this phenomenon. Below we will learn how to solve the problem of the virtual machine can not start .

Solution:

Delete% virtual machine Name%.vmx.lck folder or file in the corresponding virtual machine directory

When we open Task Manager, we find that there are two important processes in Vmware.exe and Vmware-vmx.exe. Where Vmware-vmx.exe is the main program, the virtual machine runs under this process; The VMware.exe is the shell that displays the virtual systems running in Vmware-vmx.exe and interprets the various commands and operations, and is our most common VMware user interface, which can be reentrant to open multiple at the same time.

Because VMware Workstation is reentrant, to avoid the same virtual system being opened by multiple VMware.exe at the same time, causing an error, each VMware opens the appropriate Virtual Machine tab to check for * in the virtual machine root directory. Vmx.lck folder and verify the files in it, if the file contains a legitimately generated UUID (Universal unique identifier), you will not be able to open the Virtual Machine tab and the following error message appears:

The following prompts appear after Take ownership:

If there are no legitimate files, the *.vmx.lck folder is generated in the root directory of the virtual machine, and a *.lck file containing the UUID is generated under that folder, the Virtual Machine tab opens, and the display information is received from the main program.

This *.lck file can be edited in Notepad. It's uuid={. A string of alphanumeric},uuid is a universal unique identifier (universally unique Identifier), which is characterized by uniqueness. So that only one vmware.exe can accept the display of the main program and operate on the virtual machine. LCK is the abbreviation for lock, which is the lock on the requested resource.

The VMware virtual machine generates three file *.vmx.lck,*.vmdk.lck,*.vmem.lck folders in the appropriate virtual machine directory at run time, containing files named *.lck. The *.VMX.LCK is generated with the opening of the Vmware.exe tab, and the other two are about the use of virtual disks and memory, which are generated by the operation of the virtual system. If you turn off VMware.exe to allow the virtual machine to run in the background, the *.vmx.lck folder will disappear and the other two will not.

When you open a virtual Machine tab in VMware.exe, a *.vmsd.lck folder is generated briefly, which is estimated to be generated when the data is originally transferred (send), preventing multiple shells from simultaneously requesting the virtual machine to open.

By doing this, deleting the *.vmdk.lck,*.vmem.lck folder may be due to an error, "file or directory corruption."

Do not be discouraged, possibly due to your disk drive damage, turn off VMware, reboot your physical machine, attention is the physical real host.

Do not skip the check repair of the disk while rebooting.

Try to open the *.VMX again, is not good.

Still have to say two words, if you have been smart-aleck, with Notepad edited *.vmx file, from VMware is not open *.vmx, need the right key point *.vmx with virtual machine open.