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 (152)
- vmware player failed to lock the file (124)
- a general system error occurred failed to lock the file (56)
- vmware workstation failed to lock the file (51)
- failed to lock the file vmware (45)
- failed to lock the file (45)
- unable to lock memory aborting virtual machine (40)
- vmplayer failed to lock the file (33)
- reason: failed to lock the file (31)
- vmware workstation 9 failed to lock the file (25)
thanks great help mate i deleted the lck files even though they were 0 bytes it still fixed the problem
Thanks a bunch! I thought I was going to have to edit the hex code to get my vm to work….
thanks so much, so much thanks ^^.. i love u
Thanks so much bro ! man i almost had a heart attack and then calmed down and googled the error… hehe
Thanks that really helped me out.
thx dude i needed help on my virtual machine as i first got this error i was like
DANMIT but i searched how to get rid of this error and i found this so thx alot bro
Thanks a lot dude! I love you!
)
Great, just what I need to save my work.
Thanks
Thanks, it really helps !
thanks a TON….:)