Cannot restore C: drive. ATI aborts.
I'm at a loss. Have been using ATI for at least a decade with no issues. Use on two PC's, both running Win10 Home. On desktop PC, runs fine. On laptop (Lenovo Y700, purchased March, 2016, came with Win10) ATI worked fine up until I upgraded from 2016 to 2018 versions. Instantly, could no longer restore start-up disk using the ATI backup I have scheduled to run every night. Would run ATI, all systems go, but when ATI forced a restart, something would "break" and the process would abort and take me back to the desktop. This meant that even though I was creating a nightly ATI backup, I couldn't use that backup to restore the internal C: drive. I finally discovered that I could use another program (Macrium Reflect) to create and restore my C: drive to a second identical NVMe drive in an external USB enclosure. I'd much prefer to use ATI, since prior to these problems I simply had to run ATI to "restore disk", restart, and by the time I got back to the desktop in about 30 minutes I had a fully restored PC. With my Macrium solution, I have to run the restore process, then take my laptop apart to switch in the second NVMe drive. Much more of a hassle. But at least it works.
As I said, I was having absolutely no issues with ATI until I tried upgrading from 2016 to 2018 versions. Once I realized ATI 2018 wasn't working properly, I uninstalled 2018 and reinstalled 2016 -- but now that version no longer worked either. (I left 2018 on the desktop PC, since there were no issues there.) Still hoping for a miracle, I just upgraded to ATI 2019 from 2016, but have struck out again.
So this is where I stand now: ATI is basically useless on my laptop. Below are the messages which flash by on the black screen after a restart, before the Lenovo start-up logo appears, and just before the process aborts and I'm returned to the desktop:
Starting x64 UEFI loader (v.1.1.51)...
Runtime error:
Error 0x1480008: Cannot get file "acroldr/kernel64.dat" from the partition with GUID 8520D290-5060-4986-B539-4145BC847E12.
| line: 0x76df0d19c4c85714
| file: K:/51/loader/efi/config.cpp:702
| function: GetFile
| $module: bootwiz_efia64_51
|
| error 0x1480018: Failed to open the volume by GUID.
| line: 0x76df0d19c4c856f8
| file: K:/51/loader/efi/config.cpp:674
| function: GetFile
| $module: bootwiz_efia64_51
|
| error 0x10d00e: Failed to find.
| line: 0xec492506f42e4d9
| file: K:/51/fdisk/volume_efi.cpp:115
| function: OpenVolumeByGuid
| $module: bootwiz_efia64_51
A few other data points:
Do not have a K: drive. I'm assuming ATI creates that drive to use when it forces the restart and then tries to find the K: drive to run the pretty blue ATI screen I used to see during the restore process. (Haven't seen that screen in months.)
In the ATI forums I found a thread discussing similar issues. A suggestion which seemed to work for that user was installing Intel Rapid Storage Technology; which I did. I also went into my BIOS and made the only change which seemed boot-related, which was to turn on "PXE boot to LAN". Neither had any impact on my system, and I'm still seeing the same messages as above when trying to restore.
My issues may somehow be related to fact that I upgraded internal SSD from SATA 3 to NVMe. Now using 500gb Samsung 970 Evo, which is about as common a drive as is available, so it should work. (I don't recall the exact timing of when I switched to the NVMe drive, and when I realized ATI wasn't running properly and I couldn't do restores of the C: drive.)
I use a RAM disk (disk D:) to handle browser cache and TEMP files. Could ATI be writing something to that disk, but then on startup cannot find it since it's not loaded yet? Have used RAM disk for years, while using ATI 2016 and previous versions, with no issues.
That's all I've got. If anyone can help me return to being a happy ATI user, I'd appreciate it.


- Log in to post comments

Steve, this looks to be a continuation of topic: ATI resets boot drive after restore to back-up SSD - that you raised at the end of December 2018.
The answer here is really the same as I gave for the other topic, that ATI is not designed to work in the way you are using it here.
As you now have ATI 2019 which is fully supported by Acronis, I would recommend opening a Support Case direct with Acronis Support and discussing your requirement to be able to backup your main OS and restore this to a second drive in the same system, so maintaining two identical copies of your OS in that system.
- Log in to post comments

Couple more notes. .
Make sure your bios is in UEFI mode. An NVME drive can only boot when it is uefi/GPT.
If the current OS I'd legacy (probably not but could be) then you need to boot the rescue media in UEFI mode too so that Acronis can restore the backup in UEFI/GPT.
After the restore, check the bios boot priority to make sure "windows boot manager" is listed as the first boot option.
Also make sure that you disconnect the original SSD (if still attached) before attempting to boot the restored NVME so the bios doesn't freak out if it detects the signature to be the same on both drives...otherwise it may panic and try to "fix" the issue by changing the bootloader on both disks, which often results in neither drive booting and may require a boot repair using a Windows installer disc. This is a bios issue though and completely avoidable by only having one OS boot drive connected after restoring to a new or different drive.
- Log in to post comments

Wow! Thanks to Bobbo and Steve for the amazingly quick replays. I've started re-investigating my system and will report back.
I did just look at my BIOS settings. I had "Secure boot" enabled; have now disabled and will see what happens. I disabled "PXE boot to LAN" which doesn't seem to apply to me. Also, I saw that my system has something called "Fast boot"; I've never used that, and it was disabled both when I made above post, and months ago when ATI 2016 was working "properly" (ie, the way I'd always used it, which apparently is not as designed.)
I also have "Intel Platform Trust Technology" enabled. Not sure what that is, but didn't change that setting.
My laptop does not have a RAID option in BIOS. I have never used Bitlocker (though I am considering it, and just yesterday plugged in a TPM module on my desktop PC motherboard. (The laptop already has one.) I'd have to upgrade to Win10 Pro, but I'm nervous about blowing up my systems since it's not really a tech I've ever used.
I've never used WinRE or anything other than "straight" ATI. And, it never occured to me that I was using ATI incorrectly. For years, it worked beautifully for me. If I, say, updated Firefox and found that an extension no long worked that I need, I didn't need to try to repair it. I just nuked it. I'd fire up ATI, tell it to restore the C: drive, let it restart, and basically come back in a half-hour to a system that had been taken back in time to the nightly back-up. I keep most of the files I work on in Dropbox, so those files were restored upon restart. I loved it. That's why I'm a little disappointed to learn that I've apparently been tempting fate by using ATI the way I've been for so many years.
Anyway, I'll keep investigating.
Steve, regarding my post from December:
That query was related to my desktop PC. When I said above that ATI "runs fine" on that system, I meant that I could restore the C: drive (on a 525gb Samsung 960 Pro NVMe SSD) to an older 240gb Samsung 840 SATA I keep in an otherwise unused drive bay -- and have it all work afterwards. That 240gb drive is simply a back-up, and so far I've never had to use it as a primary drive.
After a restore and restart, I have now gotten in habit of pressing the "Delete" key to take me to the BIOS, and switching the start-up drive back to the Samsung 960. I also double-check the volume size of the C: drive in Windows; if it says 476gb, then I know I'm running off the 960. Once it's all locked down, I don't have to think about it until I update my back-up drive again.
I guess overall I'm surprised to hear that I've been using ATI incorrectly. When I open ATI, I can click on a tab that says "Recovery". It then shows me "My Computer" and a listing of individual files, which is not what I want. At the bottom of that window is a box which says "Recover disks" -- which is what I want. I click that box. I select the recovery file I want, wait a few seconds while it lists the available disks on the system, and then choose the one I want to recover to. I go through a few more steps, and then the system restarts. In the past, this used to work flawlessly -- and saved my butt many, many times. I came to rely on it. Now it doesn't work, probably because of the NVMe issues. It's frustrating, but not fatal. I'll keep investigating.
- Log in to post comments

Steve, it is not that you have been using ATI incorrectly when restoring your second drive from your backup of the first drive, but that this is involving multiple copies of the same Windows OS on different disk drives in the computer.
You may find that if your target drive is blank when either restoring or cloning to it, that this may avoid the need to reboot the computer into the temporary (Linux based OS) environment, but you will probably still need to check that the BIOS boot device settings are correct after doing so.
- Log in to post comments

I agree with Steve. It's not to say that you're using it incorrectly. The issue is that each bios firmware can behave differently so the idea is to try and minimize potential, but common issues people run into with Acronis, and/or other backup products.
In most cases, using g the rescue media to restore a full OS can avoid a lot of potential issues with being able to boot into recovery. As bios security and technlogy keeps changing, newer systems tend to have UEFi, secure boot and even bitlocker enabled by default... Making nit just the default Linux environment less friendly, but all boot media not related to the original OS. It's really just about limiting certain potential issues, to give the best recovery scenarios since there is no standard bios scenario where all systems behave exactly the same.
Acronis can do what it says it can, but variances in the OS version, disk partition type and bios settings across different hardware make for different challenges on different machines.
- Log in to post comments

Steve and Bobbo, thanks for your attempts to help me get ATI working again the way it used to, for me anyway. I'm sure I'll find some workaround that gets the job done.
- Log in to post comments

SteveJH,
If you need help, just let us know. With a good backup, as long as there is a will, there is a way. The rescue media (WinPE/ WinRE version) has been my best friend for data recovery and OS migration to new disks for quite some time now.
- Log in to post comments

Hi SteveJH ,
If you are not sure how the Hard Drive is set up, download Visual BCD Editor. from https://www.boyans.net/
This program installs on all Hard Drives, but works best with Hard Drives in the MBR Configuration.
I have two Desktop Computers with at least 3 Hard Drives, with multiple partitions on each Hard Drive.
My point is this, if your Hard Drive is set up for MBR running, as mine is, configuring Acronis True Image Bootable Rescue CD to boot up with x64 UEFI loader (v.1.1.51)... as you stated above and you have Secure Boot turned off in BIOS, the Acronis True Image Rescue CD, will not start up.
I do not use the Acronis True Image Bootable Rescue CD on those Desktop Computer. I have multiple partitions and operating systems. To Restore the other partition / operating system, I use my other operating systems.
- Log in to post comments

Hi all
I'm struggling here, and hope someone might be able to help.
I'm on a trial version of Acronis, and have created a backup file from my laptop, carried out a factory reset on the said laptop, and am now trying to do a recovery based on that backup file.
I'm getting a very similar error message to the OP above, and thought it might be worth commenting here as opposed to opening a new topic.
I've installed Acronis on the brand spanking new OS, (Windows 10 Home, v. 10.0.1.19402), connected the harddrive where the tib files are located, added the files to Acronis via the "add backup" option, then tried to start an Entire PC Recovery process after validating the files.
Upon restart, I'm getting this error:
Starting x64 UEFI loader (v.1.1.120)...
Runtime error:
Error 0x1480008: Cannot get file "acroldr/kernel64.dat" from the partition with GUID D47B673-xxxxxxxxx.
| line: 0x76df0d19c4c85701
| file: c:/jenkins_agent/workspace/mod-acronis-loader/120/product/loader/efi/config.cpp:683
| function: GetFile
| $module: bootwiz_efia64_120
|
| error 0x1480018: Failed to mount the partition.
| line: 0x76df0d19c4c856e0
| file: c:/jenkins_agent/workspace/mod-acronis-loader/120/product/loader/efi/config.cpp:650
| function: GetFile
| $module: bootwiz_efia64_120
I have formatted the areas that are different to the OP's.
Some notes:
- I accidentally used a drive formatted as FAT32 instead of NTFS on the 13/04/2021, 4:26pm, which has resulted in 35 tib files instead of just one. I have added all of these files to the backup, and it shows up as a version 13/04/2021, 3:01pm, which I have attributed to the backup probably starting at 3:01pm and ending at 4:26pm
- After giving that error, laptop reboots and I get the same OS (settings, files etc) as the factory reset version but Acronis tells me that it's recovered successfully
- I've been a little cheeky because money has been really tight (am tbh struggling just to pay rent atm) - I installed and did the backup on an Acronis trial version on the 13/04, and am trying to do a recovery one day after the 30 day trial, so I registered a different account. I'm not sure if this affects the recovery?
Could anyone pretty please help?
- Log in to post comments

HH C, welcome to these public User Forums.
Sorry but more questions than answers at this point.
What version of ATI have you been using for this trial? Is this ATI 2021 which is the current latest version? This forum topic is in the ATI 2019 forum and that version is very different to 2021.
Are you able to create the Acronis Rescue Media on either a USB stick (2GB - 32GB size) or on a DVD disc? If you haven't already done this, please do so now using the 'Simple' method.
What did you backup when you created the .tib files?
Note: if you only backed up Files & Folders from the laptop, then you cannot do an 'Entire PC' recovery from that backup - put simply, it does not contain any partitions as the error messages are reporting!
An 'Entire PC' backup is a Disks & Partitions one that captures all installed fixed disk drives and all partitions on those drives, and with ATI 2020 & 2021 this creates .tibx files, not .tib.
.tib files are only used in these latest versions of ATI for Files & Folders, but should never be used to backup the Windows OS files / folders or those of installed Programs, as will always be missing important files due to these being locked by the OS, including the Windows Registry files.
If you are attempting to restore installed programs etc, then sorry but Acronis cannot be used to do this.
See KB 19296: Acronis products cannot be used to transfer applications to different system or upgrade OS
- Log in to post comments

Hi Steve
Thanks for the amazingly fast response.
I am using ATI 2021 (and .tibx files) - Apologies, I didn't realise there was a separate forum.
Just writing to let you know that I've managed to get it sorted! I re-tried Acronis Rescue Media, which got me going (after I'd realised that I should select the full disk, instead of individual partitions). It's strange though - When I previously tried using Rescue Media, it recognised the HDD plugged into my other USB port, but I was unable to select it. Shut down laptop, ignored it for 3 days, then did exactly the same thing, and... it works! Don't know what I did differently the last time, but I might just have been tired from troubleshooting for 5 hours straight.
Thank you once again for your help - You've made my day!
- Log in to post comments