I seem to recall something like this happening to me once. Find the file itself, make sure you have file extensions set to be visible (if it's windows), and check to see if the file as any sort of suffix added to the end of the vmdk files. If I remember correctly the way it locked the file was to rename it and add something to the end of the filename like .lock or something. I removed the extra extension and it booted up after that.
↧