Everything is ready — backup done, free space waiting — and a partition smaller than 1 GB vetoes the whole plan. Here is what it is protecting, and how to get past it without losing it.
Of all the blockers in this series, the recovery partition is the one people are most tempted to simply delete — it is tiny, it has no drive letter, and it is in the way. That temptation deserves a slower answer. This partition is the machine's rescue environment, and there are three honest ways past it, graded here from least to most destructive, with the full rebuild route spelled out for those who take it.
The recovery partition holds WinRE — the Windows Recovery Environment: the toolbox Windows boots into when it cannot start normally, offering Startup Repair, System Restore, Safe Mode entry and the "Reset this PC" machinery. On many Windows 10 and 11 installations it sits immediately after C — which puts it precisely where an extend needs to go. Check whether WinRE lives there and is healthy from an elevated prompt with reagentc /info. Respect the partition: it is small because its job is narrow, and its job is rescuing the machine on its worst day.
A third-party partition tool can slide the recovery partition to the far side of the free space, leaving the unallocated block touching C. Nothing is deleted; WinRE keeps working from its new position, and reagentc /info afterwards confirms it still points at the partition correctly. Of the routes past this blocker, this is the least destructive and the one most technicians reach for — with the standing conditions from the safety case: backup first, mains power, and a tool from its maker's own site, because moving any partition means moving its data sector by sector.
The built-in-only route is more surgical, and it must be done in order so the recovery environment survives the trip:
reagentc /disable — this pulls the WinRE image out of the recovery partition into a file on C, so deleting the partition no longer deletes your recovery environmentdelete partition override (it is protected against casual deletion, which is why the override word exists)set id=de94bba4-06d1-4d40-a16a-bfd50179d6ac followed by the GPT attributes line gpt attributes=0x8000000000000001reagentc /enable and then reagentc /info to prove WinRE is enabled and living on the new partitionGraded honestly: this route is free and uses only Windows' own tools, but it has the most steps where a wrong volume number can hurt. If any step's output does not match expectations, stop and restore from your backup rather than improvising.
The option nobody lists is sometimes the right one: do not move the recovery partition at all. If your free space can reach C by a different arrangement — a data partition that can be moved instead — the recovery partition never needs to be touched. And if the total gain is small, freeing space inside C (moving libraries and games to D) may deliver the breathing room with zero risk to the machine's safety net. The recovery partition is your rescue environment; every route that disturbs it must repay that disturbance with a verified WinRE at the end, or it has traded tomorrow's rescue for today's gigabytes.
See the recovery partition handled the careful way, with the WinRE check before and after, in the full video.
▶️ Watch Full VideoWindows will keep booting and working normally — WinRE is only used when something else goes wrong. What you have lost is the built-in rescue toolbox: Startup Repair, the recovery menu and the environment Reset this PC runs from. You can recreate it by making a small NTFS partition after C, marking it as a recovery partition and running reagentc /enable, or restore it from a Windows installation USB's recovery options. Do it now, not during a crisis.
Run reagentc /info from an elevated prompt. It reports whether WinRE is Enabled and shows the partition it lives on. For a full proof, restart into the recovery menu once — hold Shift while choosing Restart — and confirm the blue recovery screen appears. A thirty-second test today beats a surprise later.
Yes — major Windows updates sometimes create a fresh recovery partition (usually at the end of the system disk) when WinRE itself is updated or the old partition is too small. That is one more reason the map reading matters every time: the blocker can reappear in a new position after a feature update, and yesterday's layout notes may no longer match the disk.