![vmware workstation failed to lock the file vmware workstation failed to lock the file](https://i.stack.imgur.com/RBamJ.png)
There is no harm in deleting this file and you won’t loose any data which was in the saved state when you paused the VM.
#VMWARE WORKSTATION FAILED TO LOCK THE FILE WINDOWS#
If you are at a Windows command prompt and in the directory where the lock file exists, type delPlease take a backup of the file before deleting until the issue is confirmed fixed. lck file.ĭelete all the instances of the. Look for and delete any file, directory, or folder that ends in either. Look for the folder which contains VM Player files. Step 1: Select Preseve from the dialog box. Discard – This will discard the suspended state of the VM and Operating system will reboot losing the saved state. Preserve – This will preserve the suspended state.Ģ. When attempting to start a virtual machine on VMware Workstation you may see the error'Failed to lock the main memory file' and you are prompted whether to d.
![vmware workstation failed to lock the file vmware workstation failed to lock the file](https://communities.vmware.com/wbsdv95928/attachments/wbsdv95928/2001/15367/1/fragmented.png)
Later when I tried to resume the VM, I received an error message which said, “Failed to lock the main memory file ‘C:\****\VM82**.vmem’.”ġ. I had suspended my VM-Player with many application opened so that the next time I use it I could resume the state of the VM (Virtual Machine). Step 2: After restarting the computer open command prompt and run the following commands. 3) Restart the computer: 'win+R' type shutdown -r -t 0. Select and Delete all vmware files and folders in this location. We call it WebSphere Commerce Suite (WCS). 2) Make sure none of the VMware installation or uninstallation process is running. I use VMware Player application for development related to IBM-WebSphere Commerce Developer. Are you worried because you are not able to resume the suspended state of VMware Player and you fear that you might lose the saved state?ĭon’t worry, Friends! I have a solution to it. Below is the image of the folder containing the VM & the image of the VM itself.