Direkt zum Inhalt

True Image For Crucial Bootable Media Hang Up

Thread needs solution

Hello, I'm a new user in need of some help. While upgrading my HP Envy M7 laptop from 1TB HDD to a Crucial MX500 3D NAND SATA 2.5" SSD using the clone feature in the True Image For Crucial s/w, I followed steps I read here in the forum and on Acronis' support pages and created the USB bootable media, was able to boot successfully (blank drive in laptop, HDD attached externally), but then the program just hangs as shown in below pic- I can't access any features in the program or select any options to start cloning, and have to reboot to regain access.

Any help would be greatly appreciated!

Mike Norris

0 Users found this helpful

Mike, welcome to these public User Forums.

See KB 2201: Support for OEM Versions of Acronis Products which applies to all OEM versions of ATI supplied with hardware purchases.

I would recommend strongly making a full disk backup of the original working HDD drive before embarking on using cloning - this will be your safety net in the event of any mistakes or issues arising.

However, if the Crucial ATI rescue media is hanging when you boot from it then there are other issues at work here, potentially device driver related?

I would suggest reinstalling the original HDD in the laptop, and if not already done so, installing the Crucial ATI application in Windows.

Assuming that you can launch ATI in Windows (you may need to have the Crucial SSD connected to allow activation), then first make a disk backup of the HDD to an external backup drive.

Next, try using the different options in the Acronis Bootable Rescue Media Builder tool to create the rescue media, i.e. use the 'Simple' method to create WinPE based media using files taken from the Windows Recovery Environment on the HP Envy laptop.

Test booting from the rescue media to see if you can get beyond the hang previously seen? If yes, then shutdown, remove the HDD and replace by the SSD, then boot from the same rescue media along with having the external backup drive connected, then do a Recovery of the full disk backup to the SSD instead of doing a clone.

Note: when using the rescue media it is very important to match the same BIOS boot mode that is used by your Windows OS on the laptop.  You can confirm the BIOS mode by running the 'msinfo32' command in Windows, then look for BIOS mode in the right panel - this should normally be UEFI for most modern / recent PC's.

See KB 65508: Acronis True Image 2021: how to create bootable media and KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media

KB 65520: Acronis True Image 2021: how to back up files or disks

KB 65539: Acronis True Image 2021: How to restore your computer with WinPE-based or WinRE-based media

Thanks for the info and guidance, Steve!  I will try the steps you outlined and see where it takes me; might be a few days before I'm able to try everything.

Steve, I followed your steps and reinstalled the HDD and the ATI s/w,  then created the bootable restore files on a DVD, which worked fine.  I also ran checkdisk on the SSD from another laptop and found no bad sectors but it seemed that windows had a hard time recognizing the SSD (it eventually did).  I booted my target laptop from the bootable DVD and it came up fine, and I was able to access the restore program and start the clone with SSD in the laptop and original HDD connected via USB; however, it kept failing saying there were bad sectors on the SSD.  I tried several times but kept getting the same errors.  I took the SSD out and am taking it back to the store for a replacement unless there is something else I'm missing.

I exchanged the SSD for a new one and reattempted the clone process, but ran into another issue with the ATI saying the target drive was locked; read some previous forum articles about using ATI Linux format to reboot instead of WinRe- did that and everything finally worked- laptop is running fine on the SSD.

Thanks for your advice, Steve!

Michael, glad that all is now resolved after changing the SSD - thanks for the feedback!