First of all posting the full content of files is generally frowned upon and considered rude as no one wants to have to scroll down through hundreds of lines of crap! Next time archive (compress) the files an attach as a single .zip archive and note you need to click "Use advanced editor" in the upper right of the now normal reply in order to attach files.
Directory listing showing names only are about worthless! The only good a name only listing does is show if a file might be missing and while that does happen once in a while nonetheless a listing showing name, file size and date/time stamp give much more information to analyze. Either a snapshot or redirected output to a text file from a Command Prompt or Terminal attached as a file. As an example recently someone posted with the same error and said all the files were there and when I asked of a listing showing name, file size and date/time stamp it shows that while technically all the files were there nonetheless several were zero length in size and as such there in was the problem.
Now something that having the name, file size and date/time stamp doesn't show is if the header of any of the binary extents are corrupt and this too can cause the error you're getting. Although diagnosing that require advanced techniques as a third party utility needs to be use to extract and or examine the header of each of the extents.
Have you tried using vmware-vdiskmanager to attempt to repair the virtual hard disk? If not you can try that however make sure you have a backup first. Have a look at: Repairing a virtual disk in Workstation (2019259)