Symptoms
I cannot login to Virtual Machine that was migrated from PC.
Windows crashes with Blue screen of Death (BSOD) STOP 0x7B
or System Repair screen
Cause
Conflicting drivers/interface configuration.
Resolution
NOTE: before proceeding with the further actions please create a backup of the Virtual Machine .pvm
bundle.
Launch Parallels Desktop but do not start migrated virtual machine.
Open your Virtual Machine's Configuration> Hardware > Boot Order and add the following string into the Boot Flags field:
vm.compat_level=2
Check "Select boot device on startup" checkbox.
Boot virtual machine in Recovery mode:
Click into the virtual machine window,
Press Esc and choose the SATA drive as boot device:
Then immediately press F8 repeatedly to get to Advanced Boot Options screen.
Choose "Repair Your Computer":
In System Recovery Options click on "Command Prompt":
Using the Command Prompt switch to
C:\Windows\system32\config
folder.Note: in some cases Windows can be installed on drive
D:\
or some other letter. It depends on your particular setting.To check where Windows is installed, execute:
diskpart
and then:
list volume
the output should be similar to:
You need to find the drive letter where OS is installed (from the example above, this is drive E:).
Once you found the drive, change directory to the required folder:
E: cd Windows\System32\config
Load the SYSTEM registry hive:
reg load hklm\fix_SYSTEM SYSTEM
Launch Registry Editor to make necessary changes:
regedit
and hit Return in order to start Registry Editor.
Find and edit the following registry key:
HKEY_LOCAL_MACHINE\fix_SYSTEM\ControlSet001\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}
in the right pane locate the value 'UpperFilters' and set it to 'PartMgr'.
in the right pane locate the value 'LowerFilters' and delete it.
NOTE: in some cases 'UpperFilters' may have several values, some of them might be needful for system load. Such as 'gpt_loader'. Such values also should be left.
ALSO, if your drive is encrypted by PointSec software, you should leave 'prot_2k' value as well.
Repeat step 9 for the following key:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}
Close Registry Editor, return to Command Prompt and unload the SYSTEM hive:
reg unload hklm\fix_SYSTEM
- Restart virtual machine. Once you confirm that it boots fine, revert the changes performed in steps 2 and 3.