Skip to main content

C_drive failure after restore from backup to a new drive

Thread needs solution

I think there are some problems with TI2018 when trying to restore boot disks.  I haven't tried cloning yet, but I did create a backup of an SSD that was working in a Win7 machine and then restored to a second SSD, causing the first original SSD to fail. 

 

1) Created a backup of the C_Drive (Samsung EVO 850 500GB)

2) Connected a brand new 2nd identical EVO and did a restore from the backup in 1) above to the 2nd EVO

3) Shutdown the computer and swapped EVO's to make sure the newly restored one worked ... rebooted and it worked

4) Put the original EVO back in and received a bootup error that winlogin.exe was missing

5) I checked the BIOS and the original EVO was properly listed as the 1st boot device, and, in fact, Windows kind of started up until I got the Winlogin error

5) Put the restored EVO back in and it worked.  

So, something happened to the original C_Drive AFTER I restored a backup to a new C_Drive (never had this happen before)

 

Note: I've been using TI since TI v6

0 Users found this helpful

I haven't heard of any problems being caused by restoring a backup image to a second drive where the first drive is corrupted / unable to boot correctly afterwards.

From the information given, the backup image sounds to be good as you were able to restore this to the second EVO SSD and was able to boot successfully into Windows from this SSD.

When you checked the BIOS Boot Priority settings, were you only given the physical SSD drive or were you given an option for the Windows Boot Manager?  If the latter was offered, then this is the boot device that you should be using.  Windows Boot Manager should be used where you have UEFI BIOS, otherwise for Legacy BIOS, it should be the SSD drive.

In reply to by truwrikodrorow…

when I received the error on bootup from the original SSD the error was generated by Windows Boot Manager.  The bootup disk in the BIOS was the SSD drive, just as it is now with the second (working) SSD.

If the error came from having Windows Boot Manager selected but it is working with the SSD drive selected in BIOS, then it sounds like you have a UEFI capable computer being booted in Legacy / CSM mode, thus not using Windows Boot Manager.

In reply to by truwrikodrorow…

It is UEFI and not in legacy mode ... I am pretty sure this is an Acronis problem.  

Can you provide pictures of bios settings that confirm UEFI/CSM mode and Boot Priority settings?

I can't. Since the drive was useless, I went ahead and deleted the partition.  I'm going to restore it again from a backup, but this time I'll use the Linux bootable CD to do it.  Not taking any chances with TI2018 for doing disk restores though the Windows GUI... it's not safe.