Skip to main content

TI 2016 cannot recover from Windows 10 directly with NVMe as boot device

Thread needs solution

Warning for all users using NVMe als boot device: You cannot recover directly from Windows 10, it will stop with an runtime error and bios message! In Surface Pro 4 you won't see any message, it's yust booting again.
This behaviour is also known for all tablet devices like Microsoft Surface Pro 4, which are using an NVMe.

Recovery is only possible with boot media in newest builds 6569, 6559!

I'm using several NVMes like Samsung 950 Pro 512GB, SM951-NVMe 256GB (in Surface Pro 4) and a SM951-NVMe 512GB.

Bug is reported several times to Acronis Support, but they want money from me to fix this! Thank you Acronis that we users have to pay for your bugs in this programm. :(

0 Users found this helpful

Michael, I would recommend using the Feedback Tool in the ATIH GUI to pass on these comments directly to the developers and to attach a System Report from your Surface Pro 4 device to enable them to look more closely at the technical data from this.

Thank you for posting this warning for other users of these devices.

Hi Steve,

thank you for your comment. I had already contact to Acronis Support, I reported this problems 4 months ago with all information and reports they needed. But I won't pay for additional support, when theses problems are clearly bugs!

Michael your statement is inaccruate.   

I have a 950 Pro and have no problem making a backup and restoring to it with Windows 10 - I have done so several times (even with v6027 and WinPE rescue media, but now use v6569 since the default bootable linux recovery media has the drivers now).  However, I always use the offline bootable recovery media for this purpose.  If you have not done this, you need to be familiar with the process.  You also need to be sure that you're backing up the entire Drive contents and not just the C: drive to make sure you are backing up the boot partition.  

117004: Great Acronis "How-To" videos and other Acronis Resources

02 - SunGod2009 - How to backup and restore using Acronis True image - YouTube

Did you create bootable media?  If so, what process did you use (don't burn an .iso and tranfer to a USB - use Acronis to build it automatically)

What version of ATIH did you create your bootable media with? You should be using v6559 or 65569 for NVME driver support in the default Acronis bootable LInux media. 

Can you even boot into the online recovery media or have you tried? If you can't get into the boot media you need to make sure you boot it in the same manner as your OS was installed (UEFI if OS was installed UEFI, or Legacy if it was installed as Legacy - surface pro should be UEFI by default).  On the Surface Pro's you need to have secure boot disabled.  You may also need to disable TPM to get bootable media to boot correctly.  Then use your boot override to pick the USB drive and boot into it.

@Bobbo_3C0X1

With CPU and Mainboard you are using here? I have 2 computers, one with Gigabyte X99-UD7, i7-5820k with SM951-NVMe 512GB, and a home server with Asrock Z170 Extreme 6+ with an 950 Pro, and additionally an Surface Pro 4, and all devices can't not recover directly from Windows 10! Asrock print a message, see attachment.

With bootable media it is possible to do recovery, as you told with v6559 or 65569, now. Right. But thats not the point. I want to recovery directly from Windows, with is described in official Acronis Docu:

ATI2016_userguide_de-DE.pdf, Seite ab Seite 89

5.1.2  Volumes und Laufwerke wiederherstellen
Sie können zur Wiederherstellung Ihrer Laufwerke Backups verwenden, die sich auf einem lokalen Storage, einem Netzwerk-Storage oder in der Acronis Cloud befinden. 

And you can't tell me I'm doing anything wrong when this recovery from running Windows 10 from 3 different pc or devices doesn't work. In my opinion you never made a recovery directly from running Windows 10 with an NVMe as boot device.

Attachment Size
356228-128758.jpg 59.26 KB

My system info is in my signature.

I'm familiar with the documentation.  There is no recovery of a full system (disk or parition) in Windows - ever.  You can start the process from Windows, but then it will always shut down the system, attempt to create a new partition using Linux (Acronis System Recpvey Manager - ASRM) and restart the machine.

This is risky... I would not do this as it modifies the system bootloader and if it fails to boot, could render the system unbootable.  To avoid unnecessary modification of your system bootloader, you should use your offline recovery media when doing a full system restore. This will work.  If you choose not to though, this is up to you.  

I have recovered using the bootable media with the 950 without issue.  I will never start the recovery from within windows (ASRM), regardless of hard drive because it attempts to modify the existing windows bootloader and I am not willing to allow any program to make such a change to my system, especially when I can boot to the recovery media to accomplish this without any impact the local hard drive and/or OS.

Have you attempted to load from rescue media yet to see if you can even get that to work on your device?

> There is no recovery of a full system (disk or parition) in Windows - ever.  You can start the process from Windows, but then it will always shut down the system, attempt to create a new partition using Linux (Acronis System Recpvey Manager - ASRM) and restart the machine.

That's correct, but you don't need any separate boot device in this case. ;) As you told correctly, Windows is rebooting into another os, and this working over the years always correctly, except now with NVMes.

For example, I need to to some recovery for my home server via RDP, when I was at work or on the way through germany visiting clients. And also for computer noobs in most cases it is better not using a boot device. It's better for their usability, to take the backup via Windows Explorer or Arcronis program with listed backups. In most cases I use the hidden extra partition with backup for them, and this is also more usable for them starting this directly from Windows and not a separate boot device.

> This is risky... I would not do this as it modifies the system bootloader and if it fails to boot, could render the system unbootable.  To avoid unnecessary

> modification of your system bootloader, you should use your offline recovery media when doing a full system restore. This will work.

> If you choose not to though, this is up to you.

C'on, whole computer business and working with all that kind of stuff is risky. ;) I'm working with Acronis since 2007, and I made a lot of recovery starting from Windows (XP,7,8,8.1) and I had never any trouble with booting into another os. For example testing some new drivers, some beta programs, shareware and other changes I always make an backup before (in Windows) and do recovery (from Windows), which was working over the years everytime without any trouble. That's why I'm buying this software. Meanwhile there are a lot of cheaper even free backup programms like Aomei, Macrium etc which do the backup better and easier than Arcronis, but most of them cannot recover from windows directly (with booting into another os, of course ;) ). But this was a feature staying to Acronis, obviously the programm gets worse over the years. :(

> Have you attempted to load from rescue media yet to see if you can even get that to work on your device?

Yes, and I told this is working now since build 6569, 6559.