Six years ago I installed windows 7 as a bootcamped system under a Mac OS X 10.6. Few month later I installed Parallels Desktop and used this bootcamped Win7 from that time on only over Parallels.
February 2015 I upgraded to OS X 10.10 and as a consequence of this activity I also upgraded Parallels from version 6 to version 10 - everything still beeing fine.
Last week I received an update message from Parallels to update to the latest build what I did. After starting the bootcamped Win7 over Parallels the installation of Parallels Tools' (new build) was started - but this failed.
After investigating a few web-sites I found several solutions for this problem - but before applying them I did an import of the bootcamped Win7 in order to solve the installation of Parallels Tools on the imported system and to keep my old bootcamped Win7 as a fallback. After a while I succeeded in finishing the installation of the latest Parallels Tools and so I had a running and well working "Imported Windows 7" as a VM under the latest build of Parallels Desktop.
After having reached all this I:
Afterwards I tried to change the harddisk 1 in the copied "Imported Windows 7" from the configurated Boot Camp partition (since it was an import of a Boot Camp system) to the hdd-image i found inside the corresponding .pvm file. But trying to boot this VM's configuration resulted in a Windows 7 start then entering into the repair mode of Windows 7.
I then tried to mount the VM's harddisk via the Parallels Mounter but the result was a complete system hangup of Mac OS X, so the partition of the disk of the "Imported Windows 7" VM is also not mountable.
So actually I have 2 VMs:
Reviewing the above I simply took the same actions as described in step 2 and 3 of the Instructions of http://kb.parallels.com/de/113658.
Has anyone any solution for this situation? At least I need to get some files out of one of my two remaining VMs I was working on the last days before this mess happened.
Thx, Frank
February 2015 I upgraded to OS X 10.10 and as a consequence of this activity I also upgraded Parallels from version 6 to version 10 - everything still beeing fine.
Last week I received an update message from Parallels to update to the latest build what I did. After starting the bootcamped Win7 over Parallels the installation of Parallels Tools' (new build) was started - but this failed.
After investigating a few web-sites I found several solutions for this problem - but before applying them I did an import of the bootcamped Win7 in order to solve the installation of Parallels Tools on the imported system and to keep my old bootcamped Win7 as a fallback. After a while I succeeded in finishing the installation of the latest Parallels Tools and so I had a running and well working "Imported Windows 7" as a VM under the latest build of Parallels Desktop.
After having reached all this I:
- deleted the old Boot Camp partition with my fallback Windows 7 installation inside (but I kept the definition in Parallels Desktop,
- made a new clean partition (HFS+) in that area of the former Boot Camp,
- made a copy on OS level (.pvm -> .pvm) of the "Imported Windows 7" to this new partition,
- set the standard directory path for VMs in Parallels Desktop to this new partition,
- and opened this copy of the "Imported Windows 7" in Parallels to define a new VM.
Afterwards I tried to change the harddisk 1 in the copied "Imported Windows 7" from the configurated Boot Camp partition (since it was an import of a Boot Camp system) to the hdd-image i found inside the corresponding .pvm file. But trying to boot this VM's configuration resulted in a Windows 7 start then entering into the repair mode of Windows 7.
I then tried to mount the VM's harddisk via the Parallels Mounter but the result was a complete system hangup of Mac OS X, so the partition of the disk of the "Imported Windows 7" VM is also not mountable.
So actually I have 2 VMs:
- A: import of my old Boot Camp Win7 ("Imported Windows 7"),
- B: OS-level copy of the imported Boot Camp VM (copied "Imported Windows 7").
Reviewing the above I simply took the same actions as described in step 2 and 3 of the Instructions of http://kb.parallels.com/de/113658.
Has anyone any solution for this situation? At least I need to get some files out of one of my two remaining VMs I was working on the last days before this mess happened.
Thx, Frank