Skip to main content

Startup Recovery Manager quit working after installing build 17750

Thread needs solution
Regular Poster
Posts: 198
Comments: 120

After installing the update, (build 17750), instead of getting the message at startup to press f11 to launch the recovery manager I began getting a, "non-system disk" error. When this message first started appearing I attempted to find a solution looking at OS problems but couldn't find any.

When I  disabled the Acronis recovery manager the error went away. I cycled through a period of enabling/disabling the recovery manager. Each time I enabled it I got the, "non-system disk", error, when I disabled the recovery manager the error went away.

As I stated, this happened after installing the update. Using the older build the recovery manager worked as it was intended to work.

Any ideas what is going on?

Thanks,

Everette

0 Users found this helpful

Everette, welcome to these public User Forums.

Yours is the first report I have seen of any issues with ASRM for after the latest ATI 2019 Update #17750 is installed.

I don't use ASRM myself as it does not play nicely with a dual-boot system scenario and it also uses the older Linux OS kernel technology as the launch platform, which is much less flexible than other alternatives.

If you want to use ASRM, then I would recommend opening a Support Ticket with Acronis to report this issue after updating to 17750.

See recent forum topic: Create ATI .wim and boot from D: disk ? With BCD entry ? - which has screenshots of the method that I use instead of using ASRM.