How To Clean Install Windows 10 From A Computer Messaged Windows Build 7601 Windows Not Genuine

Windows Recovery Surround (WinRE) is the minimal OS based on Windows Preinstallation Surround (WinPE) which includes a number of tools to repair, reset and diagnose Windows. If the primary host Bone doesn't kicking for any reason, the computer tries to start WinRE, which may help to resolve the issues manually or automatically. In WinRE, you tin automatically fix the bootloader, restore the OS from an image fill-in, roll dorsum to a system restore point, run a command prompt, etc.

Windows RE consists of three files, which are located in a hidden Arrangement Reserved partition:

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

In this commodity, we'll evidence you how to kicking your calculator into WinRE, and how to repair the Windows x recovery environment if information technology doesn't work.

Contents:

• How to Kick Windows into the Recovery Environment?
• WinRE Repair and Troubleshooting Tools
• Could not Detect the Recovery Environment in Windows 10
• Repairing WinRE (Windows Recovery Environment) with ReAgentc Tool

How to Boot Windows into the Recovery Environment?

In guild to boot your computer into the recovery environment the next fourth dimension you lot restart Windows, y'all demand to press the Restart button in the Start menu while belongings downward the Shift key.

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

shutdown /f /r /o /t 0

This command cannot be executed when continued to a computer via RDP. An error appears "The parameter is incorrect (87)".

There is also another control to strength the entry into the recovery environment at the next computer boot:

reagentc /boottore

The estimator automatically boots into the Windows Recovery Environs if three previous attempts to boot Windows normally have failed. In club to boot your computer into WinRE, it is enough to interrupt the normal Windows kick with the power button 3 times in a row.

WinRE Repair and Troubleshooting Tools

In that location are several recovery and troubleshooting tools available in WinRE recovery environment to aid you fix diverse Windows bug. WinRE on Windows x includes the following tools:

• Reset this PC – allows y'all to reset your Windows to factory settings (personal data and files will exist deleted);
• System Restore – allows y'all to restore the country of Windows using a previously created restore point;
• System Prototype Recovery – allows to restore Windows from a full image backup on external media;
• Automated Repair/Beginning-up Repair – Windows tries to automatically find and gear up possible problems (the wizard tin independently repair the bootloader, BCD configuration and MBR (Principal Kick Record);
• Windows Startup Settings – allows you to select various Windows boot scenarios: Rubber Mode, disable driver digital signature enforcement, disable automated restart on system failure (this is the only mode to see the BSOD error code on the Windows kick screen),etc.;
• Uninstall Updates – allows to remove the recently installed updates (useful if Windows doesn't kicking after installing updates);
• Go back to the previous version – allows you to scroll dorsum to the previous Windows 10 build;
• Command Prompt – run command line to manually run diagnostic and repair commands.

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

You should see a control prompt window X:\Windows\System32>.

From the control line, you tin check the disk 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 find and fix problems with the registry, drivers, partitions, etc.) and other commands (there are quite a few manufactures on the site where nosotros show how to set various Windows bug in the recovery environment or WinPE).

To shut the WinRE command prompt and return to the boot way selection, run the command:

exit

Could not Find the Recovery Environment in Windows 10

In some cases, the calculator can't  kick into the Windows Recovery Surroundings. If yous try to reset the Windows, or kick into recovery mode, you may run across errors like "Could not find the recovery environs". This means that the partition with the WinRE or the .wim file of the recovery environment has been deleted/damaged; either ReAgent or BCD is not configured correctly.

The reasons why the WinRE environment stops booting or does not work correctly tin be different:

• The WinRE is disabled in Windows settings;
• The Boot Configuration Data Shop (BCD) doesn't incorporate entries to boot in recovery mode;
• The file winre.wim (WinRE surround image) is missing or moved;
• The WinRE configuration file ReAgent.xml is missing or contains incorrect settings.

Adjacent, we volition look at the chief ways to restore the WinRE environment in Windows 10 (for Windows seven and Windows eight.1, the procedure is the same).

Repairing WinRE (Windows Recovery Environment) with ReAgentc Tool

How to Manually Enable or Disable Windows Recovery Surround in Windows ten?

Try to disable and enable WinRE on your estimator past running the following commands in the elevated control 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 yous receive the error bulletin "REAGENT.EXE: The Windows RE image was not found", the winre.wim file or the System Recovery segmentation has probably been deleted.

Bank check BCD Entries for WinRE

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

Note. If WinRE has been successfully enabled using the reagent, the right WinRE entries should automatically appear in the boot configuration. Nonetheless, you'd meliorate check the value of recoverysequence parameter.

Brandish the current BCD entries:

bcdedit /enum all

In the list of boot options, find the Windows Boot Loader section with identifier={current}. In our instance, this entry looks like this:

Windows Boot Loader ------------------- identifier              {current} device                  partition=C: path                    \Windows\system32\winload.exe description             Windows 10 locale                  en-US 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

Find and retrieve the GUID value of recoverysequence attribute. In our case, information technology is {7c817935-e52f-11e6-9c2c-0050569efccb}.

Then y'all need to detect the boot configuration section having the identifier value equal to the GUID value obtained earlier and having Windows Recovery Environment in the description field. This entry tin wait like 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                   Yeah

If you lot cannot find this entry, await for another BCD record with another GUID as 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 point to another bulldoze (for case, [\Device\HarddiskVolume2]). If such department has been constitute, y'all can link this entry to kicking WinRE as the recovery environment for the electric current Os. Copy the GUID of the found entry and supersede it using the command:

bcdedit /set {current} recoverysequence {FoundGUID}

Note. If you are using multiboot, keep in heed that each Bone adds its own Windows Recovery Environment entry to the Microsoft Boot Manager. It is important not to get 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:

• Folder C:\Windows\System32\Recovery folder;
• Divide hidden System Reserved segmentation;
• Factory made OEM recovery partition (make sure you didn't delete information technology).

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

Also check the path to the wim file specified in ReAgent.xml (located  in C:\Windows\System32\Recovery folder 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 exist (the original partition has been deleted), you can change the path to <ImageLocation path="\Recovery\WindowsRE"), create the folder C:\Recovery\WindowsRE and copy the Winre.wim to information technology. Disable and enable WinRE once again:

reagentc /disable
reagentc /enable

Tip. The current Recovery Amanuensis configuration tin exist obtained using reagentc /info command. This control tin can will help to get the Boot Configuration Information (BCD) identifier and the physical path to Windows RE paradigm file:

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

Reset WinRE Settings in ReAgent.xml file

If the methods described above didn't help you to recover WinRE, you can endeavor to reset the recovery environment settings in ReAgent.xml file(backup this file in advance).

On Windows 10, just delete the ReAgent.xml file and it will be automatically created the next time yous enable WinRE with the control:

reagentc /enable

In Windows seven/Vista, open ReAgent.xml in a text editor (information technology's better to apply Notepad++) and clear the values of the following 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" starting time="0" guid="{00000000-0000-0000-0000-000000000000}"/> <InstallState state="0"/> <WinREStaged state="0"/>

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

reagentc /enable

Find and Copy the Winre.wim File Manually

If y'all cannot observe the Winre.wim file in whatever of the standard folders, try locating it using your file manager or with the following command:

dir /a /s c:\winre.wim

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

If you have establish the file, copy it in to a default location using the commands:

attrib -h -south 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 y'all couldn't detect the file, copy it from a similar Windows instance(the OS version and bitness must friction match), or from the install media/bootable USB flash drive. To exercise it, open up the \sources\install.wim (or install.esd) on the DVD/ ISO image using 7-Zip and extract the \Windows\System32\Recovery\Winre.wim and ReAgent.xml to the c:\Windows\System32\Recovery folder.  The original boot.sdi file must exist copied from the \Windows\Kicking\DVD binder.

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

Replace the path to the winre.wim file in the Recovery Amanuensis configuration:

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

Now just enable Windows Recovery Agent with this command:

reagentc /enable

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

Posted by: smithpren1947.blogspot.com

Share this post