@Miltumaya 

You could try creating a new VM, giving it access to the virtual disk of the problematic VM.

In case you want to have help, please provide some details.

Post a complete list of files in the VM's folder, i.e. the output of either dir *.* (on Windows), or ls -lisa (on Linux).
In addition to this, compress/zip the VM's .vmx file, and attach the .zip archive to your next reply.

André