Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When Windows is installed it searches it's driver database and installs the appropriate HBA driver so the boot loader can access the drive and boot the system. When an image is taken and cloned to a machine of an incompatible HBA type, Windows will fail to boot with a 7B (inaccessible boot device) error because it doesn't rescan for HBAs every boot.

What are ways of getting a Windows image that was created on a machine with one HBA type to clone onto another with an incompatible HBA type? For example non AHCI to AHCI, RAID to non-RAID, IDE to SCSI, etc...


  1. Free methods are preferable.
  2. The image can't be pre-syspreped and loaded with drivers for a bunch of different HBA types.
  3. I also may not have the system type the image was taken from in the first place.
  4. I'd like to stay away from the Windows repair approach because I think that makes other changes other than just fixing the HBA driver (if it even does fix the HBA driver).

The only way I've been able to get this to work is to:

  1. Install a fresh copy of Windows onto the machine I'm cloning to. F6 driver additions added if required.
  2. Extract the CriticalDeviceDatabase registry information and driver sys files with a script I wrote.
  3. Image over the machine with the incompatible image.
  4. Boot up into ERD commander and attach to the Windows install and import the registry data and driver files I previously extracted.

This typically works however it's not particularly easy and ERD commander is aging. It's not even based on WinPE.

The reason I use ERD commander is that it can attach to the registry hive with read/write access and has read/write access to the disk. I use both of these capabilities to import registry data and driver files.

So far this approach has generally worked for me however I want to see what other ways people have to solve this problem considering the constraints I've listed.

share|improve this question
Any why can't the machine be sysprepped? – MDMarra Oct 18 '12 at 15:33
What happens when the original hardware is not available and all you have is the ghost image and the target machine? – Andy Arismendi Oct 22 '12 at 19:06
Restore it to the target, sysprep it, recapture. – MDMarra Oct 22 '12 at 19:07
I think sysprepping requires you to be able to successfully boot first. No? – Andy Arismendi Oct 22 '12 at 19:09
You listed a workaround that will get you a bootable machine with your current image. You can either do that or build a new image. Personally, I'd build a new image and do it right from scratch. – MDMarra Oct 22 '12 at 19:10

Acronis Backup & Recovery (with the universal restore addon) can do this. In fact you can also create a customised acronis cd with all the drivers you wish to take care of things like sound cards, graphics cards, as well.

It's not free but not expensive at all (last license I purchased was around £50).

share|improve this answer
Thanks, just read through the product page. Does it only support acronis images? – Andy Arismendi Feb 9 '12 at 2:53
As far as I know, it does only support Acronis (*.tib) images. – Robin Gill Feb 10 '12 at 16:06

A machine should be sysprepped before it is cloned. Sysprepping will cause the clone to re-scan for drivers on the next boot, among other things. Any other service that supports a dissimilar restore is going to either transparently call sysprep or use a similar technology that mimics sysprep. I suggest finding a way to remove the "I can't sysprep this image" constraint, as it is a pretty unusual one.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.