Scary moment occurred last week when one of my virtual machines failed to start from VMWare Workstation. The reported error was “failed to lock the file”.
A bit of searching revealed that I needed to delete the .LCK file in the Virtual Machine’s folder.(My location was c:\virtual machines\ubuntuintrepid\
The cause for this was that I had opened the virtual disk of this VM as a mapped drive on the host machine (TIP: very useful feature to get at files from the VM without powering it up – just right click on the .VMDK file in Windows Explorer, and you’ll see a couple of options there to map the disk as a drive). That drive was still mapped when trying to start the VM, meaning that the host machine was accessing the VM’s files.
Even you can rename the lock file with TXT extension in the lock directory.
Incoming search terms:
- vmware failed to lock the file (221)
- vmware player failed to lock the file (150)
- vmware workstation failed to lock the file (80)
- failed to lock the file (77)
- failed to lock the file vmware (77)
- a general system error occurred failed to lock the file (68)
- unable to lock memory aborting virtual machine (53)
- vmplayer failed to lock the file (47)
- vmware workstation 9 failed to lock the file (43)
- failed to lock the file vmware workstation (38)