RavenHawkTech LLC

Fixing “We Couldn’t Update the System Reserved Partition” During Windows Server 2025 Upgrades

Windows Server Upgrade Recovery

When Windows Server upgrades fail during setup, the root cause is not always the installer itself. In several successful repair cases, the failure came down to an undersized or damaged EFI/System Reserved partition, a missing or broken WinRE configuration, or migration failures during the second boot phase.

Windows Server 2025 upgrades can expose old boot and recovery partition problems that may have gone unnoticed for years. A server can appear healthy during normal operation but still fail during setup when Windows attempts to update the System Reserved or EFI partition, migrate boot data, or validate the Windows Recovery Environment.

This guide summarizes a repair workflow that successfully resolved upgrade failures tied to System Reserved partition errors, EFI partition corruption, WinRE misconfiguration, and SECOND_BOOT migration failures.

Production warning: These steps modify boot and recovery partitions. Confirm you have a tested backup, remote access fallback, console access, and a recovery plan before changing EFI, System Reserved, or WinRE partitions on a production server.

Primary Symptoms

The affected servers did not all fail in exactly the same way, but the symptoms clustered around boot, recovery, and migration problems during the upgrade process.

  • “We couldn’t update the system reserved partition”
  • 0xC1900101 – 0x4000D failures during SECOND_BOOT / MIGRATE_DATA
  • Missing or improperly configured Windows Recovery Environment partition
  • Boot failures after partition changes
  • Blue screen STOP: IO1_INITIALIZATION_FAILED
  • Server rollback during upgrade

What Actually Fixed the Upgrade Failures

Across the successful repairs, the most reliable fix was rebuilding the EFI partition at a safer size, then repairing or recreating the WinRE recovery configuration where needed. Once the boot files and recovery partition were corrected, the affected upgrades were able to continue normally.

EFI Partition

Several systems had an EFI partition that was missing, undersized, damaged, or not formatted correctly for the upgrade process.

WinRE Partition

Other systems failed because Windows Recovery Environment was missing, disabled, incorrectly staged, or stored on a partition that setup could not use.

Step 1: Rebuild the EFI Partition

The most important repair was replacing the existing EFI partition with a new 500 MB FAT32 EFI partition, then rebuilding the Windows boot files with bcdboot.

Important: Confirm the disk and partition numbers on the target server before running delete commands. The numbers below are examples from a successful repair path and may not match your system.

diskpart
list disk
select disk 0
list partition

After identifying the existing EFI partition, delete it using DiskPart. In the documented repair, the EFI partition was partition 2.

select partition 2
delete partition override

Create a new 500 MB EFI partition, format it as FAT32, label it, and assign a temporary drive letter.

create partition efi size=500
format quick fs=fat32 label="System"
assign letter=S

Then rebuild the Windows boot files to the new EFI partition.

bcdboot C:\Windows /s S: /f UEFI

After the boot files are rebuilt, reboot the server and confirm that it starts normally before retrying the Windows Server upgrade.

Step 2: Repair the WinRE Recovery Partition

Some systems continued to fail until the Windows Recovery Environment partition was repaired. The most reliable approach was to ensure the recovery partition was large enough, stage Winre.wim correctly, and re-enable WinRE with reagentc.

  1. Create or resize the recovery partition to at least 1 GB.
  2. Assign a temporary drive letter to the recovery partition, such as R:.
  3. Create the recovery folder path: R:RecoveryWindowsRE.
  4. Copy Winre.wim into that folder.
  5. Disable and re-enable WinRE.
  6. Verify WinRE status before retrying the upgrade.
reagentc /disable
reagentc /enable
reagentc /info

Key check: Do not assume WinRE is healthy just because the server boots. Run reagentc /info and confirm that Windows RE is enabled and pointing to the expected recovery location.

What If Winre.wim Is Missing?

On some servers, Winre.wim was missing entirely. In those cases, the successful recovery methods included restoring the file from a matching Windows Server ISO, copying it from another healthy server running the same operating system version, or using DISM to restore missing recovery components.

For upgrade work, version alignment matters. Avoid grabbing recovery files from a mismatched operating system build unless you have confirmed compatibility for that specific repair scenario.

Additional Fixes That Helped

EFI and WinRE repair handled the core issue on multiple systems, but several cleanup steps also helped reduce upgrade friction and migration failures.

  • Use selective startup with msconfig to reduce third-party service and driver interference during migration.
  • Clean up old user profiles and corrupted ProfileList registry entries.
  • Remove stale roaming profile references.
  • Confirm the EFI partition is formatted as FAT32.
  • Confirm the server is booting in UEFI mode rather than Legacy BIOS mode.
  • Run DISM and SFC before attempting the upgrade again.
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Validation Commands

Before retrying the upgrade, validate the boot and recovery configuration. These commands are useful for checking partition layout, WinRE status, boot entries, and mounted volumes.

reagentc /info
diskpart
list partition
bcdedit
mountvol
Get-Partition

Root Cause Pattern

The pattern was consistent: systems with a missing or undersized EFI partition were more likely to fail with System Reserved partition errors, while systems with missing or broken WinRE configuration were more likely to fail during SECOND_BOOT migration. Repairing both areas created a clean path for the upgrade to continue.

Operational takeaway: Before spending hours chasing generic setup errors, inspect the EFI/System Reserved partition and WinRE configuration. A clean boot partition plus a valid recovery environment can be the difference between repeated rollback and a successful Windows Server 2025 upgrade.

Final Thoughts

Windows Server upgrade failures can look vague from the setup screen, but the fix may be very specific. In these successful cases, rebuilding the EFI partition, restoring WinRE, confirming UEFI boot mode, and cleaning up migration blockers allowed the upgrades to proceed normally.

For administrators planning in-place upgrades to Windows Server 2025, it is worth validating partition layout, WinRE health, and system image integrity before launching setup. That preparation can prevent failed upgrade loops, rollback windows, and emergency boot repair work after hours.