This is absolutely weird. The ...00004.vmdk snapshot doesn't point to the folder which - according to the log file - is used!?
I'm not sure whether this will work, but at least it should not hurt anything, so let's give it a try. I attached a .zip file, which contains a blank base virtual disk (NTFS formatted with a 100MB System partition) as well as the patched "Windows 7 x64-000004.txt" in which I set the parentCID to match the CID of the newly created base virtual disk. What you may do is to extract the contents of the .zip file to a new folder and copy the "Windows 7 x64-000004.vmdk" to this new folder too. Then use dsfi.exe and inject the patched .txt file into the .vmdk file running:
dsfi.exe "Windows 7 x64-000004.vmdk" 0 1536 "Windows 7 x64-000004.txt"
Once done and you are lucky, you should be able to map the virtual disk "Windows 7 x64-000004.vmdk" as an additional drive using VMware Workstation's "File" -> "Map virtual disk", and extract/backup the files you need.
André