Acronis UEFI double OS's problem
Hello,
I have installed two WIN10 systems on 2 SSD. True Image is installed at one of them and used to do images of both of them. After recovery of 2nd system UEFI boot loeader stopped to recognize that OS. I tried to use all found in web "solutions" - no effect. Acronis support chat - no effect (they suggested to do recovery using pendrive). I had to install OS again from scratch. Question is - what colud I do not to have that problem in the future or how to make UEFI loader see second system afer recovery (main WIN10 with true image on it recovers very well)? Will separate copy of true imaga on each OS do the job?


- Log in to post comments

Steve, thank you very much for your respond.
I'm using UEFI boot device selection, EFI partiotion on first SSD with WIN10 and ATI. Second SSD has only one partition with another WIN10 system. Screenshot made being logged on the second system. I hope, that configuration lets avoid phisical disconection of drive (which would be extremely uncomfortable). What workflow would you recommend in that config?
- Log in to post comments

Tomasz, I would make several suggestions:
First, make an 'Entire PC' backup that includes both SSD's and therefore keeps them fully in sync with each other. The two SSD's only add up to 1TB in size and I would suspect that they are not running out of free space on the drives.
Next, see Microsoft webpage: BCDEdit Command-Line Options - which you can use to capture a copy of the UEFI Firmware configuration data that is used when you select the boot drive.
bcdedit /enum firmware
The above command (from an Administrator command prompt) will show you the information you are using currently.
If I run this on my own PC (single boot with external USB 3 boot HDD connected), it shows:
Microsoft Windows [Version 10.0.19043.1202] (c) Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>bcdedit /enum firmware Firmware Boot Manager --------------------- identifier {fwbootmgr} displayorder {bootmgr} {2bf3db2c-93c8-11eb-add5-806e6f6e6963} {5c102391-93db-11eb-add6-806e6f6e6963} timeout 0 Windows Boot Manager -------------------- identifier {bootmgr} device partition=\Device\HarddiskVolume5 path \EFI\Microsoft\Boot\bootmgfw.efi description Windows Boot Manager locale en-GB inherit {globalsettings} default {current} resumeobject {664861e7-bc11-11eb-ade6-a86daa71efa2} displayorder {current} {bfb80beb-a2b4-11ea-ad10-a2228913a61a} {664861ed-bc11-11eb-ade6-a86daa71efa2} {d511766c-f2b7-11eb-ae06-a86daa71efa2} toolsdisplayorder {memdiag} timeout 10 Firmware Application (101fffff) ------------------------------- identifier {2bf3db2c-93c8-11eb-add5-806e6f6e6963} device partition=\Device\HarddiskVolume5 description Solid State Disk custom:250000c2 1 Firmware Application (101fffff) ------------------------------- identifier {5c102391-93db-11eb-add6-806e6f6e6963} device partition=H: description USB Drive (UEFI) - USB 3.0 0508 custom:250000c2 1 C:\WINDOWS\system32>
The webpage above shows other commands that can be used to export and import these settings if needed.
See also webpage: BCD System Store Settings for UEFI
- Log in to post comments