Do not rebuild the ESP with BCDBoot merely to recover space; inspect and back up non-Microsoft content first, remove only specifically identified obsolete files, and resize the 100 MB ESP if cleanup does not provide durable headroom.
1. Capture recovery material and inspect the ESP
Before modifying the ESP or partition map:
- Create a current system backup and Windows recovery/installation USB.
- Record the BitLocker recovery key and suspend BitLocker protection if partition movement will be required.
- Record the existing partition map and firmware boot entries.
Open Command Prompt as Administrator and mount the ESP temporarily:
mountvol Y: /s
dir Y:\ /a
dir Y:\EFI /a
dir Y:\EFI\Microsoft\Boot /a
dir Y:\EFI\Microsoft\Boot\Fonts /a
Copy the ESP to protected storage before deleting anything:
robocopy Y:\ C:\ESP-Backup\ /e /copyall /dcopy:t /xj
fsutil volume diskfree Y:
Also inspect C:\Windows\Logs\CBS\CBS.log. Messages such as SpaceCheck: Insufficient free space, ServicingBootFiles failed. Error = 0x70, or space used by third-party/OEM files confirm that ESP capacity is blocking boot-file servicing.^1^
2. What can be removed
Treat the ESP as boot-critical shared storage. Microsoft states that Windows manages it and that it should not contain unrelated files; OEM material relevant to pre-OS operation can legitimately be stored there, however, so an unfamiliar OEM directory is not automatically disposable.^2^^3^
- Do not manually delete
BCD, bootmgfw.efi, bootmgr.efi, memtest.efi, or other contents under Y:\EFI\Microsoft\Boot.
- Do not delete entire OEM or vendor directories. They may contain firmware-update, diagnostics, recovery, or vendor boot components.
- Unused
.ttf files under Y:\EFI\Microsoft\Boot\Fonts have been used successfully as a targeted workaround in closely matching Microsoft Q&A cases.^4^ Back them up first and avoid deleting all fonts indiscriminately on multilingual or accessibility-dependent deployments.
- An OEM firmware binary should be moved only after identifying the exact file and validating it with the device manufacturer. One matching case moved an Insyde
isflash.bin out of the ESP, but that result does not establish that arbitrary BIOS .bin files are safe to remove.^5^
After cleanup:
fsutil volume diskfree Y:
mountvol Y: /d
Reboot once, confirm Windows starts normally, and then retry servicing.
3. Resize for the durable production correction
A 100 MB ESP is below Microsoft’s current UEFI/GPT deployment minimum: 200 MB for 512/512e-sector storage and 300 MB for 4Kn storage, formatted FAT32.^2^
Resizing is preferable to recurring cleanup, but Windows does not provide a general utility for moving intervening partitions. The usual default order is:
ESP → MSR → Windows → Recovery
Consequently, shrinking C: alone normally creates free space at the wrong side of the disk. Extending the ESP may require an offline/OEM partition tool capable of moving the MSR and OS partition.
For production:
- Verify the physical layout in Computer Management → Disk Management.
- Take a tested bare-metal backup.
- Use the hardware vendor’s supported tool where available; otherwise validate the chosen offline partition tool on an identical model first.
- Enlarge the existing FAT32 ESP to at least the applicable Microsoft minimum.
- Preserve its EFI System Partition type and all existing contents.
- Boot and test BitLocker, WinRE, firmware updates, and Windows Update.
Do not shrink or move the recovery partition unless it is actually adjacent to the ESP. In the Microsoft-recommended layout, Recovery is after Windows and therefore cannot directly supply contiguous space to the ESP.^2^
4. Reserve BCDBoot for repair or migration
BCDBoot copies Windows boot files and constructs the BCD store; it does not enlarge the partition. Use it only if the ESP was recreated, reformatted, migrated, or its boot files became corrupted.^6^
From Windows PE, after carefully confirming the Windows and ESP letters:
diskpart
list volume
exit
bcdboot D:\Windows /s S: /f UEFI
Drive letters in Windows PE may differ from normal Windows. Formatting the wrong volume or selecting the wrong ESP can make the machine unbootable. Also note that using /s prevents BCDBoot from creating the normal NVRAM firmware entry, so rebuilding an in-use ESP should follow a tested recovery procedure rather than being used as routine cleanup.^6^
Version-specific exception
If this is Windows 11 24H2 or 25H2 failing specifically on the May 2026 update, install the May 26, 2026 update or later first. Microsoft resolved that particular low-ESP-space servicing issue, so its workaround is unnecessary on later updates.^1^
References
- Resolved issues in Windows 11, version 24H2
- UEFI/GPT-based hard drive partitions
- Windows and GPT FAQ
- Why do I get different data for my used diskspace (C:). I stumbled upon this problem as I cant update windows because of an partition error. - Microsoft Q&A
- Windows Update failing (0xc1900201) - Microsoft Q&A
- BCDBoot Command-Line Options