Windows Recovery Environment

HollowKnight · 21 Apr 2018

NavyLCDR said:

I don't keep recovery partitions on my computers. Everything available in the recovery partition is also available by booting from a Windows 10 installation USB flash drive...

Strongly agree and highly recommended. Just create a recovery USB after fresh install or major upgrades and put it on cloud drive.
I don't like Plug-and-Play style of Windows 10 installation, it keeps administrators away from control and customization. Why M$ can't make it simple and clear like anaconda or calamares installers in some Linux distros?!

cereberus · 22 Apr 2018

NavyLCDR said:

I don't keep recovery partitions on my computers. Everything available in the recovery partition is also available by booting from a Windows 10 installation USB flash drive. And...like you say...if my system gets messed up enough to actually require the recovery partition, I'm going to restore a backup image or do a clean install anyway.

This is particularly true on a 32GB tablet where 0.5GB is significant by comparison.

Saltgrass · 22 Apr 2018

It may have only been temporary but you were running some of the commands from a non-admin prompt window..

The bootrec /Rebuildbcd can also reset some of those values, just not sure what setting some of the Reagentc entries to "0" actually did.

topgundcp · 22 Apr 2018

@Saltgrass

just not sure what setting some of the Reagentc entries to "0" actually did.

Both Winre.wim and Reagent.xml are under: C:\Windows\System32\Recovery
If contains all 0's. ReAgentc will search for the Recovery Partition identified by ID type (DE94BBA4-06D1-4D40-A16A-BFD50179D6AC) and move WinRe.wim there then update the xml file to contain the offset, its GUID and also set an entry in the BCD.

Code:

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

<WindowsRE version="2.0">
  <WinreBCD id="{b150d609-3dff-11e8-bb6b-002683327ad9}"/>
  <WinreLocation path="\Recovery\WindowsRE" id="0" offset="1048576" guid="{318b254a-67c2-4d2d-ab28-25562cbe3f69}"/>
.....