Unable to re-join a restored machine to an AD domain.

Problem

Solution

1. On the Active Directory (AD) Domain Controller (DC) server go to Active Directory for User and Computer. (Server 2003, SBS Server 2003)
2. Navigate to the computer/server account (this could be in a Organisational Unit).
3. Right click on the computer/server account, then select “Reset Account” - click on YES
4. Reboot the computer/server

This article covers some of the issues with drivers failing to load when booting WinPE.

Use drivers of the same architecture

Drivers not located on accessible disk

Solution 1 : Make drivers available on accessible media such as a usb device

xcopy /e c:\boot\macrium\drivers\* e:\boot\macrium\drivers

xcopy /e c:\boot\macrium\drivers\* e:\drivers

You must either be running Reflect v5.2 or later and have created an 'Auto-built Windows PE' rescue CD (WAIK or WADK for Windows 8). Follow all the steps below:

1.Take the 'Windows PE' rescue CD option in the rescue CD wizard. Just click 'Next' and be patient while the integration completes.

3. Once the integration is finished cancel the rescue media wizard on the final Wizard page.

4.Download and run 'inject.exe' from here:

http://updates.macrium.com/reflect/utilities/inject.exe

This will automatically inject the drivers into the windows image file (WIM) and will take a few minutes.

5. Once completed, take the rescue media build wizard again, click through to the final page and create your rescue media. Drivers will be integrated and you should have no problems booting with the CD and recognizing your local RAID volumes or USB 3.0 host controllers (PE3.1).

Note: If you re-integrate the rescue media WIM by clicking the 'Re-Build' button on the final Wizard page, or if an update to Windows PE is made available then you must follow this procedure again to add drivers into the newly created WIM file.

If you still have problems then email the file 'c:\waiklog.txt' and an explanation of your issue to support (at) macrium.com so we can investigate further.

1. Removeable media (such as USB pen drives). The file (macrium.oem) must reside in the Drivers folder on the root of the media.
2. CD=ROM/DVD-ROM drives. The file (macrium.oem) must reside on the Drivers folder on the root of the media.
3. Local fixed hard disks. The file must reside on the Boot\Macrium\Drivers folder on the root of the local hard disk.

Missing support files

Search Terms
Cannot see RAID array in WinPE
Drivers failed to load in WinPE
WinPE drivers
Driver load failed

tag:restore

tag:image

Macrium Reflect version 5 SPLA licenses.

About the Macrium SPLA license

This is a alternative usage based charging model, available to high volume service providers where the normal perceptual license model does not make sense. It is currently being piloted with a selected customers. If it is of interest to you, please contact us for more information.

How it works

You are provided with a single key per edition. This can be installed on an unlimited number of machineshosted by you. You will pay a monthly charge based on thenumber of unique machines with the software installed that are activewithin the billing period.

The billing is automatically generated using data from a daily callback to our licenseserver. You will need to ensure that the software has a network route toour server and provide us with an IP range (or ranges) that yourmachines will use to connect to our server.

Your monthy bill will include a report of usage broken down by machine. This will include the associated IP and MAC address of the interface used to contact the license server and also a user machine reference, if specified.

How to specify the user machine reference

This is configured during the install process and is purely for your convenience in interpreting your bill.

You can install in the usual way, just specifying your SPLA key. However, currently, you can only specify the user machine reference using the command line install method. Use the following, replacing the angle brackets with parameters relevant to you.

<installer>.exe /passive /l <log filename> LICKEY=<your spla key> LICOWNREF=<your machine reference>

Please read more about command line installs here.

The option 'Enable access to restricted folders' will mount the image with full NTFS access rights to all folders in the image. This enables you to fully browse images that were created on another PC where otherwise some folders may be inaccessible due to NTFS security restrictions.

The option 'Make writable' will make the mounted file system temporarily writable. This is useful to access files in the image where the opening application is required to write to the file. For example, Microsoft Virtual Hard Disk (.vhdx) files can be mounted and files in the mounted backup can be recovered without having to restore the .vhdx file first.

Note: Changes made to the mounted file system are temporary and will be discarded when the image is unmounted.

To mount an Image using the Macrium Reflect CLI:

(i) Open Command Prompt and change directories as necessary so the path to reflect.exe is shown.

(ii) Complete the command line as follows:
reflect.exe ["Path to Image file"] [Add one or more switches]

(iii) Press Enter/Return key.

Instead of inserting "Path to Image file" you can also replace it with "LAST_FILE_CREATED" if you want the last Image created in the current Windows session to be mounted.

Available CLI switches:

Note: If you do not use -auto you will be prompted with the 'Backup Selection' dialog to assign the drive letters

Some examples of using the CLI to mount images:

To mount an Image and prompt for a drive letter:
C:\Program Files\Macrium\Reflect>reflect.exe "J:\76FF71EBBB032A35-00-00.mrimg" -b

To mount all partitions of an Image using the next available drive letter(s):
C:\Program Files\Macrium\Reflect>reflect.exe "J:\76FF71EBBB032A35-00-00.mrimg" -b -auto

To mount all partitions for the last Image created in the current Windows session:
C:\Program Files\Macrium\Reflect>reflect.exe "LAST_FILE_CREATED" -b -auto

To mount all partitions in an Image using drive letters p,q,r
C:\Program Files\Macrium\Reflect>reflect.exe "J:\76FF71EBBB032A35-00-00.mrimg" -b -auto -drives p,q,r

To mount all partitions in a password protected Image using drive letters p,q,r where 'pwd' is the password,(the password is case sensitive):
C:\Program Files\Macrium\Reflect>reflect.exe "J:\76FF71EBBB032A35-00-00.mrimg" -b -auto -drives p,q,r -pass "pwd"

To Detach a temporary mounted drive using the Macrium Reflect CLI:

(i) Open Command Prompt and change directories as necessary so the path to reflect.exe is shown.

(ii) Complete the command line as follows:
reflect.exe[drive letter to detach] [-u]
If no drive letter is included the switch '-u' will detach all temporary mounted drives.

(iii) Press Enter/Return.

Examples:

To Detach all temporary drives:
C:\Program Files\Macrium\Reflect>reflect.exe -u

To Detach Drive J only:
C:\Program Files\Macrium\Reflect>reflect.exe J -u

The Macrium Reflect Windows PE rescue media is not machine specific, however, there are two issues that could possibly arise:

1. Hardware differences between Machine A and B.
   While the rescue media creation process will take into account drivers required for hardware on Machine A, the addition, or loading, of drivers for hardware on Machine B would have to be a manual process if required.
   
   If drivers are needed on Machine B to access local fixed disks (e.g.: RAID configuration), USB3 hardware or Ethernet based resources (e.g.: NAS or other file server) then these drivers will need to be loaded manually once the rescue media has booted into the WinPE environment.
2. Booting differences between Machine A and B.
   If Machine A is a UEFI booting system then in all likelihood the rescue media will have been created as UEFI and will not boot if Machine B is an MBR booting system and vice versa.

Search Terms
Boot Rescue Media
Boot Rescue Media On Different Machine

1. Why do I need to add drivers to WinPE

While WinPE is packaged with a large collection of drivers, there are many devices that are not part of the WinPE list of drivers. In order for your device to be recognised by WinPE, you will need to add a driver so that it gets loaded at boot time of WinPE and allows WinPE to "communicate" with your device.

2. What devices should I add drivers for ?

The main devices to be concerned with are hard drive/RAID controllers, network interface cards (NIC) or USB controllers and USB hubs. The first question that needs to be addressed is:

How will I be backing up or restoring in WinPE ?

If you intend to use a network device then you will obviously need to ensure that your NIC is supported in WInPE. If your hard drives are attached to a RAID controller then you will need to ensure that your RAID Controller is supported in WinPE, either by a WinPE driver or by adding a driver. And so on, apply this basic methodology until all required devices have support.

3. What makes up a device driver and where do I get one ?

A device driver is a collection of files (also referred to as a driver package) and generally comprises of:

• The actual driver software. These files have a .SYS extension.
• The driver information, or INF, file which contains the installation instructions for the drivers. These files have a .INF extension.
• An optional security catalog which signs the drivers for operating system which require signed drivers, commonly used on x64 operating systems. These files have a .CAT extension.
• One or more optional supporting software library files (Dynamic Link Library) which contain further code to support the driver software. These files have a .DLL extension.

Your best source for driver packages is the CD that came with your device (or motherboard) or download from the vendor website as a ZIP file. When download a package from the vendor website, it is best to source a ZIP package for easy extraction.

4. How do I check if my devices require drivers adding to WinPE ?

By using the Macrium Reflect option to Create Rescue Media. This wizard in Macrium Reflect contains a step which will do all the hard work for you. It will build a list of devices in your computer that are either hard drive/RAID controllers, network interface cards, USB controllers or USB hubs. For each of these devices it will check if:

• The device is supported by default in WinPE
• There is a compatible driver in the host operating system (this is only done for Vista and later systems).
• There is a compatible driver already present in the collection of drivers on previously created rescue media.

Unsupported devices it will be presented in the list of devices with a warning icon and a Status text of Device Detected. Supported devices will have a Status of either:

• Device Support in WinPE.
• Compatible Device Support in WinPE.
• Copy Host Driver.
• Driver already present in Drivers folder.

Following is a screen-shot of the drivers step in the Create Rescue Media wizard

5. How do I update the driver software of a device ?

The first thing to note is that it is not necessary to add drivers for devices that are not supported in WinPE, the Rescue Media wizard will not force you to ensure that all devices are supported. The simple reason for this is that you may not be using certain devices when in WinPE, eg: NIC or USB controllers/hubs. The other thing to note is that you can update driver software as well. If a device is already supported you can use a different driver, you do not have to use the driver provided by WinPE for a device. This may prove useful if you are experiencing issues when performing backups/restores in WinPE, e.g.: slow restores from a USB device.

Once you have identified the drivers that you want to update:

• Select it by left clicking it in the list of devices.
• Click the Update Driver button. This will present another wizard. This wizard is relatively straightforward to use, the first page prompts you for a folder to scan for drivers and whether you want to include all sub-folders.

Click Next once a folder is selected and the wizard will scan for drivers. The wizard will automatically include the host operating system drivers if you do not choose to scan that folder. Once complete a list of results will be displayed, select the driver from the list you want to use and click the Finish button, this driver will then be copied to the WinPE disc. Clicking Cancel will abandon the process and not update any drivers. A sample screen-shot of the final page is below.

Macrium Reflect version 5.1 running on Windows 8, Windows Server 2012 or later.

Macrium Reflect version 5.2 running on Windows XP or later.

About the ADK

What is the Microsoft ADK ?

The Microsoft Assessment and Deployment Kit is part of the Microsoft System tools. It is designed to give system administrators the ability to deploy Windows on a large scale with a number of custom tools for preparing their systems. For example, it might be used by the IT department of a large company to roll out pre-configured Windows Installs.

You may already be familiar with the Windows Automated Installation Kit, or Windows AIK. This is the previous offering for Microsoft that fulfilled a similar role.

Why does Reflect use the ADK or AIK?

Both the ADK and AIK contain a component called the Windows Preinstallation Environment, or Windows PE. This is a version of Windows contained in a Windows Image, or WIM file, which is cut down from the full install of Windows but contains sufficient utilities for building recovery, install and system preparation environments.

Reflect uses the base PE environment from the ADK/AIK and customises it with the Reflect tools. This gives Reflect a rescue environment with access to a range of common hardware drivers as well as native support for Windows File Systems and Windows boot management utilities.

What is the difference between the ADK and AIK?

The ADK is a newer version of the kit designed for Windows 8. Each Windows PE version is based on a version of Windows. In the case of PE 4 (available in the ADK) the environment is based on Windows 8. In the case of PE 3, the environment is based on Windows 7. As such, PE4 supports a number of enhancements to the Windows boot environment which arrived in Windows 8.

When should I use the ADK or AIK?

If you have Windows 8, you should use the ADK if:

1. You only have Windows 8 drivers for your hardware. As PE3 is based on Windows 7, it requires Windows 7 compatible drivers. If you do not have access to these, but do have access to Windows 8, you can use the ADK and Reflect will copy your Windows 8 drivers from your system (or search for Windows 8 drivers as needed).

2. You require support for UEFI Secure Boot when using Fix Boot Options. Windows 8 is the first version of Windows to support Secure Boot and the relevant support utilities are needed by Reflect to correctly fix a system using UEFI Secure Boot.

You should use the AIK if you only have Windows 7 drivers for your hardware. As PE4 is based on Windows 8, it requires Windows 8 compatible drivers.

Can I use PE4 (ADK) to back up/recover a Windows 7 or earlier system ?

Yes you can.

Can I create PE4 (ADK) rescue media on Windows 7 or earlier ?

Only if running version 5.2 of Macrium Reflect or later.

Enabling the ADK

You can enable the ADK for your install of Reflect in two ways:

1. Download using the Macrium Reflect Download Agent, prior or post install. During rescue media wizard creation, you will be prompted for the location of the PE component file if you choose not to download using option 2 below. This option is useful if you are creating rescue media on offline computers.

2. Download using the rescue media wizard. Required PE component files will automatically be downloaded as required if you are online. Offline installations will prompt for a previously downloaded PE component file.

If you have never created AIK/ADK rescue media before

Reflect will default to the most appropriate PE base for your current operating system. PE3 (AIK) for Windows 7 or earlier, PE4 (ADK) for Windows 8/Server 2012.

If you have previously created rescue media, or wish to change the type of media you are creating

To change to the ADK, or switch your rescue media type:

1.In the main window of Reflect, click the rescue media wizard icon.

2. On the first page of the rescue media wizard, select the Windows PE option and then Click Advanced.

3. Select the PE base to use for rescue media creation, Click OK.

This article explains how to use the 'Fix Boot Problems' option to resolve common boot problems when restoring an image.

When restoring an image or cloning a HD there can be situations where Windows is unable to boot due to incorrect boot configuration. This article explains how Reflect enables you to resolve these situations.

Depending on whether the disk you have restored uses GPT or MBR partitioning schemes, the action you need to take may vary. This article covers both cases.

Fix boot problems on MBR/BIOS systems

Fix Windows boot problems is available in the Windows PE Rescue media environment. To fix Windows boot problems, start your computer with your rescue media inserted. Then, after a restore or clone, to use fix boot problems:

1. Select the restore menu, then select fix boot problems. Alternatively, choose the restore tab then under restore tasks select Fix Windows Boot Problems.

2. The Fix boot problems wizard will then open.

3. You will be presented with a list of Windows Installs, which the wizard detects. Verify these are correct. If the wizard has not automatically detected your Windows install, add it using the buttons on the right. You can also correct any details using the edit functionality.

4. Select the active partition. The wizard automatically selects the boot disk for the relevant Windows install, but you can change this if you are using an alternative setup:

5. Choose the boot options to be fixed. We recommend leaving all options checked, however, power users may wish to alter the behaviour of the wizard.

6. Click finish. The wizard will then offer you the choice to reboot. If you need to perform additional tasks in the PE environment such as ReDeploy, select no. Otherwise, select yes.

7. Your system will now boot.

---

Fix Boot problems for GPT/UEFI Boot Systems

Fix boot problems is available in the same location as for MBR systems. Boot your UEFI capable rescue media. Then:

1. Select the restore menu, then select fix boot problems. Alternatively, choose the restore tab then under restore tasks select Fix Windows Boot Problems.

2. The Fix boot problems wizard will then open.

3. You will be presented with a list of Windows Installs, which the wizard detects. Verify these are correct. If the wizard has not automatically detected your Windows install, add it using the buttons on the left. You can also correct any details using the edit functionality.

4. (Optional Step) if you have multiple disks, you may be asked to select which you should boot from. Choose the disk you wish to boot from, then press next.

5. The wizard will then display a summary screen. Press Next.

6. You will then see a report showing you a choice of actions and allowing you to restart your PC. Select Yes if you wish to restart now and select No if you wish to perform additional tasks in the PE environment.

---

Search terms

tag:restore

tag:image

The Linux CD is a compact and efficient rescue environment to restore all Windows operating systems. It will only enable your to restore your imaged partitions to exactly the same size and position as they were at the time the image was created.

If you require more flexible imaging and restore options or your hardware is not supported then use the Windows PE rescue environment. Note, RAID systems and disks attached via USB3 interfaces are not supported in this rescue environment.

It operates as a wizard, guiding you through locating an image, selecting what to restore and where to restore it to.

Image location

First a Macrium image file must be located.

1. Navigate to the folder that contains the image to be restored in the left hand pane. Possible locations are network attached disks, CDs or DVDs, internal hard disks or those attached via USB or eSata.

2. The backup list shows all backup images in the selected folder and the pane below shows the partitions included in the image.

3. Highlight particular backup image that you want to restore, the contents of which will be revealed in the lower right pane. If you have an incremental/differential set, chose the last image in the set, unless you wish to restore to an earlier point in time.

4. In the case that your images are multi-part images – typical for images stored on a FAT formatted device such as a USB hard disk or on CD/DVD recordable media, locate the last image in the set.

5. Note that the drive letters presented in the left pane may be different from those that Windows uses. If you wish to eject a CD, double click on the CD icon.

Select a network adaptor from the list and view or change the IP address and network parameters if incorrect.

Note: if there are no adaptors listed, then the Linux rescue disk does have support for your network adaptor. In this case, consider a windows PE rescue disk.

The "Set" button applies any configuration changes, and "Get address" attempts to acquires a new address via DHCP. This will have been attempted at boot time, but may need to be invoked manually, for example where a network lead was not connected at boot time.

Once you have located the image, you can proceed to next page.

Partition selection

You are now prompted to chose which disk to restore using the drop down list and then which partitions to restore. By default all partitions included in the image will be selected.

Target disk selection

Restore

You are presented with a summary of the restore operation that you have configured.

If you are happy to proceed, click Restore.

In the case that you have selected a multi-part image on a different disk such as a CD or DVD, you will be prompted to insert the disk containing the first and then subsequent image files as they are required.

What is Macrium Redeploy?

• Migrating to a new machine due to hardware failure or planned upgrade such as a new motherboard etc.

• Moving between a physical and a virtual machine (P2V / V2P ).

• Changing a non-raid to a raid installation or legacy SATA to AHCI SATA

There are various aspects of the windows boot processes that will typically cause a boot failure after significant changes to the hardware. The purpose of ReDeploy is to attempt to overcome these issues enabling a Windows installation to run on new hardware.

The discovery of hardware and association with a matching device drivers is a time consuming process. It must be undertaken when windows is being installed but then is skipped during a normal windows boot to make the boot delay acceptable.

Early in the boot process, the boot loader loads the windows kernel (the core of the operating system) and selected “critical” drivers required to get Windows up and running. If the new hardware configuration requires a new driver to read the disk containing the operating system then Windows will fail to boot.

Once the kernel and the critical drivers are loaded, the kernel is started. The kernel and its associated HAL need to match the motherboard for best enabling. A driver is optionally loaded to handle specific CPU features. Again, for a stable system,this driver needs to match the hardware – in this case, the CPU model.

ReDeploy is designed to detect changes to these critical system features,locate relevant drivers and inject them into your windows operating system to enable it to boot.

You will need to run ReDeploy from the Windows PE Reflect rescue CD. This allows the new hardware to be detected and the configuration of the Windows system modified to enable it to boot.

ReDeploy is designed make the complex process of getting an off-line windows operating system running as easy and intuitive as possible. What it will not do is install the complete driver set for the new hardware. You will be able to complete the driver installation for devices such as network and graphics adapters once your windows installation has booted on your new hardware.

Note: Image deployment to multiple PCs requires a deployment license for each PC deployed. Please see here for information on purchasing deployment licenses. If you deploy an image to a different PC then you should make sure your installed software, including Windows and Macrium Reflect is suitably licensed for the new PC.

Platform support

The Standard edition of Macrium Reflect v5 does not contain ReDeploy, neither do any of the 30 day trial editions.

Using Macrium ReDeploy

Note: ReDeploy will modify an existing offline operating system to work with new hardware. You should restore your system image to the PC being deployed before running ReDeploy. There is no need to reboot your PC after restoring an Image and before you run ReDeploy.

1. Boot the target PC with the Windows PE rescue CD or USB equivalent. (At bottom of this tutorial is a link to a video on creating a Windows PE rescue CD).
2. Take the ReDeploy Restored Image to new hardware option.
   
3. If you have a multi-boot system, then you will be presented with a list of operating systems, select the operating system to be redeployed. Click on 'Next'.
   
4. The following dialog will ask you to specify driver locations for your mass storage devices (such as RAID card). If you haven't already done so, please insert a driver disk for the hardware you are going to boot from. This will typically be the motherboard or RAID card driver CD, click on Add to add driver locations. You can also specify additional paths such as network folders, click on 'Map Drive' to add a network share. Then Click on 'Next'
   
   Note: ReDeploy will first search through any user specified driver locations. If none are specified or no matching drivers are found then removable devices such as CD's and floppy drives are searched. ReDeploy will also search through Windows' database of drivers.
5. ReDeploy will now seek drivers for all discovered mass storage devices and a list will be displayed with details to the right. Click 'Next'
   
   

   ReDeploy will now seek drivers for all discovered mass storage devices and a list will be displayed with details to the right.

   For each mass storage device, there are three possibilities:

   • The driver is already installed. It might still need to be enabled at boot – this will be done automatically.
   • The driver has been located, either from a CD, user specified path or from the Windows database. This driver will be installed on completion of ReDeploy.
   • No matching driver has been located.
   
   If no driver has been located or you wish to override the displayed driver, then the 'locate driver' button can be used to manually specify an .inf file.
   
   
   Note: If you have multiple mass storage interfaces in your system, then you only need to locate drivers for the hardware that contains the Windows system and active partitions.
6. The options on the next dialog maybe left at the defaulted values. If you have trouble booting then these options can help resolve issues. Click Next. For more information about the options please see below:
   
   
   
   1. Disable reboot on system stop
      Set this option to stop automatic rebooting if a BSOD occurs while Windows is loading or running. If this option is not set and Windows generates a BSOD, there will be no time to note the BSOD error codes.
   2. Display boot drivers as they load
      Set this option to show which drivers are being loaded as Windows loads. Once Windows is loading and running without issue this option can be reverted using the Windows MSCONFIG utility. You can use the Pause/Break key to freeze the list as it scrolls past, use space to un-pause.
   3. Enable boot logging
      Set this option to enable logging of drivers being loaded by Windows as it loads. The resulting log file 'ntblog.txt' can be found in the windows folder. Once Windows is loading and running without issue this option can be reverted using the Windows MSCONFIG utility.
   4. Disable CPU Driver
      Set this option to disable CPU drivers. This may be useful if you see BSOD's in the selected Hardware Abstraction Layer drivers or system lockup on entering standby or shutdown.
   5. Set Hardware Abstraction Layer
      Set this option to choose which Hardware Abstraction Layer is to be used in the selected Windows operating system. The recommended HAL for this machine will be the one initially selected. If you have the incorrect HAL configured, your Windows installation will typically be unstable and you will often see random BSOD's or lock ups after Windows has booted. In particular, if you are redeploying from or to Virtual Box with APIC unchecked (the default) or very old physical hardware, the you will need to set a new HAL.
   6. Allow Windows to detect Hardware Abstraction Layer
      Set this option to allow Windows to determine the best Hardware Abstraction Layer to use at boot time. For Vista, use this in preference to the “Set Hardware Abstraction Layer” option. This is a Vista and later only option.
   7. Enable SATA AHCI
      Set this option to enable support for generic SATA AHCI hardware. You will typically also need to enable an option in your BIOS for your mass storage hardware to operate in this mode. This is a Vista and later only option.
7. You will be presented with a list of actions that will be performed and clicking Finish will apply these options to the target operating system. A log file 'ReDeploy.log' will be saved to the drive containing the operating system redeployed.
   
   
   After clicking 'Finish' to inject drivers and apply your settings you get a confirmation dialog, and you can reboot your OS which should now be compatible with your new hardware!

ReDeploy does not detect any operatingsystems

Check that

• The OS has been restored or the disk containing it connected to the target PC.

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

Windows never boots – machine appears to cycle continuously

Windows is probably experiencing a BSOD on booting but it is displayed so briefly that your screen can't display it. Rerun Redeploy and set the “Disable reboot on system stop” option. Reboot and note the BSOD error code.

While booting Windows - Bluescreen message 0x0000007B

This is an indication that Windows hasn't correctly loaded, or associatedyour hardware with mass storage drivers for the disk containing the OS.

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

It can also be caused by your BIOS configuration – for example XP will not boot with AHCI SATA mode set.

While booting Windows - Bluescreen message0x00000024

This is an NTFS read error. It is likely that a single disk of a raid 0 or raid 5 set being mounted by the standard IDE driver.

After booting Windows – Two drives appearcontaining the OS image

If windows boots correctly and you have RAID 1 (Mirror) configured and you see your windows folder on two drives then Windows has used the standard IDE driver and you are not operating in RAID mode.

After booting Windows - Bluescreen message 0x0000007E

This typically indicates that the configured HAL is incompatible with the hardware.

Rerun Redeploy and either set the HAL to the recommended type or set “Allow windows to set HAL” if redeploying Vista or later.

After booting Windows becomes unstable or locks up.

The most likely cause of this the configured HAL being incompatible with the hardware. Rerun Redeploy and either set the HAL to the recommended type or set “Allow windows to set HAL” if redeploying Vista or later.

While booting Windows – Driver not signed error

You will see this if you are using 64bit Windows Vista or later and you have injected an unsigned driver. Reboot, hitting F8 to get the windows boot optionsmenu. Chose the allow unsigned drivers option and Windows should complete booting. Locate signed drivers from your hardware vendor and either rerun ReDeploy, using the Locate Driver option or use the Update Driver option in the Windows device manager.

Keyboard and mouse never become active

If the keyboard and mouse don't become active try reinserting the their USB connectors or moving them to different USB sockets. If you do have PS/2 devices available, then try those – note they need to be connected before the system boots to become active. If this does not help, try rebooting (power cycling is probably your only option).

With regard Windows XP / Windows Server 2003 operating systems

The XP/2K3 operating system kernel can take a long time discovering USB components and sometimes never actually discover them. To force discovery of USB items, perform the following steps:

• Download the following ZIP file: http://updates.macrium.com/reflect/v5.0/USB.zip
• Boot into WinPE.
• Copy the files from the ZIP to the following folders:
  • devcon.exe to the root of the operating system volume.
  • usb.bat to the root of the operating system volume.
  • usb.job to the \Windows\Tasks folder for your system volume.
• Reboot.

The job should run as SYSTEM user and invoke the batch file which in turn invokes devcon.exe. This should force a rescan of the USB devices in your system. A log file should be created on the root of your operating system volume of the devcon process.

If that doesn't help, then maybe your system has locked up. Consult the relevant troubleshooting section if this seems to be the case.

The backup destination is a password protected network share

When running a scheduled task network share access credentials may need to be supplied to Macrium Reflect defaults to allow access.

Take the 'Other Tasks' > 'Defaults' > 'Network' > 'Logon' and enter the logon credentials for your network share.

No backups exist for the same type in the destination folder

A common mistake is to create a 'File and Folder' full backup and then create and Incremental or Differential 'Image' definition, or vice versa.
Check that the backup file(s) are the correct type in the destination folder. Image files have the file extension '.mrimg' and backup files have the extension '.mrbak'.

Search terms
Backup Aborted
Differential error
Differential problem
Incremental error
Incremental Problem

For brevity, CD will refer to either CD or DVD.
Except where stated, it is equally applicable to linux or PE based rescue CDs.

Introduction

The causes of non-booting rescue CD fall into one of two broad categories, either it is an issue with your CD or with your PC.

Verify your CD

Try as many of the following steps as possible:

1. Try booting the CD on a 2nd PC.
   If it boots, this indicates a configuration or hardware issue with your PC. Please see Verifying your PC later in this article.
2. Try a different brand of CD media.
   We have found that CD recordable media is of variable quality. Often, using different media will resolve your issue.
3. Try creating the rescue media on a 2nd PC.
   If Reflect is installed on the 2nd PC, please try creating rescue media there.
   Alternatively, following the same CD creation steps as before, select Create ISO image file on the last page of the wizard. Transfer this to the 2nd PC and us a third party utility such as ImgBurn to burn the CD.
   In each case, try booting the 1st PC with the new CD.

Note: Booting from DVD and CD can take a while due to the time to load the large boot image, CD in particular can take up to 5 minutes. Unfortunately, on some hardware PE 4 does not show a progress bar during the loading period. Therefore, with a PE4 CD, please give the media chance to finish loading before concluding that it is not bootable.

Verify your PC.

To boot rescue media from CD, your BIOS or UEFI firmware must be correctly configured and have hardware suitable for booting. Please try as many of the following steps as possible to diagnose this.

Note that there is no standard for motherboard firmware configuration, so our instructions are necessarily non-specific. Please consult your motherboard manual for details relevant to your PC.

1. Try booting a Microsoft Windows install CD.
   If the boot fails, this is indicative the your hardware is incorrectly configured. Please continue through this list for further diagnosis.
2. Invoke your BIOS/UEFI boot menu.
   
   Boot menus vary in appearance and are invoked in different ways. You may need to refer to your motherboard manual to find the key combination to access this. Sometimes, this is displayed on the screen and is usually a key such as DEL, F8, F11, F12, F2 etc.
   Please note that on UEFI/BIOS dual systems, you may be given the option to boot UEFI or not for each device. Please boot the type matching your installed OS. There are a few possible outcomes:
   1. You are able to boot your rescue media in this manner, but not without performing this step. In this case, please see the next step in this section.
   2. You are unable to boot your rescue media having seen the hardware in the menu. In this case, you may wish to try the Verify CD steps above. If these do not rectify the issue, your hardware may not support booting Windows PE (you can also try this with the Windows Install CD to verify). In this case, please try an alternative rescue media format such as USB, or attach a different CD/DVD drive to the system.
   3. You are unable to see the hardware in your list. In this case your firmware has not recognised the device and it is not supported for booting.
3. Change the motherboard boot order.
   Please enter your BIOS or UEFI firmware setup utility and navigate to the "boot order" or "boot menu" equivalent screen. Please ensure CD/DVD booting has a higher priority than your hard disk, which may be labelled ATAPI, SATA, SCSI or various other labels depending on your system. Please press F10, or your equivalent for "save and exit" to reboot the system with the new priority.
   Please note that some UEFI firmware may not have boot priorities for removable media, or booting from removable media may be a configurable option that you must enable.
4. Create a USB rescue stick.
   Follows the same steps as used when creating a CD, selecting instead "USB media" on the last page. If this works and your have verified your CD, it is indicative that your hardware cannot boot a CD. However, a usb stick, is just as functional as a CD, so we recommend you use this as your rescue device.
   Note: This is only available for PE rescue media.

What to expect when booting rescue media.

1. The PE 3.0 environment is based on (a cutdown version of) Windows 7 and so boots in a similar fashion.
2. The PE 4.0 environment is based on Windows 8 and so boots in a similar fashion.
3. You may notice a lag during boot on CD/DVD rescue media whilst the WIM is copied into memory. This can take some time, so please be patient. PE 4.0 media on UEFI systems may additionally display no progress bar during initial load, so please be patient if you have a blank screen.

ERROR: Selected writer 'NTDS' is in failed state!
- Status: 11 (VSS_WS_FAILED_AT_POST_SNAPSHOT)
- Writer Failure code: 0x800423f4 (<Unknown error code>)
- Writer ID: {b2014c9e-8711-4c5c-a5a9-3cf384484757}

Type Error
Event 412
Source ESENT
lsass(800) Unable to read the header of logfile\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\Windows
tds\edb.log.Error -546.

The Problem

This problem occurs because Macrium Reflect requires elevated Administrator privileges to run. When a network share is mapped to a drive letter in Windows Explorer this is done using standard user account privileges not elevated privileges. Windows makes the mapped share 'visible' only to the standard user not the elevated Administrative user required to run Macrium Reflect.

Please note that this affects all UAC enabled Windows programs and is explained in more detail by this MS article:

http://technet.microsoft.com/en-us/library/ee844140%28v=ws.10%29.aspx

Solutions

1. Use the UNC path to access the network folder

Rather than browsing for mapped drive letter you can locate the same folder by entering/browsing for the full Universal Naming Convention (UNC) path, i.e, \\server\share.



In the above example the Server name is 'MyNas' the Share name is 'public' and the folder is 'MyFolder'. So the UNC path is \\MyNas\public\MyFolder'.

2. Alternatively, change Windows to make mapped shares visible

Note: This solution involves changing the Windows registry.

1. Press the Windows button, type 'regedit.exe' and press enter.
2. In the Windows that opens, navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System

3. Point to New, and then click DWORD Value.




4. Type EnableLinkedConnections, and then press ENTER.

5. Right-click EnableLinkedConnections, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. Exit Registry Editor, and then restart the computer.

After making this registry change network shares mapped to a drive letter will be visible to all programs, including those that require elevated privileges

This article explains the possible cause for the failure: Backup aborted! - Failed To Create Volume Snapshot. Result Code: 0x8004230c shown in the backup and VSS log when creating a disk image or a file and folder backup with Macrium Reflect. You may also see the following line in the error log: Error text: VSS_E_VOLUME_NOT_SUPPORTED

Description

The most likely cause of this error is that the Microsoft Volume Shadow copy Software Provider has been disabled. This essential core service is required to make volume snapshots on your system. Volume snapshots are used to create disk images and are also used by Windows to create system restore points.

Solution