Share via

[SOLVED] Preparing Windows Recovery Environment: REAGENTC.EXE: Operation failed: 70 After Disabling WinRE with ReagentC /Disable

Question

Monday, December 28, 2015 4:01 PM

Howdy,

I cannot re-enable my WinRE configuration after I disabled WinRE.

PS D:\> xcopy.exe /H W:\Windows\System32\Recovery\winre.wim 'T:\Recovery\WindowsRE\'
W:\Windows\System32\Recovery\winre.wim
1 File(s) copied
PS D:\> ReAgentc.exe /setreimage /path T:\Recovery\WindowsRE\ /target W:\Windows
REAGENTC.EXE: Windows RE is already enabled.


PS D:\> ReAgentc.exe /setreimage /path T:\Recovery\WindowsRE\ /target C:\Windows
REAGENTC.EXE: Windows RE is already enabled.

PS D:\> ReAgentc.exe /info /target C:\Windows
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk5\partition1\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: e2b06021-6f56-11e4-82ee-abb7ebf625e8
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.

PS R:\Recovery\WindowsRE> ReAgentc.exe /disable
REAGENTC.EXE: Operation Successful.

PS R:\Recovery\WindowsRE> ReAgentc.exe /setreimage /path T:\Recovery\WindowsRE\ /target C:\Windows
Directory set to: \\?\GLOBALROOT\device\harddisk6\partition1\Recovery\WindowsRE

REAGENTC.EXE: Operation Successful.

PS R:\Recovery\WindowsRE> ReAgentc.exe /setreimage /path T:\Recovery\WindowsRE\ /target W:\Windows
Directory set to: \\?\GLOBALROOT\device\harddisk6\partition1\Recovery\WindowsRE

REAGENTC.EXE: Operation Successful.

PS R:\Recovery\WindowsRE> ReAgentc.exe /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Disabled
    Windows RE location:
    Boot Configuration Data (BCD) identifier: 00000000-0000-0000-0000-000000000000
    Recovery image location:   \\?\GLOBALROOT\device\harddisk6\partition5\Recovery\WindowsRE
    Recovery image index:      1
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.

PS R:\Recovery\WindowsRE> ReAgentc.exe /enable
REAGENTC.EXE: Operation failed: 70

REAGENTC.EXE: An error has occurred.

As you see, the WinreBCD and WinreLocation tags refer to blank GUIDs when they should refer to proper GUIDs (like the PBRImageLocation that refers to the install.wim for re-installing Windows)

Any clues how to re-enable it and fix GUIDs?

Thank you in advance.

Well this is the world we live in And these are the hands we're given...

All replies (14)

Tuesday, December 29, 2015 3:53 PM âś…Answered | 2 votes

Figured!

This is nightmare! MSFT you have to fix this.

The reason is: the recommended Recovery partition size of 300 Mbytes is too small. The remaining 1 Mbyte left after placing WinRE.wim is too small and ReAgentC just is unable to add some data.

I haven't traced the file system I/O, but I believe what ReAgentC does on WinRE partition is:

1. Looks for WinRE.wim.

2. Copies Boot Configuration Database (BCD) files from the target Windows installation folder to the WinRE partition.

This 2nd step seems to be the culprit. Still requires checking.

The story is below.

Here's how I've figured it:

PS C:\Windows\system32> reagentc /setreimage /path T:\Recovery\WindowsRE\ /target W:\Windows
Directory set to: \\?\GLOBALROOT\device\harddisk6\partition1\Recovery\WindowsRE

PS C:\Windows\system32> reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Disabled
    Windows RE location:
    Boot Configuration Data (BCD) identifier: 00000000-0000-0000-0000-000000000000
    Recovery image location:   \\?\GLOBALROOT\device\harddisk6\partition5\Recovery\WindowsRE
    Recovery image index:      1
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.

PS C:\Windows\system32> reagentc /enable
REAGENTC.EXE: Operation failed: 70

REAGENTC.EXE: An error has occurred.

Then I created a dummy 0 byte winre.wim on the first partition (with letter T in my case) and repeated the operation:

PS C:\Windows\system32> reagentc /enable
REAGENTC.EXE: Operation Successful.

After this, the 0 byte Winre.wim disappeared from the partition. Still, ReAgentC started to show it registered the WIM:

PS C:\Windows\system32> reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk6\partition1\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: e2b0602f-6f56-11e4-82ee-abb7ebf625e8
    Recovery image location:   \\?\GLOBALROOT\device\harddisk6\partition5\Recovery\WindowsRE
    Recovery image index:      1
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.

Well this is the world we live in And these are the hands we're given...

Monday, December 28, 2015 4:21 PM

I have tried running:

T:\>bcdedit /enum osloader

And I've noticed WinRE is listed multiple times:

Windows Boot Loader

identifier              {e2b0600e-6f56-11e4-82ee-abb7ebf625e8}
device                  ramdisk=[\windows\system32\winload.efi]\Recovery\WindowsRE\Winre.wim,{e2b0600f-6f56-11e4-82ee-abb7ebf625e8}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-US
inherit                 {bootloadersettings}
displaymessage          Recovery
displaymessageoverride  Recovery
osdevice                ramdisk=[\windows]\Recovery\WindowsRE\Winre.wim,{e2b0600f-6f56-11e4-82ee-abb7ebf625e8}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes

Windows Boot Loader

identifier              {e2b06017-6f56-11e4-82ee-abb7ebf625e8}
device                  ramdisk=[\Device\HarddiskVolume3]\Recovery\WindowsRE\Winre.wim,{e2b06018-6f56-11e4-82ee-abb7ebf625e8}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-US
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[\Device\HarddiskVolume3]\Recovery\WindowsRE\Winre.wim,{e2b06018-6f56-11e4-82ee-abb7ebf625e8}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes

Windows Boot Loader

identifier              {e2b06026-6f56-11e4-82ee-abb7ebf625e8}
device                  ramdisk=[\windows\system32\winload.efi]\Recovery\WindowsRE\Winre.wim,{e2b06027-6f56-11e4-82ee-abb7ebf625e8}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-US
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[\windows]\Recovery\WindowsRE\Winre.wim,{e2b06027-6f56-11e4-82ee-abb7ebf625e8}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes

Windows Boot Loader

identifier              {e2b0602a-6f56-11e4-82ee-abb7ebf625e8}
device                  ramdisk=[\windows\system32\winload.efi]\Recovery\WindowsRE\Winre.wim,{e2b0602b-6f56-11e4-82ee-abb7ebf625e8}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-US
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[\windows]\Recovery\WindowsRE\Winre.wim,{e2b0602b-6f56-11e4-82ee-abb7ebf625e8}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes

Possibly I could somehow clean this clutter?

Well this is the world we live in And these are the hands we're given...

Tuesday, December 29, 2015 7:06 AM

Hi Exotic Hadron,

Please try to point to the BCD GUID to have a test.

"Reagentc /enable /osguid {e2b0600f-6f56-11e4-82ee-abb7ebf625e8}".

REAgentC Command-Line Options

https://technet.microsoft.com/en-us/library/hh825204.aspx?f=255&MSPPError=-2147217396

Best regards

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

Tuesday, December 29, 2015 10:32 AM | 1 vote

Please try to point to the BCD GUID to have a test.

"Reagentc /enable /osguid {e2b0600f-6f56-11e4-82ee-abb7ebf625e8}".

REAgentC Command-Line Options

https://technet.microsoft.com/en-us/library/hh825204.aspx?f=255&MSPPError=-2147217396

Do I have to specify the OS GUID, or should it be the WinRE GUID?

I removed excess WinRE records from the BCD and left the only one:

Windows Boot Loader

identifier              {e2b0602a-6f56-11e4-82ee-abb7ebf625e8}
device                  ramdisk=[\windows\system32\winload.efi]\Recovery\WindowsRE\Winre.wim,{e2b0602b-6f56-11e4-82ee-abb7ebf625e8}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-US
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[\windows]\Recovery\WindowsRE\Winre.wim,{e2b0602b-6f56-11e4-82ee-abb7ebf625e8}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes

Now when I specify the GUID after the comma following WinRE.wim, I get the following error 32:

C:\Windows\system32>Reagentc /enable /osguid {e2b0602b-6f56-11e4-82ee-abb7ebf625e8}
REAGENTC.EXE: Operation failed: 32

REAGENTC.EXE: An error has occurred.

Well this is the world we live in And these are the hands we're given...

Tuesday, December 29, 2015 10:59 AM

Now after I cleaned off all the WinRE records but one, attempting to enable WinRE returns the following:

C:\Windows\system32>Reagentc /enable
REAGENTC.EXE: The Windows RE image was not found.

Could you please help properly configure the ReAgent.xml file:

<?xml version='1.0' encoding='utf-8'?>

<WindowsRE version="2.0">
  <WinreBCD id="{00000000-0000-0000-0000-000000000000}"/>
  <WinreLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}"/>
  <ImageLocation path="\Recovery\WindowsRE\" id="0" offset="1048576" guid="{c1af44d4-5e74-4641-9f05-8ad552f39953}"/>
  <PBRImageLocation path="\Recovery\WindowsRE\" id="0" offset="155817345024" guid="{c1af44d4-5e74-4641-9f05-8ad552f39953}" index="1"/>
  <PBRCustomImageLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}" index="0"/>
  <InstallState state="0"/>
  <OsInstallAvailable state="1"/>
  <CustomImageAvailable state="0"/>
  <IsAutoRepairOn state="1"/>
  <WinREStaged state="1"/>
  <OperationParam path=""/>
  <OsBuildVersion path="10240.16384.amd64fre.th4.150709-1700"/>
  <OemTool state="0"/>
  <IsServer state="0"/>
  <DownlevelWinreLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}"/>
  <IsWimBoot state="0"/>
  <ScheduledOperation state="4"/>
</WindowsRE>

Based on my BCD configuration (bcdedit /enum /v), what GUID must be placed instead of {00000000-0000-0000-0000-000000000000} to WinreBCD and WinreLocation parameters?

Here are the BCD records:

Windows Boot Manager

identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device                  partition=\Device\HarddiskVolume4
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  en-US
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
flightsigning           Yes
default                 {e2b06012-6f56-11e4-82ee-abb7ebf625e8}
resumeobject            {e2b06028-6f56-11e4-82ee-abb7ebf625e8}
displayorder            {e2b06029-6f56-11e4-82ee-abb7ebf625e8}
                        {e2b06012-6f56-11e4-82ee-abb7ebf625e8}
                        {e2b06013-6f56-11e4-82ee-abb7ebf625e8}
                        {e2b0602c-6f56-11e4-82ee-abb7ebf625e8}
toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout                 30

Windows Boot Loader

identifier              {e2b06029-6f56-11e4-82ee-abb7ebf625e8}
device                  vhd=[D:]\win10protpbak.vhdx,locate=custom:12000002
path                    \Windows\system32\winload.efi
description             Windows 10
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence        {e2b0602a-6f56-11e4-82ee-abb7ebf625e8}
recoveryenabled         Yes
isolatedcontext         Yes
flightsigning           Yes
allowedinmemorysettings 0x15000075
osdevice                vhd=[D:]\win10protpbak.vhdx,locate=custom:22000002
systemroot              \Windows
resumeobject            {e2b06028-6f56-11e4-82ee-abb7ebf625e8}
nx                      OptIn
bootmenupolicy          Standard
hypervisorlaunchtype    Off

Windows Boot Loader

identifier              {e2b06012-6f56-11e4-82ee-abb7ebf625e8}
device                  vhd=[D:]\win10TPENT3.vhdx,locate=custom:12000002
path                    \Windows\system32\winload.efi
description             Windows 10 Pro Technical Preview
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
integrityservices       Enable
recoveryenabled         No
isolatedcontext         Yes
flightsigning           Yes
allowedinmemorysettings 0x15000075
osdevice                vhd=[D:]\win10TPENT3.vhdx,locate=custom:22000002
systemroot              \Windows
resumeobject            {e2b06011-6f56-11e4-82ee-abb7ebf625e8}
nx                      OptIn
bootmenupolicy          Standard
hypervisorlaunchtype    Auto

Windows Boot Loader

identifier              {e2b06013-6f56-11e4-82ee-abb7ebf625e8}
device                  vhd=[D:]\win10tpent1.vhdx,locate=custom:12000002
path                    \Windows\system32\winload.efi
description             Backup
locale                  en-us
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
integrityservices       Enable
isolatedcontext         Yes
flightsigning           Yes
allowedinmemorysettings 0x15000075
osdevice                vhd=[D:]\win10tpent1.vhdx,locate=custom:22000002
systemroot              \Windows
resumeobject            {e2b06011-6f56-11e4-82ee-abb7ebf625e8}
nx                      OptIn
bootmenupolicy          Standard
hypervisorlaunchtype    Auto
detecthal               Yes

Windows Boot Loader

identifier              {e2b0602c-6f56-11e4-82ee-abb7ebf625e8}
device                  vhd=[D:]\recovery.vhdx,locate=custom:12000002
path                    \Windows\system32\winload.efi
description             Windows 10 Recovery
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence        {e2b06021-6f56-11e4-82ee-abb7ebf625e8}
integrityservices       Enable
recoveryenabled         Yes
isolatedcontext         Yes
flightsigning           Yes
allowedinmemorysettings 0x15000075
osdevice                vhd=[D:]\recovery.vhdx,locate=custom:22000002
systemroot              \Windows
resumeobject            {e2b06011-6f56-11e4-82ee-abb7ebf625e8}
nx                      OptIn
bootmenupolicy          Standard
hypervisorlaunchtype    Auto

Thank you.

Well this is the world we live in And these are the hands we're given...

Tuesday, December 29, 2015 2:15 PM

I have cleaned all the remnants of WinRE records in BCD.

Could somebody please help me understand how to register the WinRE again?

If I do:

C:\Windows\system32>ReAgentc.exe /setreimage /path T:\Recovery\WindowsRE\ /target W:\Windows
Directory set to: \\?\GLOBALROOT\device\harddisk6\partition1\Recovery\WindowsRE

REAGENTC.EXE: Operation Successful.

Nothing happens in effect.

C:\Windows\system32>ReAgentc.exe /info /target W:\Windows
Windows Recovery Environment (Windows RE) and system reset configuration
Information:


    Windows RE status:         Disabled
    Windows RE location:
    Boot Configuration Data (BCD) identifier: e2b06021-6f56-11e4-82ee-abb7ebf625e8
    Recovery image location:   \\?\GLOBALROOT\device\harddisk6\partition5\Recovery\WindowsRE
    Recovery image index:      1
    Custom image location:
    Custom image index:        0


REAGENTC.EXE: Operation Successful.

C:\Windows\system32>ReAgentc.exe /enable
REAGENTC.EXE: Operation failed: 70

REAGENTC.EXE: An error has occurred.

If I specify the GUID, the ReagentC tool obviously tells that data store is not configured. Quite understood provided that I cleaned all the remnants of WinRE records off the BCD.

C:\Windows\system32>ReAgentc.exe /enable /osguid {e2b06021-6f56-11e4-82ee-abb7ebf625e8}
The Boot Configuration Data store has not been configured. Run bcdboot.exe first and try again.

Any clues how to recreate the BCD entry?

bcdedit /copy {current}

doesn't work, because bcdedit does not allow changing device parameter to values like ramdisk=[\windows\system32\winload.efi]\Recovery\WindowsRE\Winre.wim,{e2b0602b...

Any chance ReagentC could recreate boot entries?

Well this is the world we live in And these are the hands we're given...

Tuesday, December 29, 2015 2:36 PM

If I clean the ReAgent.xml in %systemroot%\System32\Recovery, the tool recreates the config file but it does NOT fill it proper GUIDs and does NOT recreate the entries in the BCD!

Here's what it does:

C:\Windows\system32>ReAgentc.exe /setreimage /path T:\Recovery\WindowsRE\ /target W:\Windows
Directory set to: \\?\GLOBALROOT\device\harddisk6\partition1\Recovery\WindowsRE

REAGENTC.EXE: Operation Successful.


C:\Windows\system32>ReAgentc.exe /setreimage /path T:\Recovery\WindowsRE\ /target W:\Windows
Directory set to: \\?\GLOBALROOT\device\harddisk6\partition1\Recovery\WindowsRE

REAGENTC.EXE: Operation Successful.


C:\Windows\system32>ReAgentc.exe /info /target W:\Windows
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Disabled
    Windows RE location:
    Boot Configuration Data (BCD) identifier: 00000000-0000-0000-0000-000000000000
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.

How do I make ReagentC to recreate entries in BCD and fill in proper GUIDs in its ReAgent.xml?

Do I have to reinstall Windows?

Well this is the world we live in And these are the hands we're given...

Tuesday, December 29, 2015 2:51 PM

I have a Windows installation record:

Windows Boot Loader

identifier              {e2b0602c-6f56-11e4-82ee-abb7ebf625e8}
device                  partition=W:
path                    \Windows\system32\winload.efi
description             Windows 10 Recovery
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {e2b06021-6f56-11e4-82ee-abb7ebf625e8}
integrityservices       Enable
recoveryenabled         Yes
isolatedcontext         Yes
flightsigning           Yes
allowedinmemorysettings 0x15000075
osdevice                partition=W:
systemroot              \Windows
resumeobject            {e2b06011-6f56-11e4-82ee-abb7ebf625e8}
nx                      OptIn
bootmenupolicy          Standard
hypervisorlaunchtype    Auto

But I do not have the WinRE installation record since I have removed every record referencing WinRE, so there's no {e2b06011-6f56-11e4-82ee-abb7ebf625e8} object in BCD to resume.

How do I recreate the object in the BCD?

Well this is the world we live in And these are the hands we're given...

Monday, January 30, 2017 4:44 PM

Hello. I have the same question.

"Do I have to specify the OS GUID, or should it be the WinRE GUID?"

Such as:

  • REAGENTC.EXE /enable /osguid {the windows or recovery GUID?}

and

  • reagentc /setreimage /path c(windows partition):\WINDOWS\System32\Recovery\winre.wim /

or

  • reagentc /setreimage /path e(recovery partition):\recovery\windowsre\winre.wim /

and

  • reagentc /setosimage /path c:\WINDOWS\System32\Recovery\winre.wim /

or

  • reagentc /setosimage /path e(recovery partition):\recovery\windowsre\winre.wim /

?

Tuesday, January 31, 2017 3:33 PM | 1 vote

Hi, if I recall correctly this should be the OS guid, see here.

Also check that the record doesn't exist already:

bcdedit /enum osloader

Well this is the world we live in And these are the hands we're given...

Tuesday, January 31, 2017 5:07 PM | 1 vote

By the way, if you want to show the created WinRE entry in the Boot Manager menu, do the following:

1) List the created OS loader entry:

C:\WINDOWS\system32>bcdedit /enum osloader

Windows Boot Loader

identifier              {6a13a88a-3200-11e4-87ce-dc78f8a51f73}
device                  ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{6a13a88b-3200-11e4-87ce-dc78f8a51f73}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-US
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{6a13a88b-3200-11e4-87ce-dc78f8a51f73}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes

Windows Boot Loader

identifier              {6a13a88f-3200-11e4-87ce-dc78f8a51f73}
device                  ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{6a13a890-3200-11e4-87ce-dc78f8a51f73}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-US
inherit                 {bootloadersettings}
displaymessage          Recovery
displaymessageoverride  Recovery
osdevice                ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{6a13a890-3200-11e4-87ce-dc78f8a51f73}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes

Windows Boot Loader

identifier              {current}
device                  partition=C:
path                    \WINDOWS\system32\winload.efi
description             Windows 10
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {6a13a896-3200-11e4-87ce-dc78f8a51f73}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {6a13a892-3200-11e4-87ce-dc78f8a51f73}
nx                      OptIn
bootmenupolicy          Standard
hypervisorlaunchtype    Auto

Windows Boot Loader

identifier              {6a13a896-3200-11e4-87ce-dc78f8a51f73}
device                  ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{6a13a897-3200-11e4-87ce-dc78f8a51f73}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-US
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{6a13a897-3200-11e4-87ce-dc78f8a51f73}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes

In this example you can see three OS loader entries that link to the WinRE.wim image. First is located on a separate partition (first partition) and is left from Windows 7, the second looks for the WinRE.wim in the current .\Windows installation, and the last one looks at the last partition on the hard drive. The first one is a leftoever from Windows 7, so it contains an old recovery image. The second one, in C:\Windows\ was created during the installation of Windows 10, and was created by using reagentc. I was upgrading from Windows 7 to Windows 10, and Windows 10 setup did NOT expand the 300 Mbyte recovery partition so that it could allocate the new WinRE.wim. Instead, Windows 10 setup created an osloader entry that links to the WinRE.wim in Windows folder.

After that, I've created a separate WinRE.wim image using reagentc and put that new winre.wim to the 5th partition on the disk.

2) Memorize the identifiers of the two WinRE entries.

In this example these are:

{6a13a88a-3200-11e4-87ce-dc78f8a51f73} - obsolete one from Windows 7; we won't need it.
{6a13a88f-3200-11e4-87ce-dc78f8a51f73} - contains Windows 10 code, created using reagentc
{6a13a896-3200-11e4-87ce-dc78f8a51f73} - same as the previous, only created by Windows 10 setup.

Finally, I want to only these two entries to show up in the boot menu after my laptop starts:

{6a13a896-3200-11e4-87ce-dc78f8a51f73}
{6a13a88f-3200-11e4-87ce-dc78f8a51f73}

3) Here's how you can add the GUIDs to the boot menu:

bcdedit /displayorder {6a13a896-3200-11e4-87ce-dc78f8a51f73} /addlast
bcdedit /displayorder {6a13a88f-3200-11e4-87ce-dc78f8a51f73} /addlast

Well this is the world we live in And these are the hands we're given...

Wednesday, February 8, 2017 10:00 AM

I am also getting a "operation failed: 32" error. What is a 32 error? I asked MS chat support, and they could not help me.
Does anyone know what this is?
How do we fix it?

Thursday, February 9, 2017 11:17 PM

Error 32 is:**

ERROR_SHARING_VIOLATION**

32 (0x20)

The process cannot access the file because it is being used by another process.

Sunday, March 25, 2018 9:04 AM | 1 vote

Actually, I'm afraid that creating 0 sized winre.wim just fooled recovery disk creation wizard to start.

So I think that it's better to actually restore proper winre.wim rather than fake it before creating recovery disk.

And I found a solution on the net (the way to recover winre.wim that I couldn't find anywhere on my disks and backups) What worked for me on win10pro was described here: https://www.winhelp.us/restore-windows-re.html#restore