How to add the Recovery partition in a System Backup too?

[pstein]

After starting a System  Backup Hasleo Backup Suite presents me all found partitions.

The Windows 10 partition and the ESP partition are pre-selected (=shown with a checkmark in checkbox).
Unfortunately the 0,49 GB Recovery partition is NOT pre-selected.

Moreover when I tick into the corresponding checkbox it cannot be selected.

Why?

How can I perform a System Backup WITH Recovery Partition?

[admin]

For information on this issue, please refer to:
https://www.easyuefi.com/forums/thread-3...ml#pid9759

[pstein]

Thank you for your help.

See requested output info below.

Interesting: Recovery Partition seems to be disabled.
I never intentionally disabled it in the past.

Whenever I need to repair/troubleshoot my Win10 system I booted from USB flash drive with full Windows 10 installation stuff (including recovery).
So I was not aware that the Recovery WinRE on my SSD is disabled.
However I would like to embed/add it in my System Backup

How can I re-activate (and update if necessary) it?

Disk 0 is a hard disk
Disk 1 is a SSD

   

   

Run cmd.exe as a administrator
2. Run "bcdedit /enum all /v  >> C:\bcd.txt"
3. Send C:\bcd.txt to us
Firmware Boot Manager
---------------------
identifier              {a5a30fa2-3d06-4e9f-b5f4-a01df9d1fcba}
displayorder            {9dea862c-5cdd-4e70-acc1-f32b344d4795}
                        {4599f69f-76f1-11ed-bd5e-806e6f6e6963}
timeout                1

Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device                  partition=\Device\HarddiskVolume2
path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description            Windows Boot Manager
locale                  de-DE
inherit                {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default                {dbeba750-7633-11ed-9123-a160bb82bf6f}
resumeobject            {dbeba74f-7633-11ed-9123-a160bb82bf6f}
displayorder            {dbeba750-7633-11ed-9123-a160bb82bf6f}
toolsdisplayorder      {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout                30

Firmware Application (101fffff)
-------------------------------
identifier              {4599f69f-76f1-11ed-bd5e-806e6f6e6963}
device                  partition=\Device\HarddiskVolume2
path                    \EFI\OEM\BOOT\BOOTMGFW.EFI
description            Windows Boot Manager

Windows Boot Loader
-------------------
identifier              {dbeba750-7633-11ed-9123-a160bb82bf6f}
device                  partition=C:
path                    \Windows\system32\winload.efi
description            Windows 10
locale                  de-DE
inherit                {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence        {dbeba751-7633-11ed-9123-a160bb82bf6f}
displaymessageoverride  Recovery
recoveryenabled        Yes
isolatedcontext        Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {dbeba74f-7633-11ed-9123-a160bb82bf6f}
nx                      OptIn
bootmenupolicy          Standard

Windows Boot Loader
-------------------
identifier              {dbeba751-7633-11ed-9123-a160bb82bf6f}
device                  ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{dbeba752-7633-11ed-9123-a160bb82bf6f}
path                    \Windows\system32\winload.efi
description            Windows Recovery Environment
locale                  de-DE
inherit                {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
displaymessage          Recovery
osdevice                ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{dbeba752-7633-11ed-9123-a160bb82bf6f}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                  Yes
custom:46000010        Yes

Resume from Hibernate
---------------------
identifier              {dbeba74f-7633-11ed-9123-a160bb82bf6f}
device                  partition=C:
path                    \Windows\system32\winresume.efi
description            Windows Resume Application
locale                  de-DE
inherit                {1afa9c49-16ab-4a5c-901b-212802da9460}
recoverysequence        {dbeba751-7633-11ed-9123-a160bb82bf6f}
recoveryenabled        Yes
isolatedcontext        Yes
allowedinmemorysettings 0x15000075
filedevice              partition=C:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No

Windows Memory Tester
---------------------
identifier              {b2721d73-1db4-4c62-bf78-c548a880142d}
device                  partition=\Device\HarddiskVolume2
path                    \Windows\system32\winload.efi
description            Windows-Speicherdiagnose
locale                  de-DE
inherit                {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
badmemoryaccess        Yes

EMS Settings
------------
identifier              {0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
bootems                No

Debugger Settings
-----------------
identifier              {4636856e-540f-4170-a130-a84776f4c654}
debugtype              Local

RAM Defects
-----------
identifier              {5189b25c-5558-4bf2-bca4-289b11bd29e2}

Global Settings
---------------
identifier              {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
inherit                {4636856e-540f-4170-a130-a84776f4c654}
                        {0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
                        {5189b25c-5558-4bf2-bca4-289b11bd29e2}

Boot Loader Settings
--------------------
identifier              {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
inherit                {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
                        {7ff607e0-4395-11db-b0de-0800200c9a66}

Hypervisor Settings
-------------------
identifier              {7ff607e0-4395-11db-b0de-0800200c9a66}
hypervisordebugtype    Serial
hypervisordebugport    1
hypervisorbaudrate      115200

Resume Loader Settings
----------------------
identifier              {1afa9c49-16ab-4a5c-901b-212802da9460}
inherit                {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}

Device options
--------------
identifier              {dbeba752-7633-11ed-9123-a160bb82bf6f}
description            Windows Recovery
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\WindowsRE\boot.sdi

[admin]

Your BCD shows that Windows RE is actually stored on the C: drive, which is why HBS does not select the 0.49 GB Recovery partition.

Windows Boot Loader
-------------------
identifier              {dbeba751-7633-11ed-9123-a160bb82bf6f}
device                  ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{dbeba752-7633-11ed-9123-a160bb82bf6f}
path                    \Windows\system32\winload.efi
description            Windows Recovery Environment
locale                  de-DE
inherit                {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
displaymessage          Recovery
osdevice                ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{dbeba752-7633-11ed-9123-a160bb82bf6f}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                  Yes
custom:46000010        Yes

[pstein]

Interesting. Thank you
I never moved intentionally WinRe to the C:\ partition.

However the Recovery partition (=the 1 GB) exists but is empty.
Why does HBS make it selectable for System backup anyway?
If it is selected then HBS should simply backup an empty partition.

And a another question:
How can I move the Recovery WinRE stuff from S:\ partition back to its original Recovery partition?
Or re-create Recovery partition content?

[admin]

Interesting. Thank you
I never moved intentionally WinRe to the C:\ partition.

However the Recovery partition (=the 1 GB) exists but is empty.
Why does HBS make it selectable for System backup anyway?
If it is selected then HBS should simply backup an empty partition.

And a another question:
How can I move the Recovery WinRE stuff from S:\ partition back to its original Recovery partition?
Or re-create Recovery partition content?

In this case, the recovery partition is actually not selectable. You can refer to the method shared by al3x to rebuild the Recovery partition. Please see the following link for details:
https://www.easyuefi.com/forums/thread-3...ml#pid9843

[admin]

Interesting. Thank you
I never moved intentionally WinRe to the C:\ partition.

However the Recovery partition (=the 1 GB) exists but is empty.
Why does HBS make it selectable for System backup anyway?
If it is selected then HBS should simply backup an empty partition.

And a another question:
How can I move the Recovery WinRE stuff from S:\ partition back to its original Recovery partition?
Or re-create Recovery partition content?

In this case, the recovery partition is actually not selectable. You can refer to the method shared by al3x to rebuild the Recovery partition. Please see the following link for details:
https://www.easyuefi.com/forums/thread-3...ml#pid9843

[al3x]

If you follow these steps, you probably won't need step 5.
That was only needed in that special case where there were 2 different recovery partitions right next to each other.

And step 6 had a small error, I described the fix here:
https://www.easyuefi.com/forums/thread-3...ml#pid9846

Since reagentc is already disabled for you, you could also try step 15 first to see if enabling reagentc is working for you correctly.
There's a good chance that reenabling isn't working for your setup because the file Winre.wim was deleted beforehand.

In that case you could try copying the Winre.wim file first from a working setup ISO file, see this post:
https://www.easyuefi.com/forums/thread-3...l#pid10013

[admin]

If you follow these steps, you probably won't need step 5.
That was only needed in that special case where there were 2 different recovery partitions right next to each other.

And step 6 had a small error, I described the fix here:
https://www.easyuefi.com/forums/thread-3...ml#pid9846

Since reagentc is already disabled for you, you could also try step 15 first to see if enabling reagentc is working for you correctly.
There's a good chance that reenabling isn't working for your setup because the file Winre.wim was deleted beforehand.

In that case you could try copying the Winre.wim file first from a working setup ISO file, see this post:
https://www.easyuefi.com/forums/thread-3...l#pid10013

It seems many users are encountering this issue. I have stickied the thread containing your previous replies.