Windows update failures often come from a full EFI System Partition that cannot store new boot files. This problem shows up during major updates or feature installs and usually blocks the entire process. Clearing old or unnecessary EFI boot fonts frees space instantly and lets the update continue. The fix works fast and avoids risky repartitioning tools that ask for payment.
Windows Update EFI Fix: Quick Facts
- EFI partition can fill up on older systems
- Windows updates need free EFI space to write new boot files
- Removing unused font files frees several megabytes
- Fix works on Windows 10 and Windows 11
- No drive wipe or reinstall needed
- Requires only built-in Windows tools
Why The EFI Partition Fills Up
The EFI System Partition holds secure boot components, language files, and boot managers. Windows relies on this space during major updates, so a full EFI partition blocks the upgrade. Older systems often have a 100 MB partition that fills over time. Clearing oversized font files creates enough room for update files to load.
- Stores bootloader files
- Can fill with old language fonts
- Blocks updates when full
A full EFI partition triggers confusing errors, but the fix is simple once the cause is clear.
Why Windows Updates Get Blocked
Major Windows updates depend on writing fresh boot components. A full EFI partition stops these changes and forces users into confusing repair loops. Keeping the EFI partition healthy prevents update failures, boot errors, and repeated rollback attempts. A small cleanup often restores full update functionality.
- Prevents blocked updates
- Avoids unnecessary reinstalls
- Improves system reliability
- Reduces failed restarts
- Helps extend system lifespan
EFI issues rarely announce themselves, so quick checks prevent headaches later.
How To Free EFI Partition Space
A short command sequence frees EFI space safely. No paid tools or boot disks are needed. This fix only touches fonts and language folders inside the EFI partition and leaves core boot files intact. The goal is to mount the EFI partition, clear the bloat, and give Windows enough room to finish the update.
Before proceeding to the below in depth steps to address the issues, try fixing the problem by accessing the following:
- Settings
- System
- Fix problems using Windows Update
- Click Reinstall Now
If the above option does not work, then proceed with the below.
Open Command Prompt As Administrator
- Click Start
- Type cmd
- Right-click Command Prompt and choose Run as administrator
Mount The EFI Partition
In the elevated Command Prompt, type:
mountvol S: /s
If this works with no error, the EFI partition is now mounted as drive S: and you can go to the cleanup steps below.
If You See “The Parameter Is Incorrect”
Some systems block mountvol after a failed update. Use DiskPart to attach the EFI partition instead. Run the following in Command Prompt as Administrator:
diskpart
list volume
Look in the list for the small FAT32 volume that is about 100–300 MB in size and shows System in the Info column. Note its volume number, for example Volume 1.
Then run:
select volume <your EFI volume number>
assign letter=S
exit
Replace <your EFI volume number> with the correct number, for example:
select volume 1
assign letter=S
exit
After that, the EFI partition will be available at S: and you can run the cleanup commands.
Extra Cleanup For Smaller EFI Partitions
Older systems often have a tiny 100 MB EFI partition that fills up fast. Even after clearing fonts, major Windows updates can still fail because dozens of unused language folders sit in the Microsoft Boot directory. These folders hold localized boot resources that most English-only systems never use. Removing them is safe and frees the extra space that Windows needs during big updates.
Universal Safe CMD Commands To Mount And Clear Fonts
Still in Command Prompt, with the EFI partition mounted as S:, run:
del /f /q S:\EFI\Microsoft\Boot\Fonts\*.ttf
This removes EFI boot fonts that Windows can regenerate when needed. It frees several megabytes immediately and is safe on Windows 10 and Windows 11.
- Frees extra EFI space
- Targets only font files
- Works on Windows 10 and Windows 11
Remove Old Language Folders To Free Even More Space
A full EFI partition usually includes more than forty language folders that do not affect a normal English install. Windows keeps only the active language and can rebuild resources when required. Deleting unused language folders typically frees another 20 to 40 megabytes and stops the update from running out of space during the reboot phase.
If your native or display language is English, you can safely remove all the language folders listed below. If you use another language as your main Windows display language, keep that folder and remove the rest.
Universal Safe CMD Commands
(Copy and paste entire block if your primary Windows language is English):
rmdir /s /q S:\EFI\Microsoft\Boot\bg-BG
rmdir /s /q S:\EFI\Microsoft\Boot\cs-CZ
rmdir /s /q S:\EFI\Microsoft\Boot\da-DK
rmdir /s /q S:\EFI\Microsoft\Boot\de-DE
rmdir /s /q S:\EFI\Microsoft\Boot\el-GR
rmdir /s /q S:\EFI\Microsoft\Boot\en-GB
rmdir /s /q S:\EFI\Microsoft\Boot\es-ES
rmdir /s /q S:\EFI\Microsoft\Boot\es-MX
rmdir /s /q S:\EFI\Microsoft\Boot\et-EE
rmdir /s /q S:\EFI\Microsoft\Boot\fi-FI
rmdir /s /q S:\EFI\Microsoft\Boot\fr-CA
rmdir /s /q S:\EFI\Microsoft\Boot\fr-FR
rmdir /s /q S:\EFI\Microsoft\Boot\hr-HR
rmdir /s /q S:\EFI\Microsoft\Boot\hu-HU
rmdir /s /q S:\EFI\Microsoft\Boot\it-IT
rmdir /s /q S:\EFI\Microsoft\Boot\ja-JP
rmdir /s /q S:\EFI\Microsoft\Boot\ko-KR
rmdir /s /q S:\EFI\Microsoft\Boot\lt-LT
rmdir /s /q S:\EFI\Microsoft\Boot\lv-LV
rmdir /s /q S:\EFI\Microsoft\Boot\nb-NO
rmdir /s /q S:\EFI\Microsoft\Boot\nl-NL
rmdir /s /q S:\EFI\Microsoft\Boot\pl-PL
rmdir /s /q S:\EFI\Microsoft\Boot\pt-BR
rmdir /s /q S:\EFI\Microsoft\Boot\pt-PT
rmdir /s /q S:\EFI\Microsoft\Boot\qps-ploc
rmdir /s /q S:\EFI\Microsoft\Boot\qps-plocm
rmdir /s /q S:\EFI\Microsoft\Boot\ro-RO
rmdir /s /q S:\EFI\Microsoft\Boot\ru-RU
rmdir /s /q S:\EFI\Microsoft\Boot\sk-SK
rmdir /s /q S:\EFI\Microsoft\Boot\sl-SI
rmdir /s /q S:\EFI\Microsoft\Boot\sr-Latn-RS
rmdir /s /q S:\EFI\Microsoft\Boot\sv-SE
rmdir /s /q S:\EFI\Microsoft\Boot\tr-TR
rmdir /s /q S:\EFI\Microsoft\Boot\uk-UA
rmdir /s /q S:\EFI\Microsoft\Boot\zh-CN
rmdir /s /q S:\EFI\Microsoft\Boot\zh-TW
- Safe for English-based systems
- Only removes unused language folders
- Prevents low-space EFI update failures
Verify EFI Free Space Before Restarting
Once fonts and language folders are removed, checking free space on the EFI partition confirms that the update has room to finish. Windows usually needs at least 25 MB free during the reboot stage for major upgrades. Systems with 30–50 MB free almost never hit rollback loops related to EFI space. Verifying this number before restarting cuts down on wasted time and repeated failures.
Universal Safe CMD Command To Check Space:
fsutil volume diskfree S:
Look at the Total free bytes value. If it shows 25 MB or more, you are in the safe range. Above 30 MB is ideal for larger updates.
- Confirms that EFI space is update ready
- Helps avoid another rollback cycle
- Works on any modern Windows installation
If The Update Still Fails
Some systems continue to fail the Windows update even after the EFI fonts and language folders are removed and enough free space has been restored. When this happens, the cause is no longer the EFI partition. Instead, Windows Update itself becomes corrupted from repeated failed attempts. The update cache, permissions, and servicing stack can lock up, which produces error 0x80070005 during the “commit boot files” or “offline servicing” stage. Resetting these components clears damaged data and restores the system to a clean update-ready state.
Clear Broken Windows Update Cache
Run these commands in an elevated Command Prompt to stop the update services and rename the folders that store cached update files:
net stop wuauserv
net stop bits
net stop cryptsvc
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start bits
net start cryptsvc
This forces Windows to rebuild fresh update folders and removes any corrupted or incomplete update files.
Reset Permissions On Update Components
Damaged permissions can block updates from writing the system files they need. Resetting permissions ensures the update can proceed normally:
icacls C:\Windows\SoftwareDistribution /grant administrators:F /t
icacls C:\Windows\System32\catroot2 /grant administrators:F /t
This restores full administrative access to both update storage directories.
Repair Windows Component Store With DISM
The servicing stack can break after repeated failed updates. Using DISM fixes the underlying component store:
DISM /Online /Cleanup-Image /RestoreHealth
Once DISM completes, run:
sfc /scannow
SFC repairs system files and ensures no corrupted components block the update.
Restart And Try The Update Again
After clearing update caches, fixing permissions, and repairing the Windows component store, the system is fully reset for the next update attempt. Combined with the newly cleaned EFI partition, this removes the last major causes of 0x80070005 and allows repair-version updates like Windows 11 24H2 to complete successfully.
Why This Step Matters
- Clears corrupted update downloads
- Fixes permissions that block system-level writes
- Repairs the component store used during offline update servicing
- Prevents endless rollback loops
- Works on Windows 10 and Windows 11
This section ensures users understand that EFI cleanup solves only one part of the problem, and that corrupted update components require a separate reset to fully restore the update pipeline.
Why EFI Space Matters For Updates
Windows updates rely on more than free space on the C drive. Boot partitions play a key role in loading and finalizing update components. When the EFI space is too tight, updates fail with generic messages that hide the real cause. Fixing the EFI space issue helps Windows apply important security patches and version upgrades safely.
Systems built on older versions of Windows often carry a smaller EFI partition. Over time, language resources, fonts, and legacy boot files fill the space. Clearing unused content prevents future update failures and keeps the system healthier over the long run.
Relevant Source (Superuser): What Is The Absolute Minimum Size A UEFI System Partition Can Be
This Q&A explains common EFI partition size guidelines and notes that the EFI partition stores languages, fonts, and other boot data, which supports your point about small partitions filling over time.
Relevant Source (GaryTown): Low Space On EFI (System) Partition – Clean Up
This article describes real-world Windows upgrade failures caused by low EFI space and shows how cleaning unnecessary EFI content prevents update issues, aligning with your big picture overview.
Fix Windows Update Without Reinstalling
A full EFI partition can trigger stubborn update failures, but the fix is simple once you know where to look. Clearing outdated boot fonts frees enough space for new Windows boot files and avoids the pain of wiping drives, reinstalling Windows, or getting trapped behind paid partition tools. A quick command line cleanup restores the space Windows needs without risky repartitioning. Staying aware of EFI limits keeps updates stable and prevents the kind of frustration that comes from forcing tools that don’t actually solve the problem.
EFI Partition Fix FAQ
Does deleting EFI fonts break Windows?
No. These fonts are not required for booting. Windows regenerates needed ones automatically.
Why is the EFI partition only 100 MB?
Older Windows installs created smaller EFI partitions that do not fit modern update requirements.
Will updates work after clearing the fonts?
Yes. This method restores enough space for boot updates to complete successfully.
Do I need to rebuild the bootloader?
No. Only free space is required for updates to proceed. Bootloader files remain intact.
Can I expand the EFI partition instead?
Yes, but free tools often block EFI resizing. The command-line cleanup is safer and faster.
How JENI Helps Keep Systems Stable
JENI supports users by helping them avoid many of the update failures that come from slowdowns, cluttered drives, and inconsistent system performance. A cleaner and more efficient system makes it less likely that Windows updates will hit roadblocks tied to storage, fragmentation, or background conflicts. The tools built into JENI focus on keeping everyday performance predictable, which supports a smoother update experience in general.
Key Ways JENI Supports System Health
- Keeps storage cleaner which reduces hidden system pressure
- Manages background load so updates process more reliably
- Helps maintain consistent performance before and after major updates
The overall goal is to reduce complications that often surface during large Windows transitions and version changes. A healthier system is far less likely to run into space constraints or stalled update processes that disrupt normal use. JENI works to maintain that stability day to day so updates have fewer reasons to fail. The end result is a system that stays responsive, predictable, and ready for long update cycles without the problems that typically slow users down.
Related Articles
Windows Update Loop Fixes:
Fix stubborn Windows update loops, failed installs, and repeated restart problems that keep Windows from completing important updates.
Windows 11 24H2 Bug Fixes:
Troubleshoot Windows 11 24H2 problems that affect File Explorer, the Start menu, system stability, and daily usability.
Windows Startup Repair Options:
Use Windows recovery tools to repair startup problems, boot failures, update damage, and system issues without wiping the PC.
Windows Driver And Firmware Fixes:
Improve Windows stability by checking drivers, firmware, update behavior, and hardware-level problems that can trigger system errors.
Blue Screen And Corruption Fixes:
Find hidden Windows corruption, repair damaged system files, and reduce crashes before they become larger recovery problems.
Windows Maintenance For Stability:
Keep Windows faster, safer, and more reliable with a practical maintenance routine for updates, cleanup, repair, and system health.
