This is because of the "Significant Hardware Changes" detected by Windows when switching from Boot Camp to Parallels, or vice versa. Using the 0x0000007b fix appears to resolve any BSOD issues when booting into Windows using Parallels or Boot Camp, but there are a few other issues that arise from doing this: Thus, you have to do the procedure listed above to get Windows to run in Parallels.)
#Copycatx clone bootcamp Pc#
( When trying to run your Windows installation under Boot Camp, through Parallels, Windows reacts in the same way it would if you physically moved your hard drive from one PC to another. If it is 0x0000007b, then see this article to resolve the trouble. If you "Disable automatic restart on system failure" by using the boot option (F8), you should be able to see what the stop error is. The Stop Error I was getting was 0x0000007b. Section 3: Resolving issues with Stop Error 0x0000007bĪfter I resolved the first issue, I could boot back into Windows using Boot Camp, but was still getting a BSOD (Blue Screen of Death) when trying to use Parallels.
#Copycatx clone bootcamp how to#
There is more information on how to do this here. I restored the "system" registry file from the latest backup located in "C:\System Volume Information\_restore\RPX\Snapshot". If you want to look into it for yourself, you can find information here.). I had to resolve this issue by restoring this registry file using the Recovery Console (I actually used MacFUSE and NTFS-3G to access the NTFS partition from OSX to do this, but will not get into how to do this. ( If you do not have this problem, please skip this step.) There are two things that I had to do to resolve the issues that arose after installing the latest version of Parallels 3 (build 4560).įirst, I started receiving "Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM" when booting to Windows using Parallels or Boot Camp. Section 2: Resolving issues that may arise from installing Parallels Select the "Parallels" hardware profile when using Parallels and select the "Boot Camp" hardware profile when using Boot Camp. This will allow you to choose the correct hardware profile when booting into Windows using Boot Camp or Parallels. "Always include this profile as an option when Windows starts" Check the properties of each profile and make sure the following options are selected: Under "Hardware profiles selection", make sure "Wait until I select a hardware profile" is selected.ĥ. Rename the current profile "Boot Camp", and then copy it.
Go to the "Hardware" tab and click on "Hardware Profiles".ģ.
Open your "System Properties" either through the Control Panel or by right-clicking on "My Computer" and going to Properties.Ģ. (Credit for this fix goes to logan_barnett.)ġ. Please note, these steps are not available in Windows Vista. ( If you already tried to access your Boot Camp installation through Parallels, and can no longer get into Windows through Boot Camp or Parallels, please skip this step and come back to it after you have completed Section 2.)įirst we need setup one Hardware profile for Boot Camp and one for Parallels. Section 1: Preparing your Boot Camp Installation for Parallels
The reasons for this are addressed in Section 4 of this article. Something to know upfront: using your existing Boot Camp installation with Parallels will most likely require you to activate your Windows installation a second time. If you have already installed Parallels and now have problems, don't worry, this article should address and resolve these issues as well. Hopefully Parallels will be able to integrate these fixes into a future release.īefore doing anything, I would recommend preparing your existing Windows installation under Boot Camp, for Parallels, before trying to access it through Parallels. This article NOW resolves all issues pertaining to using Windows under Boot Camp through Parallels, INCLUDING activation. How to: Resolve trouble between Parallels and Windows under Boot Camp - UPDATEDĪfter seeing several threads relating to this issue, I decided to make this it's own thread instead of trying to reply to each.
0 kommentar(er)
