How to Repair or Restore the Windows Recovery Environment WINRE | Fix ReAgentC errors in Windows 10

On this video, I’m going to show you how to enable windows recovery environment and system reset in running windows, or by booting from the USB drive.
This is a brief video for professional users, however, there is another video containing many methods and comprehensive details showing everything about Windows Recovery Environment and variations in its location from this video:

How to create bootable USB in android mobile:

I will show you 4 methods to repair or to restore the WinRE environment in Windows 10, however, the procedure is the same for Windows 7 and Windows 8.1.

Method number 1:
Type CMD into Search box, then run command prompt as administrator
If you are booting from USB, open command prompt and Execute this command to identify windows partition:
BCDEDIT
Execute this command to change CMD directory to System 32 folder.
CD /D C:\WINDOWS\SYSTEM32
Execute the following command to show of windows identifier:
BCDEDIT /V /ENUM OSLOADER
Type this command without hitting Enter:
REAGENTC /ENABLE /OSGUID
Copy the identifier of windows and paste it after previous command then press Enter.
Make sure the description is containing Windows 10 or the windows version that is installed on your PC.
In running windows, you can execute Reagentc command with or without using OSGUID.

Method number 2:
DIR /S /A C:\WINRE.WIM
If the file found in another folder, copy it into recovery folder using this command:
XCOPY /H C:\RE_BACK\WINRE.WIM C:\WINDOWS\SYSTEM32\RECOVERY
Execute Reagentc Command again to enable Recovery.

Method number 3:
Type DISKPART and hit enter
Type LIST DISK and hit enter
SEL DISK 0
Execute this command to show the list of volumes:
LIST VOL
Execute this command to show the list of partitions:
LIST PART
Recovery partition usually labelled with Recovery name and its size around 500 megabytes with NTFS file system, but not FAT32 file system.
In a custom manufacturer recovery with additional apps or tools, the size of partition may extended into many gigabytes.
If the recovery volume doesn’t have a letter, give it V letter using the following 2 commands:
SEL VOL 2
ASSIGN LETTER=V
Execute EXIT command to close DISKPART
Show contents of the V partition using this command:
DIR /S /A V:
XCOPY /H V:\RECOVERY\WindowsRE\WINRE.WIM C:\WINDOWS\SYSTEM32\RECOVERY
ATTRIB -S -H -R V:\RECOVERY\WINDOWSRE\*.*
Delete all files in WindowsRE folder using this command:
del V:\RECOVERY\WINDOWSRE\*.*
In running windows, you may need to set the recovery path using this command:
REAGENTC /SETREIMAGE /PATH C:\WINDOWS\SYSTEM32\RECOVERY
REN C:\WINDOWS\SYSTEM32\RECOVERY\REAGENT.XML REAGENT.OLD
Enable recovery Environment using ReagentC command as on method number 1.
If the reagentc failed with this error message, “The boot configuration data has not been configured” or “REAGENTC.EXE: Unable to update Boot Configuration Data”, you can fix that as followings:
execute the following command to rebuild BCD,
BCDBOOT C:\WINOWS

Method number 4: How to enable Recovery if the required files are missing?
If the WinRE.wim file is not available in windows or recovery partition, you have to copy it from ISO file of windows installation with the same or newer build number then installed windows.
In running windows,
Double click the ISO file to mount it and memorize its letter.
When booting from a USB, open Notepad:
Click on file tab then select Open option
Click on this PC icon to show all partitions
Determine the letter of the USB drive
In my system, the D partition is assigned to USB partition.

MD C:\MOUNT
DISM /MOUNT-IMAGE /IMAGEFILE:D:\SOURCES\INSTALL.WIM /INDEX:1 /MOUNTDIR:C:\MOUNT /READONLY
Copy the WinRE.wim:
XCOPY /H C:\MOUNT\WINDOWS\SYSTEM32\RECOVERY\WINRE.WIM C:\WINDOWS\SYSTEM32\RECOVERY
I have already created a bootable recovery image for windows 10 X64 version 19041.

XCOPY /H E:\SOURCES\BOOT.WIM C:\WINDOWS\SYSTEM32\RECOVERY
Replace the E with the letter of the USB drive or the mounted ISO file in your computer.
REN C:\WINDOWS\SYSTEM32\RECOVERY\BOOT.WIM WINRE.WIM
Finally execute the Reagentc command again to enable Recovery.

how to fix windows recovery environment
how to repair or restore the windows recovery environment
windows recovery environment windows 10 not working
windows recovery environment how to access
how to fix could not find recovery environment windows 10
how to create recovery environment windows 10
how to fix could not find recovery environment windows 8.1

[blessing]

Best YouTuber ever I literally almost cried man. You’re a life saver

[artin]

You are insane. Best vid I stumbled on so far it worked and every part was crystal clear.

[rias_gremoryy]

Omg you are a life saver😭😭😭 method 1 worked easily without a doubt

[jay]

My case was a daisy chain of issues that started with a bad windows update and bios firmware update. I had to completely rebuild my bcd in accordance with uefi because I have GPT disks. I tried EVERYTHING, even the 3rd option (which partially worked for me) and it did not work. The steps I took:
Used a bootable usb windows media. I used cmd prompt to completely rebuild the partition tables for efi and msr as a default windows installation would do. I also copied the recovery portion within the same steps from the usb drive to the new partition (There's many tutorials for all this). After doing this, I proceeded to rebuild the boot config file. This did not fix the windows re issue after restarting, but now my partitions were normal again. Now I followed step number 3 in this video partially (the part about rebuilding BCD and setting guid) . I believe rebuilding my BCD after rebuilding my partitions in usbmedia and then setting guid was the fix for me. I now have my windows RE working again with correct partitions.

[chitranshrawat]

Bro you deserve a like
Method third work for me
Thankyou

[efis.]

You are a complete lifesaver, thank you.

[tomspeedx]

Mate
Thank you so much for that video and making it easy to follow even though there were loads of commands to type
I managed to start a factory reset finally i thought i would never make it

[Infinity_XPG]

BHAI THANKS A LOT
I WAS UNABLE TO FIND SUCH A VIDEO,
GOD LVL

[xemnasnoheart]

Thank you so much! Just running "REAGENTC /ENABLE" enabled WINRE for me.

[spieffy]

thank you so much man, i was getting ready to reset and sell my old pc, but i got a problem, used your methods, it worked ;DD thanks man, earned a sub :D

[ibingeyt]

It didn’t work for me. It showed operational successful, however, nothing changed. An option even disappeared from my advanced settings in the boot menu. EDIT; ANYONE WHO HAS THE PROBLEM ABOVE, just restart and it should be fine.

[mohamedabdinasir]

finally, thank you very much Sir, you are a life saver

[risottinoquellovero]

man you saved me, today i runned a spoofer to get unbanned from a game and i was on 20h2 and so the spoofer fucked up my pc, all windows file get corrupted so i cant log in, i tried to go in save mod but i cant, after a while i finaly logged in, i opened the cmd and tried to restore the boot files and get the following error message (Bootrec not recognized or something like that) after i discovered your channel and tried to reset my pc using your erlier video, its not worked cuz my recovery files was in another partition later i log off from my pc sad and tried and later tried to find an another solution when i discovered this video, thanks man, you saved my like 10 hours to find a working solution

[nicobby]

Thx so much, third method worked for me, you're a lifesaver

[zynical]

Thanks so much!
The first method worked for me

[TienNguyen-llnc]

I am running "REAGENTC /ENABLE". But i got the error: "REAGENTC.EXE: Operation failed: 3"
How can I solved the error??

[sangeetayadav]

He is super fast.
I an enable to get some of the commands that's why I have to watch this video many times

[santoshgavhane]

BEST EVER, 4 TH METHOD WORKS FOR ME THANKS

[Aljjocol]

In my case reagentC was enabled, recovery partition was created as intended, so I went to try the winre (win+x and restart) and during pc boot it would stuck at "please wait" screen. It would not enter the winRE. So I guess something is wrong with the boot path. So my solution was to disable reagentc, then delete the reagent.xml file and re run reagentc /enable so it creates the xml with the correct paths. I would recommend re checking the recovery GUID to be the same between the OS ''recovery sequence" and in the identifier in the "windows recovery environment" using the bcdedit /enum all command

[smeckjee]

It worked tnx mate. Only needed to watch until 1:38 for me to fix it!