servicing failing due to full EFI system partition

Hakim Ismail 40 Reputation points
2026-11-14T04:31:20.8833333+00:00

Hi team,

One of our workstations keeps failing on cumulative and boot component updates because the EFI System Partition (ESP) has run out of free space. The main C: drive still has plenty of room, so it's strictly that tiny 100MB system partition choking up the servicing stack.

Before I start touching the partition layout or risking a non-bootable machine, I want to check what's actually eating up the space inside. If I assign a temporary drive letter to the ESP via diskpart and inspect it, what's safe to clear out, like leftover OEM BIOS firmware update bins or unused language font files under \EFI\Microsoft\Boot\Fonts? And if deleting obsolete files still doesn't give enough headroom, is it safer to shrink the adjacent recovery/OS partition and extend the ESP using a third-party partition tool, or rebuild it cleanly with bcdboot?

Please let me know what you guys usually do in production without risking boot issues.

Windows for business | Windows Client for IT Pros | Devices and deployment | Set up, install, or upgrade
0 comments No comments

2 answers

Sort by: Oldest
  1. AI answer

    2026-11-14T04:32:22.8233333+00:00

    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:

    1. Verify the physical layout in Computer Management → Disk Management.
    2. Take a tested bare-metal backup.
    3. Use the hardware vendor’s supported tool where available; otherwise validate the chosen offline partition tool on an identical model first.
    4. Enlarge the existing FAT32 ESP to at least the applicable Microsoft minimum.
    5. Preserve its EFI System Partition type and all existing contents.
    6. 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

    1. Resolved issues in Windows 11, version 24H2
    2. UEFI/GPT-based hard drive partitions
    3. Windows and GPT FAQ
    4. 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
    5. Windows Update failing (0xc1900201) - Microsoft Q&A
    6. BCDBoot Command-Line Options
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. HLBui 15,990 Reputation points Independent Advisor
    2026-11-14T05:31:48.6666667+00:00

    Hi Hakim Ismail

    In production, I generally recommend taking the least invasive approach first. If the EFI System Partition (ESP) is only 100 MB, it's fairly common to see cumulative updates and servicing stack operations run into free-space limitations on older Windows installations.

    Before making any partition changes, it's reasonable to temporarily assign a drive letter to the ESP and review its contents. In many cases, you'll find leftover OEM firmware update files or other vendor-specific artifacts that are no longer needed. However, I'd be very cautious about deleting anything under the core Microsoft boot structure unless you're absolutely certain what it does. The Fonts folder can sometimes contain language-specific font files that are not required in your environment, but I still recommend making a backup of the ESP before removing anything.

    If cleanup doesn't provide enough free space, my preferred long-term solution is usually to extend the ESP rather than continually managing its contents. Expanding the partition to 300-500 MB generally eliminates future servicing issues and aligns better with what we see on more recent Windows deployments. As long as you have a verified backup and use a reputable partition management tool, extending the ESP is typically lower risk than rebuilding it from scratch.

    I personally treat recreating the ESP and rebuilding boot files with bcdboot as a recovery option rather than a first choice. It works well when necessary, but modifying the existing partition layout is usually the safer and more predictable path if the system is otherwise healthy.

    If you find this answer useful, please consider clicking "Accept Answer" so it can help other admins who run into the same ESP space issue in the future

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.