Skip to main content

TI 2018 F11 or recovery media do not work on 3 of my 5 PCs

Thread needs solution

TI hangs when trying to use the F11 mode (Linux) to do a backup.  It also hangs when trying to use the recovery media for both backup and recovery.  TI hangs during the initial phase after the input of the path to place the backup on an external hard drive.  This hang occurs on 3 of my 5 PCs.  The common part is that all 3 are Dells.  All 5 PCs are Windows 10.  I reported this problem last year and have had several conversations with support and all I get is that they are working on it.  It seems that it is a very low priority since I'm the only one reporting the problem.  I would caution other users to verify the recovery media works on their PC before a disaster happens and they really need it to work.

0 Users found this helpful

Bernie, sorry but more information will be needed here to better understand how to try to help you with this issue?

Please run the msinfo32 command on all of your 5 PC's and make a note for each of what is shown in the BIOS mode setting shown in the report produced by this tool.  This will be either Legacy or UEFI.

From the same report page, please note what is shown for System Type where this will normally show either x64 or x86 (based PC) which translates as being either 64-bit or 32-bit in architecture.

If your systems are UEFI, then please check in the BIOS settings whether you have Secure Boot enabled or not?

Next question here is: which version of the Acronis Rescue Media are you using when trying that method for recovery?

The F11 key invocation of the Acronis Startup Recovery Manager is using a Linux kernel OS, hence my question as to whether your Rescue Media is also the Linux version or whether you have created the Windows PE version?

Please see KB 60091: Acronis True Image 2018: how Simple bootable media creation mode works and also KB 60820: Acronis True Image 2018: how to create bootable media 

I would strongly recommend creating the Windows PE version of the Rescue media rather than relying on the Linux one.  There is far better driver support with the WinPE media, and you can also use the MVP Custom ATIPE Builder tool which can inject additional device drivers along with enabling support for such as BitLocker drives and giving you a file manager & web browser on the rescue media etc.  

  

Thanks for your reply.  I understand the F11 is Linux as is the rescue media I created to test (also failed).  I am using the Linux based rescue media from TI2017 and that works just fine (thankfully).  Because it works I don't think the problem is in the BIOS but did do a msinfo32 on this PC anyway.  

I did try the "simple" version of rescue media but it doesn't seem to support my wireless mouse and I could not figure out how to navigate the backup screen using only the keyboard.

In the past I did try the WINpe for s different problem (it didn't help) and remember that it required a LOT of disk space.  I will try it again but don't hold much hope.  I think Acronis messed up the Linux version in TI 2018 and have not fixed it.  BTW I just got and installed version 11530 and remade and tested the rescue media -- same problem.

Attachment Size
447663-146222.txt 1.62 KB

Windows base recovery media is now the default; there have been numerous reports of issues with the Linux recovery media. May I suggest you create the "Simple" windows base recovery media which use Windows RE rather than Windows PE so does not require the large downloads that you mention.

Ian

I tried the "simple" option  and it doesn't seem to recognize the wireless mouse. I could not find a way to click all the needed boxes with the keyboard.  If the Linux interface is no longer supported it seem to me that  that should be made public.

I formatted and remade the "simple" rescue USB.  It worked with a quick test so in the next few days  I will start a full backup-restore-clone creation test but this is good progress.

Good to hear that you are making some progress.

"If the Linux interface is no longer supported it seem to me that  that should be made public." It is not that it is no longer supported, it is just that there are some problems with recent builds. I agree that they should give more direction as to which recovery media is likely to be easiest to create and least likely to cause problems.

Ian

In reply to by truwrikodrorow…

I tested the Simple backup on the 3 PCs that fail the F11/Linux backup/recovery.  It worked OK on two PCs and had an annoying issue on one.  It failed to recognize my wireless mouse unless I removed and reinserted the wireless-USB dongle.  I noticed that the two that worked are Logitech mice and the failing one was a Microsoft mouse.  Replaced the MS mouse with a Logitech and it worked.  Pretty bad when software does not recognize Microsoft stuff!!

I also tried a test of the Clone feature and it fails on all three PCs.  In fact the software recommends I use the Linux based recovery media.  That really pissed me off after I had a laugh. Ironic.

So I'm back to wanting the Linux version to work!

Which computer did you make the Simple media on?  Was it one with the Logitech mouse, which it sounds most likely if it picked up the device drivers for the wireless mouse.  Have you tried using the Microsoft wireless mouse on that same system for its device drivers to be installed, then possibly also picked up when making the simple media?

I made the Simple USB on the system the that had been using the Microsoft mouse. 

It did work if I removed the dongle and reinserted it.  I tried removing other USB's and also waiting till the boot was finished before turning on the mouse but  none of that helped, just the mouse dongle worked.

 

In any case, without the clone function I'll go back to to my TI17 Linux rescue USB since I really need the clone once a month.