ReDeploy Troubleshooting Guide

Applies to: Professional and Server Editions of Macrium Reflect only.

 

 

This topic helps you troubleshoot errors that occur after using Macrium Reflect ReDeploy to deploy an operating system to new hardware.

Note:  Unusual hardware configurations can make it impossible for older Windows operating systems, such as XP, to boot. In these rare cases, using ReDeploy will not help.

ReDeploy does not detect any operating systems

Check that the operating system has been restored or that the disk containing the operating system is connected to the target computer.

If you are using firmware raid or non-standard mass storage hardware, check that the drivers have loaded correctly.

Windows never boots the machine appears to cycle continuously

Windows is possibly experiencing a system stop, blue screen error when it boots but the blue screen displays so briefly that the screen does not display it.

Rerun Redeploy and set the Disable reboot on system stop option. Reboot, and note the blue screen error code.

Blue screen message  0x0000007B while booting Windows

Code 0x0000007B indicates that Windows has not loaded correctly, or the associated hardware with mass storage drivers for the disk containing the operating system have not loaded correctly.

Rerun Redeploy. For each mass storage device, choose Locate driver to manually locate the best driver on your driver CD. Consider checking for the availability of newer drivers from your hardware vendor.

The BIOS configuration can also cause blue screen message 0x0000007B. If for example AHCI SATA mode is set, Windows XP cannot boot.

Blue screen message 0x00000024 while booting Windows

This is an NTFS read error. It is likely that the boot process is mounting a single disk from a RAID 0 or RAID 5 set using a standard IDE driver.

Driver not signed error while booting Windows

The Driver not signed error appears for 64-bit Windows Vista or later when you have injected an unsigned driver.

You can either tell Windows to allow unsigned drivers or update the driver as follows:

After booting Windows, two drives appear containing the operating system image

If Windows boots correctly and you have RAID 1 (Mirror) hardware, if you see the Windows folder on two drives then Windows has used standard IDE drivers and you are not operating in RAID mode.

Blue screen message 0x0000007E after booting Windows

Code 0x0000007E typically indicates that the configured hardware abstraction layer (HAL) is incompatible with the hardware.

Rerun Redeploy and either set the HAL to the recommended type or, if you are redeploying Vista or later, select Allow Windows to set HAL.

After booting Windows becomes unstable or locks up

The most likely cause of this is that the configured hardware abstraction layer (HAL) is incompatible with the hardware.

Rerun Redeploy and either set the HAL to the recommended type or, if you are redeploying Vista or later, select Allow Windows to set HAL.

Keyboard and mouse never become active

If the keyboard and mouse do not become active, try removing then reinserting the their USB connectors or moving the USB connectors to different USB sockets. Finally, try rebooting.

If you have PS/2 devices available, then try those. Note that to connect a PS/2 device you must reboot.

Your system might also have locked up. Refer to the relevant troubleshooting section.