I have had similar problems too with both Workstation 5 and 6. From my experiences there are usually either one of two causes. The first and most common is that another program is using you virtual machine files. To check if this is so look for a program called ‘unlocker’ http://ccollomb.free.fr/unlocker. The second cause may be bad hard drive sectors, usually a chkdsk (start->run type in chkdsk) sweep will fix that quite easily.
I have had similar problems too with both Workstation 5 and 6. From my experiences there are usually either one of two causes. The first and most common is that another program is using you virtual machine files. To check if this is so look for a program called ‘unlocker’ http://ccollomb.free.fr/unlocker. Don’t unlock files pertaining to VMware (vmnat.exe, vmnetdhcp.exe, vmount2.exe, vmware-authd.exe, vmware-tray.exe)! The second cause may be bad hard drive sectors; usually a chkdsk (start->run type in chkdsk) sweep will fix that quite easily.
I hate to say this but, I am out of ideas. The most I could suggest is that you look for corruption in your VM’s .vmxf, .vmsd and .vmx files. Other than that if no other solution can be found I would suggest importing the VM (under file->import).
I had this same problem in Workstation version 6 after I created a clone of the VM from a snapshot. Removing all .lck files and folders from the VM directory solved this for me without reverting to 5.5 or earlier.
