Skip to main content

Recovery windows 10 in a loop

Thread needs solution

The proces as described in acronis document 59870 "restore within running windows" goes well as described but ends in a loop. There is a kind of dos environment in which the PC keeps shutting down and restart but I don't know how to stop this other than a hard shut down (cutting off the power) of the computer. The same ending I do see when cloning the disk. After the hard shut down starting the system shows the restore/clone was succesfull.

What is the right way ending the loop? What I'm doing wrong?

Windows 10

Crucial SSD

0 Users found this helpful

Niko, welcome to these public User Forums.

KB 59870: Acronis True Image: how to restore the system to the original disk from within running Windows - is fine in principle but can lead to the situation you find yourself in, and thus is not recommended by the MVP's helping with this forum!

The issue here is that doing a restore / recovery started from within Windows causes Acronis to modify your Windows Boot Configuration Data (BCD) in order to create a temporary Linux based environment from which to launch a standalone ATI application.  This Linux environment may not have support for some modern disk drives and has not support for devices using RAID.

The first question here is:  Did you see any evidence that after doing the Restart at Step 11. in the above KB document process, that any data was actually restored to your internal drive?

If you just saw the computer restarting over and over without restoring any data, then you will be in a recovery scenario that will need either the Acronis bootable Rescue Media, or else a Windows 10 Install or Rescue DVD or USB stick.

If you have the Acronis Rescue Media or are able to create this on a different computer with ATI 2019 installed, then you could boot from this and attempt to recover / restore your backup in that way, which in turn will restore the Windows BCD to how it was when the backup was created.

Note: booting the Acronis Rescue Media needs to be done in the same BIOS mode as your Windows 10 OS uses.  Given you cannot boot Windows to run commands from the desktop, you will need to look at the BIOS Boot settings to check what mode Windows uses.
If in the BIOS Boot settings you see 'Windows Boot Manager' as the primary boot device, then this is a UEFI boot system, otherwise it is a Legacy boot system.

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

A live restore of OS SSD uses a temporary Linux distribution. When the restore is completed the recovery installation closes and either deleted the temporary Linux installation or creates a script that deletes it when next the PC is booted. In your case this is not happening for some reason.

what. Build of Windows 10 are you running? What build of ATI 2019. Any denials about the PC.that might help us work out what is going wrong.

Ian

Thanks for this fast reply!

ATI 2019 build 14350

Windows 10 home, 64 bits version 10.0.17763 build 17763

I'm not a real expert!😏

After I've stopped the loop by cutting of the power and restarting the pc the data were restored well. So for the moment there is no problem till the next restore.

So only finishing and deleting the linux environment seems going wrong? Is there a linux command that I could use for ending this loop. Do I have to delete this linux application or does it gone?

I have recently cloned my hhd to a crucial ssd and the first cloning was going well without the above loop. After a crash I had to reinstall the system on the ssd and then the problem did start as well with the cloning and afterwards installing or more recent the backup of the ssd.

On the ssd as well the hdd is the system so I can boot from both.

When there is no solution within windows the next time (I hope it wont come because I have found the cause of the crash) I can use the acronis rescue disk.

Niko

Niko, good to hear that doing a full power down allowed you to get out of the loop and that the restore was complete.

Please see KB 61621: Acronis True Image 2019: How to restore your computer with WinPE-based or WinRE-based media - for more information on using the rescue media for recovery.

-

This might be what you are asking for Linux Shutdown

Thanks all for the help that will make it a lot easier the next time I have to go this road!

@ enchantech: what is the exact command I do have to type for poweroff: "[-d<delay>] "or "-d<delay>"?

I'm not that used to linux 😉.

poweroff is the command.  the -d is what's known as a switch to which you can specify an amount of time to delay the command.  The KB should read poweroff [-d <(sec) delay>.  Thus a 30 second delay to poweroff would be poweroff -d 30

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 2
Comments: 1727

Robert Smith wrote:

I have fixed my problem by cleaning boot your computer.

Hello Robert! 

Thanks for sharing your experience.