ReDeploy detects changes to critical system features, locates relevant drivers and injects them into your Windows operating system so it boots. For a stable system, the driver needs to match the hardware, in this example, the CPU model.

Drivers are optionally loaded to handle specific central processing unit (CPU) features. The kernel and its associated hardware abstraction layer (HAL) need to match the motherboard for best enabling. When the kernel and critical drivers are loaded, the kernel starts.

If the new hardware configuration requires a new driver to read the disk containing the operating system then Windows will fail to boot. It is skipped during a normal Windows boot making the boot delay acceptable.Įarly in the boot process, the boot loader loads the Windows kernel (the core of the operating system) and the critical drivers required to get Windows up and running. Moving between a physical and a virtual machine (P2V / V2P).Ĭhanging a non-raid to a raid installation or legacy SATA to AHCI SATA.Īspects of the Windows boot process can cause a boot failure after significant changes to the hardware, ReDeploy can overcome these.ĭiscovering hardware and association with matching device drivers is time consuming and must be undertaken while windows is being installed. There are a variety of scenarios where you move a windows installation to a new machine, for example:ĭue to hardware failure or planned upgrade. Macrium ReDeploy overcomes issues with Windows boot processes to run a Windows installation on new hardware.

Macrium reflect ubuntu