Issues booting into new image
Using True Image 2016, I was able to create and backup an image, after sysprep, on an HP 6305 Small Form Factor desktop. Once that unit reboots, it loads Windows and I am able to move forward. However, trying to image the same model with the saved image will not boot. The machine goes into a loop, and will not load Windows. I have tried different configs in the BIOS, but that has no effect. Is there a different option during the saving image, or installing the image process that I need to take? Any assistance would be appreciated, as I have multiple machines to reimage in a short period of time, and will not be able to install from a base image during that timeframe.


- Log in to post comments

Steve, thanks for the reply. I used this process to create the image:
1. Used recovery disk to install Windows 7 and other drivers
2. Customized the profile and settings in the desktop to meet my company's standards
3. Ran a sysprep
4. After reboot, booted to Acronic to create a backup image to save for future deployments
5. After this process, the desktop rebooted normally
My issue is in trying to apply this image to another desktop. I used Acronis to restore from the saved backup, as I do all machines (desktops and laptops of different models). However, when the machine boots up after completion, it seems to be caught in a loop, and reboots contantly without loading the OS. I have used this process hundreds of times without this issue, even on this same model when it was imaged with Windows XP, which we are now upgrading to Windows 7. My question is if there is some process or setting, either during the saving process or restoring process I am using, that could cause this issue?
I hope this clears up what I am asking. If it is not an Acronis issue, I might need to do more research with HP (manufacturer of the desktop).
- Log in to post comments

James, it seems that what you are doing is fine upto a point, that is all the way to the point where you have restored the save backup image to the new computer system, but in fact you are restoring the image to different hardware and therefore should be using the Acronis Universal Restore tool before attempting to boot from the restored OS image on that system.
See KB document: 2149: Acronis Universal Restore which states:
It is designed to allow a machine to boot its operating system initially after a restoration/deployment of an image to hardware that is different from the one it was taken from, and then proceed with the installation of other drivers and configuration.
Acronis Universal Restore allows changing Windows Hardware Abstraction Layer (HAL.dll) and install mass storage boot device drivers into the system.
Although your HP desktops may appear to be identical, there may be slight differences that need to be dealt with.
See also KB document: 56637: Acronis True Image 2016: Restoring to Dissimilar Hardware with Acronis Universal Restore which includes a video tutorial, if needed.
Note: you may not need to add any additional device drivers to the AUR media as it should be sufficient just to run it.
- Log in to post comments

Thank you for the information. I will check it out, although, I have never come across this before, even on previous imaging with the exact same devices 2 years ago.
- Log in to post comments

James,
If you have a spare drive, I would remove the drive from the computer that was used to make the backup, install the spare drive, then perform a restore operation to that drive, and see if the computer boots. If the restore to the original computer has the same problem, then the issue is in the backup that you created. If the backup is good, then you will have to try Universal Restore.
When creating the backup, you should perform a disk mode/full partition list backup. Picture below:
FtrPilot
Attachment | Size |
---|---|
373905-131452.jpg | 171.19 KB |
- Log in to post comments

If the hardware is different, then UR is the way to go as it will generalize the drivers to a generic state like a fresh build of Windows. You usually get a bootloop or BSOD if there are incompatible or non-existent drivers when trying to restore an image to different hardware.
FYI - there is a sysprep limit as well if you sysprep the same image over and over - in Windows 7 and newer, it is 3 times. You can get around this by using a base image and updating it and making an image of it to always keep available. Then sysprep and make a new image for deployment. Go back to your original image so that you don't have one of your syspreps wasted if you plan to update the base image down the road again.
FYI 2 - no need to sysprep if you are deploying images to a non-Active directory environment. If the goal is to generalize the image for deployment to new/different hardware, you only need to run Acronis Universal restore to generalize the drivers
FYI 3 - make sure the SATA mode in the bios is the same on both systems. If you create the image on a system where the OS was installed with the bios set to AHCI, but then attempt to restore that image on a system with the bios sata mode set as RAID or SATA, it won't boot (Win 10 is good about this, but Win 8.1 and Win 7 are very picky about this). Making sure they are both the same on both systems will help rule out issues.
FYI 4 - how you boot your reocvery media for a RESTORE, makes a difference. If your original image was created on an OS installed in Legacy/MBR mode and you attempt to restore to a newer sysetm that is configured for UEFI, you tpically want to try to restore the image in the same manner as the image was ceated. Booting your recovery media in UEFI mode will attempt to restore the paritions with a UEFI layout. Booting your recoery media in legacy mode will attempt to restore the partitions with a MBR layout. You can go from MBR to UEFI (usually), but you can never go from UEFI to MBR with Acronis.
- Log in to post comments