Please edit the .cmd file and add -ExecutionPolicy Bypass to the command to see whether this allows you to run the scripts.
powershell.exe -ExecutionPolicy Bypass -command "%~dpn0.ps1 -FilePath \"%~1\""
If this still doesn't help, then please open a Command Prompt, go to the directory in which you've saved the scripts, and run the
Get-VmdkHeader.cmd "E:\mastervm6\master6-disk1-000016.vmdk"
This way the command prompt will not close after running the command, and you should see an error output.
After taking a closer look at the issue, I think that it's related to 2 issues. One is the corrupted .vmsd file, which causes the dictionary error, and the other one is most likely caused by a corruption in the above mentioned .vmdk file.
Fixing the .vmsd file is comparable to playing a puzzle with thousands of white pieces, so that if you do not have a recent backup, you'll likely loose the snapshot tree. If the .vmdk file is corrupt too, I may be able to fix the metadata, but I cannot bring back any overwritten data. However, if you can afford to loose the latest snapshot, we can set the VM back to its parent snapshot.
André
