Acronis True Image 2018 Build 10640
Windows 10 (64) with latest updates.
Acronis True Image 2018 Build 10410 installed.
After I update to Build 10640, when I reboot my computer, Windows 10 will not start. I have to restore a previous backup to get Windows to start. I have tried updating to Build 10640 several times. The results are the same. I have to restore a previous backup to start windows.

- Log in to post comments

Have you booted directly into your bios and had a look at the boot priority order? A UEFI booted machine should have Windows Boot Manager listed first in the boot priority list.
- Log in to post comments

Well lo and behold, something had rearranged the boot priority order in my UEFI BIOS, and it *wasn't* me.
My boot SSD with listed first without the Windows Boot Manager designation. There is an entry for Windows Boot Manager, but it was last in the list after my optical drive at #2.
I reordered the list to put Windows Boot Manager at the top at #1, and now the system [re]boots normally.
Note that this started with my very first reboot after updating to 10640. Thus, I had no opportunity to even enter BIOS configuration to screw up the boot order until after that first 10640 reboot had already failed.
The update to 10640 still seems like the primary suspect to me. I will run without any version of Acronis installed under Windows for several days to assess stability.
In case it's relevant, my mobo is an ASUS X99 Deluxe II, and I'm running Windows 10 64-bit Fall Creators Edition build 1709.
- Log in to post comments

Mark, when was the last time your OS updated with Microsoft? I'm not saying Acronis is or isn't the cause for the boot order difference, but I find it odd if it was simply from upgrading to a new version of Acronis.
However, any time a hard drive is recovered and/or when Windows 10 does a major "update" that basically re-installs Windows 10 as part of the process, the hard drive receives a new UUID (hardware id for the bios). This change to the UUID may cause the bios to reorder the boot priority like you experienced, as a result. If you use bitlocker or another encyrption sofware and make a partition change of any kind (shrink or expand any partitions), this will also change the disk UUID and may cause issues with a bios ability to detect the hard drive as the same one that it identified with as the booting OS previously.
Thanks for sharing that the boot order was indeed the issue as it is something that we can point others who may have a similar experience.
- Log in to post comments

I updated Windows 10 to the Fall Creators Edition about a week before the Acronis 2018 update to 10640. Since Fall Creators was a fairly time-consuming major update, I did do an offline Acronis linux rescue clone to back up the updated boot disk. I was able to boot back into Windows after that without any problems, so presumably my boot priority order was still OK at that point.
There would have been additional minor Windows Updates in the days after that, as is the case since Windows 10 updates more or less constantly. I can't recall whether any of those triggered an intentional reboot. If they did, there was no trouble.
I'm not using BitLocker on that desktop machine nor have I changed any partition sizes.
I definitely would have remembered Windows trouble on my primary desktop after Fall Creators since my initial attempt at installing it on my laptop back in October resulted in a bricked unbootable machine until I cloned it back to a pre-Fall backup. The laptop is also now successfully running Fall Creators (but has never had the Acronis .exe installed onto it).
- Log in to post comments

Some implementations of the UEFI bios can be finicky at times. I have 2 of them that gave me fits for a long time. After a good number of updates by the manufacturer and my persistence in learning how, when and why things went wrong with it, finally I can use the machines confident that when Windows upgrades or I restore a backup etc. I can get the bios to work like it is suppose to and boot the machine. I do have less trouble now with boot order than I did several bios updates ago so I would encourage you to check the manufacturer support site and see if your bios is up to date. If not, I would strongly recommend updating following the recommended procedures for doing so.
- Log in to post comments

I'm one release behind on my BIOS. The latest release only came out a month ago, and I prefer to let it have more exposure before I flash to it.
Boot priority order is easily manageable now that I know it's a thing that can go wrong ;-).
- Log in to post comments

A very reasonable position.
- Log in to post comments