BSOD/Corrupt VM File

Discussion in 'Windows Virtual Machine' started by wycliffe, Aug 2, 2009.

  1. wycliffe

    wycliffe Member

    Messages:
    83
    My father has been running Parallels on his MBP with no issues until recently when he started getting the BSOD whenever he now tries to open Parallels. His .pvm file is backed up on Time Machine but anytime we restore it and try to open it, we get the BSOD again. I did a clean Windows install and that opens flawlessly - but we can not access the legacy data without the BSOD. Is there anyway to migrate the old .PVM files into the new .PVM created with the clean Windows install or is the data lost forever, even though it was backed up. The old .PVM is acting like it has been corrupted and then it overwrote all previous versions backed up in Time Machine.
     
  2. desgael

    desgael Pro

    Messages:
    344
    The data itself is not lost. You ca do the following:

    1. Right-click on an older .pvm file and choose "Show package content" option.
    2. Inside the bundle, find the .hdd file (or files, there could be several of those), this is a hard disk image itself which contains all the data.
    3. Drag or copy this file to some other place.
    4. Open your newly installed Windows virtual machine, make sure it is stopped and go to Virtual machine -> Configure
    5. Now you can press the plus button and add a second hard disk to it, just point to the .hdd file that you got from an older .pvm

    That way, you will get access to all the data on that hard disk, but all the programs would have to be reinstalled.

    One more thing you can try is to repair an old virtual machine, you can use the following article for this:
    http://kb.parallels.com/en/5138
     
  3. wycliffe

    wycliffe Member

    Messages:
    83
    Thanks for your quick response.

    Actually, I was able to repiar Windows from within the corrupted .pvm file during booting. Was able to recover everything.
     

Share This Page