WinRE Manager

Repair and rebuild the Windows Recovery Environment (WinRE) on Windows 10 and 11.

WinRE Manager services winre.wim, injects the OEM and Intel VMD drivers the recovery environment needs, verifies the registered recovery route, and keeps the recovery partition correctly sized. Safe to re-run: a machine that needs no work takes an idempotent fast path that mounts no WIM, does not modify the OS-disk partition layout, and does not disable, re-register, or enable WinRE. Runs on one machine, or as a scheduled SYSTEM task across a managed fleet.

What do you need?

Common Windows Recovery problems

If Windows is telling you something is wrong with the recovery environment, find the message below and start there.

The full error-by-error matrix — exact strings, causes, and what WinRE Manager does — is in the README.

Who is this for?

Three audiences. All drive the same control flow on every machine.

flowchart TD
    Start["Windows 10 / 11 machine<br/>with a broken or missing<br/>recovery environment"]

    Start --> Who{"Who is running<br/>WinRE Manager?"}

    Who -->|"Personal PC"| Single["One-off repair<br/>on your own laptop"]
    Who -->|"IT admin / sysadmin"| Fleet["Scheduled deployment<br/>across a managed fleet"]
    Who -->|"MSP / advanced"| Hosted["Hosting your own<br/>manifest, maps, and base WIM"]

    Single --> RunOne["Run WinRE-Manager.cmd<br/>Check · Preview · Repair"]
    Fleet --> RunFleet["Deploy WinRE.ps1 as SYSTEM<br/>via Scheduled Task / Intune / RMM"]
    Hosted --> RunHost["Configure your own<br/>self-hosted sources"]

    RunOne --> Flow["Same control flow<br/>on every machine"]
    RunFleet --> Flow
    RunHost --> Flow

    Flow --> Fast{"What does it find?"}
    Fast -->|"Nothing to fix"| FP["Tier 1 · fast path<br/>no OS-disk changes"]
    Fast -->|"WinRE registered, disabled"| EO["Tier 2 · enable-only<br/>prepare volume · re-register"]
    Fast -->|"WinRE missing or broken"| FU["Tier 3 · full update<br/>plan · shrink · rebuild · deploy"]

    FP --> Dedicated["DEDICATED WinRE<br/>on a dedicated recovery partition"]
    EO --> Dedicated
    FU --> Dedicated
    FU --> Fallback["OS-FALLBACK WinRE<br/>on C: · degraded but functional"]

    style Start fill:#1f6feb,stroke:#1f6feb,color:#fff
    style Dedicated fill:#238636,stroke:#238636,color:#fff
    style Fallback fill:#9e6a03,stroke:#9e6a03,color:#fff
    style Hosted fill:#8957e5,stroke:#8957e5,color:#fff

The four design invariants

Every decision in the codebase follows these four rules, in this order:

1. Never break Windows RE.
2. Never leave a machine without a working recovery route — to the extent the machine, its OS, and its storage stack allow.
3. Minimize the reagentc /disable → reagentc /enable window.
4. Do no work unless needed. When work is needed, prepare everything before touching anything.

Rules 1–3 are invariants: no code change may weaken them. Rule 4 is the working rule — the discipline by which rules 1–3 are enforced on the fast path, the enable-only path, and the destructive path. Full hierarchy, enforcement tables, and reasoning: Architecture.

Safety by design

The destructive path is surrounded by protections implemented in the code rather than relying on operator assumptions. Every preparation — planning the partition layout, resolving and verifying the driver artifacts, building and normalizing the candidate image — completes before WinRE is disabled or any partition is deleted. A failure before destruction leaves the old recovery route intact; a failure during the destructive sequence restores the previous state where the design can, and names the one residual corner it cannot close. The manager also refuses to run unelevated, on a non-x64 architecture, or concurrently with another instance, and it never modifies the OS volume’s BitLocker state.

The full model — every protection, the code path that enforces it, and the residual corner the deliberate post-deletion failure test is intended to close — is documented in README — Safety by design, Architecture, and Recovery partition.

Three tiers of work

Full pipeline, checkpoints, and the state model: Architecture and State and idempotency.

What WinRE Manager fixes

WinRE Manager exists because “reinstall Windows” is not a repair. The full error-by-error matrix — the exact error strings, the underlying cause, and what WinRE Manager does — is in the README. The failure classes:

• Recovery environment not found. WinRE disabled, or winre.wim missing from wherever reagentc points.
• “The Windows RE image was not found.” winre.wim absent, corrupt, or the wrong build.
• reagentc /enable failures. BCD inconsistencies, access-denied paths, Audit Mode / OOBE / sysprep states.
• Recovery partition too small. The partition cannot hold the serviced SafeOS image plus Microsoft’s 250 MiB servicing margin. Frequently surfaced by Windows Update as 0x80070643 — the well-known example is the Windows 10 update KB5034441; the underlying failure is not KB-specific.
• “Startup Repair cannot repair this computer automatically.” The deployed WinRE lacks the storage-controller driver the machine needs.
• Missing or mis-sized recovery partition geometry. Missing partition, undersized partition, recovery partition on a non-OS disk, recovery partition separated from C: by a data partition (v48 intervening-anchor path).

Detailed write-ups:

Documentation

Current release

v48 patch 1 raised ScriptVersion from 47 to 48, so every managed machine performs one full-update pass on its next scheduled run, then returns to the fast path. v48 patch 2 kept ScriptVersion at 48 and added a fail-fast elevation guard and a source-WIM hash cache; a machine already on v48 patch 1 continues on the fast path. Full release notes, migration steps, and per-machine field evidence: Changelog.

Requirements at a glance

• Windows 10 (build 19041+) or Windows 11 (build 22000+). Windows 11 24H2 and 25H2 explicitly supported.
• PowerShell 5.1 or 7.x.
• x64 OS architecture. ARM64 support is not claimed.
• Elevation or SYSTEM for production. The read-only harness runs unelevated when invoked directly; the recommended wrapper (WinRE-Manager.cmd) launches it elevated for complete query results.
• 7-Zip at C:\Program Files\7-Zip\7z.exe (installed via winget if missing).
• Internet access on first deployment. Offline after the first successful run on a machine whose state file is present and whose local safety checks pass.

Full requirements and caveats: README § Requirements.

Field-tested hardware

Selected results. Full per-machine evidence: Changelog.

The v44 patch 7 destructive path is field-verified on encrypted C: across eight distinct physical machines. The remaining coverage gaps — post-deletion failure on the intervening-anchor path, the v48 multi-intervening and surplus rejections, the transactional-WIM rollback branch, and the architecture gate on ARM64 — are documented in Testing.

Repository

• Repository: github.com/ArthurJDurand/WinRE-Manager
• Releases: github.com/ArthurJDurand/WinRE-Manager/releases/latest
• Bug reports / discussion: GitHub Discussions
• Security: SECURITY.md — do not file public issues for vulnerabilities.
• Contributing: CONTRIBUTING.md
• Sponsor: github.com/sponsors/ArthurJDurand
• License: MIT — see LICENSE.

Repository: github.com/ArthurJDurand/WinRE-Manager · Docs: ArthurJDurand.github.io/WinRE-Manager