Status: [LIVE] Endpoints found: https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/configure-uefigpt https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-movefileexw Source: https://github.com/PaulRobert1/WinRE-Relocator # WinRE Relocator **Relocate Windows Recovery Environment and extend C: online on supported basic GPT and MBR disks.** WinRE Relocator is a standalone PowerShell script that creates and verifies a replacement recovery partition before deleting the original. It can use an existing unallocated gap before C: or unallocated space at the end of the disk. It never moves the beginning of C: or initiates or schedules a reboot. **[Download Move-WinRE-ExtendC.ps1 — v3.0.2](https://github.com/PaulRobert1/WinRE-Relocator/releases/download/v3.0.2/Move-WinRE-ExtendC.ps1)** [Full operations guide](docs/OPERATIONS.txt) · [Validation record](docs/VALIDATION.txt) · [Release notes](RELEASE_NOTES.md) > **Validation status:** The nine helper suites passed **318 checks on Windows PowerShell 5.1** and **297 checks on Linux PowerShell 7**, with zero failures. One Windows fixture and two Linux fixtures were skipped; see the results below. Pending-maintenance checks use mocked registry reads. Real partition changes, WinRE registration, BitLocker operations, REAgentC rollback registration, and recovery boot have **not** been integration tested. Validate the tool on a disposable Windows clone before production use. ## New in v3.0.2: optional pending-cleanup exception `-AllowPendingCleanup` permits a narrow set of recognized pending file deletions after both Windows file-operation queues are inspected. The default remains strict: queued operations block preview and apply for a plan that would change partitions. The option preserves the registry entries and queued files, and it does not permit pending Windows servicing, replacements, or unrecognized operations. See [Pending maintenance and cleanup queues](#pending-maintenance-and-cleanup-queues) for the accepted scope and commands. ## Volume GUID path compatibility v3.0.0 was reported to stop during preflight with `Get-Item: Illegal characters in path` while reading `Winre.wim` through a path such as `\\?\Volume{GUID}\Recovery\Windo