Here's my circumstances... I'm using Parallels Desktop for Mac v12 on OS X El Capitan (10.11.6). I have been successfully running a Windows XP VM for years with zero problems. The MacBook Pro HDD dies. I replace the HDD and recover my OS X system using my most recent Time Machine backup All is good...until I try to run my Windows XP VM. On start up, Windows XP detects file system issues, runs CHKDSK, and finds lots of broken file indexes, etc. Very consistent results on every retry. I try out older Time Machine backups of the PVM - same problem! I don't care about running the guest Windows XP OS - I am very happy to just extract user files/folders from the VM. I mount the PVM file using Parallels Mounter; the Windows XP file structure seems to be fully intact (no folders missing, files seem to be in place) I copy some files out to OS X however if I try to copy many at once, the copy process freezes up - I get a spinning beach ball associated with the Finder app. My only way to regain control of the system is to power cycle the system. Further investigation shows that just browsing (with Finder, of course) certain folders within the mounted PVM cause the lockup/freeze problem - it's not related to copying out the files within. I've also seen that I can browse to a particular folder and see all the contents I would expect and then not being able to see them after having rebooted (due, of course, to hitting on some "bad" folder and locking up the system). Parallels Mounter/Finder "problem" occurs for all of my backups of the PVM. Uh oh. I test this out with the trial version of Parallels v13 and get the same problem. So here's the question... 1) Have I found a bug in Parallels Mounter? (where it doesn't handle certain file/folder access problems well?) If so, how to report it? 2) Is there another tool I can use browse the guest OS folder system that's more resilient to guest OS file system corruption?
