Fix for VMWare Virtual Machine ‘Failed to Lock the File’ Error
If you're new here, you may want to subscribe to Windows Reference RSS feed Thanks for visiting!
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.
Random Posts
Did you enjoy this post? Why not leave a comment below and continue the conversation, or subscribe to my feed and get articles like this delivered automatically each day to your feed reader.
Trackbacks & Pingbacks
Comments
Leave a comment
Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
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