How To Fix Windows Recovery Environment

Windows Recovery Surround (WinRE) is the minimal Bone based on Windows Preinstallation Environment (WinPE) which includes a number of tools to repair, reset and diagnose Windows. If the main host OS doesn't boot for any reason, the estimator tries to start WinRE, which may assist to resolve the issues manually or automatically. In WinRE, y'all can automatically fix the bootloader, restore the OS from an image fill-in, roll back to a system restore signal, run a control prompt, etc.

Windows RE consists of three files, which are located in a hidden Organization Reserved division:

• winre.wim – WIM image with WinPE and several additional recovery tools;
• kick.sdi – used to create a RAM deejay in retentiveness;
• ReAgent.xml — WindowsRE configuration file.

In this commodity, we'll evidence you how to boot your computer into WinRE, and how to repair the Windows 10 recovery environment if it doesn't piece of work.

Contents:

• How to Boot Windows into the Recovery Environment?
• WinRE Repair and Troubleshooting Tools
• Could non Find the Recovery Environment in Windows 10
• Repairing WinRE (Windows Recovery Environment) with ReAgentc Tool

How to Boot Windows into the Recovery Environment?

In gild to boot your calculator into the recovery environment the adjacent time you restart Windows, you lot need to press the Restart button in the Start menu while holding down the Shift key.

You tin also reboot the computer in WinRE mode from the command prompt using the new -o parameter of the shutdown control:

shutdown /f /r /o /t 0

This command cannot exist executed when connected to a computer via RDP. An error appears "The parameter is wrong (87)".

There is also another command to force the entry into the recovery environment at the side by side calculator boot:

reagentc /boottore

The computer automatically boots into the Windows Recovery Surroundings if three previous attempts to kicking Windows usually accept failed. In club to boot your reckoner into WinRE, it is enough to interrupt the normal Windows boot with the ability button three times in a row.

WinRE Repair and Troubleshooting Tools

In that location are several recovery and troubleshooting tools available in WinRE recovery surround to help you fix various Windows problems. WinRE on Windows 10 includes the post-obit tools:

• Reset this PC – allows you to reset your Windows to factory settings (personal data and files volition exist deleted);
• System Restore – allows you lot to restore the state of Windows using a previously created restore point;
• System Image Recovery – allows to restore Windows from a full epitome backup on external media;
• Automatic Repair/First-up Repair – Windows tries to automatically find and prepare possible issues (the wizard can independently repair the bootloader, BCD configuration and MBR (Main Kicking Record);
• Windows Startup Settings – allows you lot to select various Windows boot scenarios: Safe Mode, disable driver digital signature enforcement, disable automated restart on organization failure (this is the only manner to see the BSOD error code on the Windows boot screen),etc.;
• Uninstall Updates – allows to remove the recently installed updates (useful if Windows doesn't kick after installing updates);
• Go back to the previous version – allows you to roll back to the previous Windows ten build;
• Command Prompt – run command line to manually run diagnostic and repair commands.

If you lot desire to run a command prompt or other fault fixing tool, WinRE will enquire you for the countersign of the local administrator business relationship (the countersign will be compared with the data in the local SAM database).

You should run into a command prompt window X:\Windows\System32>.

From the control line, you tin can cheque the deejay with the chkdsk tool, check and repair the Windows image using sfc.exe or DISM, run regedit.exe, bootrec.exe, startrep.exe (this tools allows you to observe and fix problems with the registry, drivers, partitions, etc.) and other commands (there are quite a few manufactures on the site where we prove how to prepare diverse Windows problems in the recovery environment or WinPE).

To close the WinRE control prompt and return to the boot mode selection, run the command:

exit

Could not Find the Recovery Surroundings in Windows 10

In some cases, the computer tin can't  boot into the Windows Recovery Surroundings. If you try to reset the Windows, or kick into recovery fashion, you may see errors similar "Could non detect the recovery surround". This ways that the partition with the WinRE or the .wim file of the recovery surround has been deleted/damaged; either ReAgent or BCD is non configured correctly.

The reasons why the WinRE environment stops booting or does non work correctly can be unlike:

• The WinRE is disabled in Windows settings;
• The Kicking Configuration Data Store (BCD) doesn't contain entries to boot in recovery style;
• The file winre.wim (WinRE surround prototype) is missing or moved;
• The WinRE configuration file ReAgent.xml is missing or contains incorrect settings.

Side by side, we will look at the main ways to restore the WinRE environment in Windows 10 (for Windows 7 and Windows 8.1, the procedure is the aforementioned).

Repairing WinRE (Windows Recovery Surroundings) with ReAgentc Tool

How to Manually Enable or Disable Windows Recovery Environs in Windows 10?

Try to disable and enable WinRE on your computer by running the following commands in the elevated command prompt:
reagentc /disable
reagentc /enable

If the error "REAGENTC.EXE: Unable to update Kick Configuration Data" appears, first fix the problem with the Windows bootloader (instructions for UEFI and BIOS computers).

If you receive the fault message "REAGENT.EXE: The Windows RE image was not found", the winre.wim file or the System Recovery division has probably been deleted.

Check BCD Entries for WinRE

Make sure that the Boot Configuration Information (BCD) contains the right entries to boot the WinRE environment.

Note. If WinRE has been successfully enabled using the reagent, the right WinRE entries should automatically appear in the kicking configuration. Still, y'all'd better cheque the value of recoverysequence parameter.

Brandish the current BCD entries:

bcdedit /enum all

In the list of boot options, find the Windows Boot Loader department with identifier={current}. In our example, this entry looks similar this:

Windows Boot Loader ------------------- identifier              {current} device                  partition=C: path                    \Windows\system32\winload.exe description             Windows 10 locale                  en-The states inherit                 {bootloadersettings} recoverysequence        {7c817935-e52f-11e6-9c2c-0050569efccb} recoveryenabled         Yes allowedinmemorysettings 0x15000075 osdevice                partition=C: systemroot              \Windows resumeobject            {1c7df7a0-4560-11e5-9675-8451eaa913bb} nx                      OptIn bootmenupolicy          Standard

Detect and think the GUID value of recoverysequence aspect. In our case, it is {7c817935-e52f-11e6-9c2c-0050569efccb}.

And then yous need to notice the kicking configuration department having the identifier value equal to the GUID value obtained earlier and having Windows Recovery Surround in the description field. This entry can look similar this:

Windows Boot Loader ------------------- identifier              {7c817935-e52f-11e6-9c2c-0050569efccb} device                  ramdisk=[F:]\Recovery\WindowsRE\Winre.wim,{7c817936-e52f-11e6-9c2c-0050569efccb} path                    \windows\system32\winload.exe description             Windows Recovery Environment locale                  en-US inherit                 {bootloadersettings} displaymessage          Recovery osdevice                ramdisk=[F:]\Recovery\WindowsRE\Winre.wim,{7c817936-e52f-11e6-9c2c-0050569efccb} systemroot              \windows nx                      OptIn bootmenupolicy          Standard winpe                   Aye

If you cannot notice this entry, wait for another BCD tape with some other GUID every bit an identifier and the text "Windows Recovery Environment" in the description field, which contains the path to Winre.wim in the device and osdevice values .

The path to WIM file can indicate to another bulldoze (for example, [\Device\HarddiskVolume2]). If such department has been found, you tin link this entry to kicking WinRE as the recovery environment for the current Os. Copy the GUID of the plant entry and supercede information technology using the control:

bcdedit /fix {electric current} recoverysequence {FoundGUID}

Note. If you are using multiboot, proceed in mind that each Os adds its own Windows Recovery Environment entry to the Microsoft Kick Managing director. It is important not to become lost in them.

The Location of the Winre.wim File

Make certain that Winre.wim is present in the specified location. Typically, it is stored in one of the following locations:

• Binder C:\Windows\System32\Recovery binder;
• Separate subconscious System Reserved sectionalization;
• Manufactory made OEM recovery partition (brand sure you didn't delete information technology).

In our example, it should be located on the F:\ drive (F:\Recovery\WindowsRE \Winre.wim).

Also cheque the path to the wim file specified in ReAgent.xml (located  in C:\Windows\System32\Recovery binder or in Recovery folder on the recovery partition). Open this file in any text editor and check the value of <ImageLocation path= attribute. If the path specified doesn't be (the original partition has been deleted), you tin modify the path to <ImageLocation path="\Recovery\WindowsRE"), create the folder C:\Recovery\WindowsRE and re-create the Winre.wim to it. Disable and enable WinRE again:

reagentc /disable
reagentc /enable

Tip. The current Recovery Agent configuration can be obtained using reagentc /info control. This command tin can will assistance to get the Boot Configuration Data (BCD) identifier and the physical path to Windows RE image file:

(location: \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE)

Reset WinRE Settings in ReAgent.xml file

If the methods described above didn't help yous to recover WinRE, y'all tin can try to reset the recovery environment settings in ReAgent.xml file(fill-in this file in advance).

On Windows ten, just delete the ReAgent.xml file and information technology volition be automatically created the next fourth dimension you enable WinRE with the command:

reagentc /enable

In Windows seven/Vista, open ReAgent.xml in a text editor (it's meliorate to use Notepad++) and clear the values of the post-obit parameters: WinreBCD, WinreLocation, ImageLocation, InstallState, WinREStaged:

<WinreBCD id="{00000000-0000-0000-0000-000000000000}"/> <WinreLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}"/> <ImageLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}"/> <InstallState state="0"/> <WinREStaged state="0"/>

Relieve the changes. Brand sure that Winre.wim is nowadays in the %windir%\System32\Recovery folder. Enable WinRE with the command:

reagentc /enable

Find and Copy the Winre.wim File Manually

If you cannot notice the Winre.wim file in any of the standard folders, try locating it using your file manager or with the following command:

dir /a /due south c:\winre.wim

Tip. Don't forget to look for this file in the subconscious partitions as well, which need to be assigned a bulldoze alphabetic character in advance.

If you take establish the file, copy information technology in to a default location using the commands:

attrib -h -s c:\Recovery\3b09be7c-2b1f-11e0-b06a-be7a471d71d6\winre.wim
xcopy /h c:\Recovery\3b09be7c-2b1f-11e0-b06a-be7a471d71d6\winre.wim c:\Windows\System32\Recovery

If yous couldn't find the file, copy it from a similar Windows case(the OS version and bitness must match), or from the install media/bootable USB wink drive. To do it, open the \sources\install.wim (or install.esd) on the DVD/ ISO image using seven-Zip and excerpt the \Windows\System32\Recovery\Winre.wim and ReAgent.xml to the c:\Windows\System32\Recovery binder.  The original kick.sdi file must exist copied from the \Windows\Boot\DVD folder.

You can replace the built-in winre.wim image with the more advanced Dart 10 recovery paradigm, which contains boosted tools useful for diagnosing and fixing Windows boot problems.

Supersede the path to the winre.wim file in the Recovery Agent configuration:

reagentc /setreimage /path C:\windows\system32\recovery

Now merely enable Windows Recovery Amanuensis with this command:

reagentc /enable

Source: http://woshub.com/restoring-windows-recovery-environment-winre-in-windows-10/

Posted by: crawfordwheabion.blogspot.com

Share this post