Help with BCD Recovery Entry Point Error

I've been trying to enable the recovery environment but so far have been unsuccessful.


This is the previous thread that has not provided a solution: Can I Delete These 2 Recovery Partitions?
I've taken a look at the reagentc error logs and discovered the warning about an invalid recovery entry point, see below.

[ReAgentc.exe] -----Executing command line: reagentc /info-----
[ReAgentc.exe] ------------------------------------------------------
[ReAgentc.exe] Enter WinReGetConfig[ReAgentc.exe] Parameters: configWinDir: NULL
[ReAgentc.exe] WinRE config file path: C:\WINDOWS\system32\Recovery\ReAgent.xml
[ReAgentc.exe] Update enhanced config info is enabled.
[ReAgentc.exe] ReAgentConfig::ReadBcdAndUpdateEnhancedConfigInfo BCD recovery entry points to invalid location (no winre.wim at )
[ReAgentc.exe] WinRE is staged[
ReAgentc.exe] Wim dir location: \\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE[ReAgentc.exe] System is WimBoot: FALSE
[ReAgentc.exe] WinRE image validated
[ReAgentc.exe] Exit WinReGetConfig return value: 1, last error: 0x0

Using Bootice I think I see that some information is missing from the Windows Recovery device object. If someone could verify that I'm headed in the right direct and also how I can go about fixing it, I would be most appreciative.

Hey mate,

It shows that WinRE is disabled for you. You can enable it using option 2 in the tutorial below.

Enable or Disable Windows Recovery Environment in Windows 10

If needed, you can create your own recovery image to use for this.

Create Reset Recovery Image in Windows 10

Brink said:

Hey mate,

It shows that WinRE is disabled for you. You can enable it using option 2 in the tutorial below.

Enable or Disable Windows Recovery Environment in Windows 10

If needed, you can create your own recovery image to use for this.

Create Reset Recovery Image in Windows 10

Hi Shawn and thanks for your response. I’ve tried all the normal stuff to enable the recovery environment but to no avail. This thread is a follow on to my previous post Can I Delete These 2 Recovery Partitions?
i’ve made a recovery drive and have images and other tools in case of a disaster so I’m covered. I’m trying to figure out the root cause of this issue since I have two other PCs with the same problem. This definitely has my attention, I love a challenge.
Bob

Out of curiosity, does it let the created reset recovery image work for you?

Brink said:

Out of curiosity, does it let the created reset recovery image work for you?

Yes, I was able to boot from it but, I'm very curious why I was able to create the recovery drive if I'm not able to enable the recovery environment. My knowledge in this area is definitely thin so I'm feeling my way around.
I do have a Dell Inspiron lappy that's V1903 and its recovery environment is enabled and fully functional so I do have something to use as a standard. But, for the life of me I don't understand what the missing piece of the puzzle is here. I keep looking at things. On the lappy the device objects (recovery) SdiDevice is set to "C". I tried changing that on the problem PC but it didn't help. Now I'm really stumped. What could have killed the recovery environment of three desktop PCs and not done so on the lappy. Driving me crazy.

Since you Have a System Backup and you not worried..

Right click and delete the reference to (Device objects) Recovery environment
And (Application Objects) Windows Recovery environment
then try again

Code:

Reagentc /setreimage /path \\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE\ /Target C:\Windows
Reagentc /enable

Ran a backup with Bootice before the deletion.
Commands succeeded but still disabled.
I think one of the problems is that there is no winRE.wim anywhere on the C-Drive in any of the normal locations. So, since I've already extracted winre.win from my install media, I'm going to work my way through the the article at:
TeraByte Unlimited Knowledge Base
I'll make a complete image before I start so I can go back. I just might learn something today. Its only time and I'm retired.
Bob.
UPDATE: I was wondering of my decision to allow Macrium to change the Windows Boot Menu to the Windows PE10 Release 1709, v 7.2.4325 had anything to do with this problem? I remember doing this on all three of the PCs that I'm having this issue with.

Ok assign a drive letter "R" to the recovery partition
-------------
copy wimRE.wim to C:\windows/system32/recovery
---------------
attrib -h -r -s -a R:\Recovery
attrib -h -r -s -a R:\Recovery\WindowsRE

Delete sdi and xml files
-----------------------
attrib -h -r -s -a C:\Recovery
attrib -h -r -s -a C:\Recovery\WindowsRE

delete xml file
-------------------

Code:

Reagentc /setreimage /path \\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE\ /Target C:\Windows
Reagentc /enable

reboot

the problem here is that you have 3 recovery partitions and each upgrade is trying to redirect reagent to the next one

Kyhi said:

Ok assign a drive letter "R" to the recovery partition
-------------
copy wimRE.wim to C:\windows/system32/recovery
---------------
attrib -h -r -s -a R:\Recovery
attrib -h -r -s -a R:\Recovery\WindowsRE

Delete sdi and xml files
-----------------------
attrib -h -r -s -a C:\Recovery
attrib -h -r -s -a C:\Recovery\WindowsRE

delete xml file
-------------------

Code:

Reagentc /setreimage /path \\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE\ /Target C:\Windows
Reagentc /enable

reboot

was already going to do that after Macrium full image is finished. It going to take about 90 more minutes. I have a big C and D drives.