Search

Language:  

Available article translations:

Cannot login to Windows Virtual machine migrated from a PC. BSOD 7B

APPLIES TO:
  • Parallels Desktop 10 for Mac Home Edition
  • Parallels Desktop 9 for Mac Standard Edition
  • Parallels Desktop 8 for Mac Standard Edition

Symptoms

I cannot login to my Virtual Machine migrated from my PC

Windows crashes with Blue screen of Death STOP 0x7B or System Repair screen

Resolution

  1. Launch Parallels Desktop but do not start your migrated Virtual machine or stop it if it is running.
  2. Open your Virtual Machine's Configuration -> Hardware -> Boot Order and add the following string into the Boot flags field:

    vm.compat_level=2
    

    also check "Select boot device on startup" checkbox

  3. Start your Virtual Machine,

    click into the Virtual Machine window,

    press Esc and choose the SATA drive as boot device (usually "2")

    then immediately press F8 repeatedly to get to Advanced Boot Options screen.

    Choose "Repair Your Computer"

  4. In System Recovery Options click on "Command Prompt"

  5. Using the Command Prompt switch to Windows\system32\config folder:

    switch to main Windows boot drive

    C:
    

    Note: in some cases the actual "Windows boot drive" may be D: or some other letter depending on your particular setting. To check whether the drive you switched to contains WINDOWS folder type in:

    dir
    

    and press Return, the output should be similar to

    once you verified you are on the correct drive, type in:

    cd Windows\System32\config
    

    press Return,

  6. Load the SYSTEM registry hive:

    type in:

    reg load hklm\fix_SYSTEM SYSTEM
    

  7. Launch Registry editor to make necessary changes:

    type in:

    regedit
    

    press Return, Registry Editor will start.

  8. Go to HKEY_LOCAL_MACHINE/fix_System/ControlSet001

  9. Find the following registry branches:

    HKEY_LOCAL_MACHINE/fix_System/ControlSet001/services/atapi

    HKEY_LOCAL_MACHINE/fix_System/ControlSet001/services/intelide

    HKEY_LOCAL_MACHINE/fix_System/ControlSet001/services/msahci

    in every path find key 'Start' and change it to '0'

  10. Repeat step 9 for the following branches:

    HKEY_LOCAL_MACHINE/fix_System/ControlSet002/services/atapi

    HKEY_LOCAL_MACHINE/fix_System/ControlSet002/services/intelide

    HKEY_LOCAL_MACHINE/fix_System/ControlSet002/services/msahci

    Once it is done close Registry Editor

  11. Return to Command Prompt and unload the SYSTEM hive:

    reg unload hklm\fix_SYSTEM
    

  12. Restart your Virtual Machine

Please see the full Command prompt output for reference:

Cause

Windows boot disk drivers are not configured properly in System Registry.




1e5db16426987d561060acdf56d947b4 97cd84747b25a2e5a06065a21a747a53 a9c6e0b6a5209e617a7c0dd5eace86cf 3307fff3682b15f0ba3fbe13d779296d 39e36b0abb33520c52ec8a15b563c41d

FEEDBACK
Was this article helpful?
Tell us how we may improve it.
Yes No