Windows Update Error Fix – KB5066835 / KB5066128 Not Installing? Why Not Try This?

You clicked “Install.” Windows said it would be a few minutes. Then — nothing. An error code, a spinning circle going nowhere, or a silent rollback that leaves you exactly where you started.

If KB5066835 or KB5066128 is refusing to install on your Windows 11 PC, you are not imagining it — and you are definitely not alone. Microsoft’s own Q&A forums are flooded with users hitting this exact wall.

The good news? There are clear, working fixes. This guide walks you through every one of them, from the 30-second quick checks to the deeper repairs that solve the stubborn cases.

What Are KB5066835 and KB5066128? (And Why They Matter)

Before you fix it, it helps to know what you’re actually dealing with.

KB5066835 is the October 2025 cumulative update for Windows 11. It targets:

• Version 24H2 (Build 26100.6899)
• Version 25H2 (Build 26200.6899)

It includes security patches, servicing stack improvements, and a significant change to how Windows handles RSA cryptography — which, as we’ll see, is directly responsible for some of the failures people are seeing.

KB5066128 is the companion .NET Framework update (3.5 and 4.8.1) for the same builds. It often fails alongside KB5066835, and the fixes for one usually resolve the other too.

Skipping these updates isn’t a safe option. Without them, your system is missing security patches that protect against real, actively exploited vulnerabilities.

The Error Codes — What Each One Actually Means

The original article covered three error codes. In practice, users are reporting six distinct failures. Here’s what each one tells you about where the problem is:

Note the last two — 0x800F0983 and 0x800F0922 — these are specific to KB5066835 and were widely reported in late 2025. They are caused by a nearly-full EFI partition, not corrupted files. The standard SFC/DISM approach won’t fix them.

Step-by-Step Fixes of KB5066835 / KB5066128 Not Installing

Quick Checklist Before You Start

Run through these first. They resolve about 30% of cases before you need to go any further:

• Restart your PC — not sleep, not hibernate. A full restart clears pending update states
• Check you have at least 10 GB free on your C: drive (Settings → System → Storage)
• Pause your antivirus temporarily — some security tools block update file writes
• Disconnect VPN if you’re using one — it can interfere with Microsoft’s update servers
• Make sure your Windows version — press Win + R, type winver. You need 24H2 or 25H2 for KB5066835

If you’ve done all five and the update still fails, move to the fixes below.

Let’s go through the most effective solutions. Try them in order. One of them should work for you.

Fix 1: Run the Windows Update Troubleshooter

The fastest starting point. It catches about a third of common update problems automatically.

1. Open Settings → System → Troubleshoot → Other troubleshooters
2. Find Windows Update and click Run
3. Let it finish — it may take 2–3 minutes
4. Restart your PC and try the update again

If it finds issues but the update still fails after the restart, continue to Fix 2.

Fix 2: Clear the Windows Update Cache

Corrupted cached update files are one of the most common causes. Here’s how to flush them completely:

1. Open Command Prompt as Administrator (search “cmd” → right-click → Run as administrator)
2. Run these commands one at a time, pressing Enter after each:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver

3. Now delete the cache folders:

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old

4. Restart the services:

net start wuauserv
net start cryptSvc
net start bits
net start msiserver

5. Close Command Prompt, restart your PC, and try the update again.

This is one of the most effective fixes for the 0x8024a205 and 0x80240069 errors.

Fix 3: Repair System Files with SFC and DISM

If the cache flush didn’t work, corrupted system files may be blocking the installation. Run both tools — in this order:

Step 1 — DISM (runs first, deeper repair):

Open Command Prompt as Administrator and run:

DISM /Online /Cleanup-Image /RestoreHealth

This connects to Windows Update servers to download and replace damaged files. It takes 10–20 minutes. Let it finish completely.

Step 2 — SFC (runs second, repairs system files using the now-repaired image):

sfc /scannow

This takes 5–10 minutes. Once it’s done:

• If it says “Windows Resource Protection found corrupt files and repaired them” → restart and try the update
• If it says “no integrity violations found” → the problem is elsewhere; continue to Fix 4

Why run DISM first? SFC uses the Windows image to repair files — but if the image itself is corrupted, SFC repairs things with broken files. Running DISM first ensures SFC has a clean image to work from.

Fix 4: Manually Download and Install from the Microsoft Update Catalog

This bypasses Windows Update entirely — and it works for the majority of stubborn failures, including the 0x80240069 download error.

1. Go to catalog.update.microsoft.com
2. Search for KB5066835 (or KB5066128)
3. Critical step: match the download to your exact Windows version:
   • Press Win + R → type winver → note your version (24H2 or 25H2)
   • Go to Settings → System → About → check if you have a 64-bit (x64) or ARM system
4. Download the correct .msu file
5. Double-click it to install

Getting the version wrong (e.g., downloading the 24H2 package on a 25H2 system) will cause an immediate failure — so double-check before downloading.

Fix 5: Check Your EFI Partition Space (The Fix Most Guides Miss)

This one is responsible for the widespread 0x800F0983 and 0x800F0922 errors with KB5066835 specifically, and almost no mainstream guides cover it.

Windows 11 updates need free space in your EFI (Extensible Firmware Interface) System Partition — a small hidden partition that manages your PC’s boot process. If it’s nearly full, the update cannot write its files and fails silently or rolls back.

How to check:

1. Press Win + R, type diskmgmt.msc, press Enter
2. Look for a partition labelled “EFI System Partition” — it’s usually 100–550 MB
3. If it shows less than 15 MB free, this is your problem

How to fix it:

1. Open Command Prompt as Administrator
2. Mount the EFI partition:

mountvol X: /s

3. Navigate to it:

X:
cd EFI\Microsoft\Boot\Fonts

4. Delete unused font files (these are safe to remove):

del *.ttf

5. Unmount it:

mountvol X: /d

6. Restart and try the update again

Important: Only delete the font files from the EFI partition. Do not delete any other files in this location — doing so could prevent your PC from booting.

One user on Microsoft’s forums confirmed this exact fix: after their EFI partition had only 2 MB free, clearing the fonts folder resolved KB5066835 immediately.

Fix 6: Use the “Fix Problems Using Windows Update” Recovery Option

This is a lesser-known built-in option that essentially performs a repair reinstall of the update without touching your files or apps.

1. Go to Settings → System → Recovery
2. Look for “Fix problems using Windows Update”
3. Click it and follow the prompts — it will download a repair version of your Windows build

The process takes 1–2 hours and requires a stable internet connection. Multiple users on Microsoft’s community forums reported this fixed KB5066835 when every other method had failed.

Note: If the option is greyed out or doesn’t appear, it may not be available on your specific build. Continue to Fix 7.

Fix 7: Temporarily Disable Antivirus and Third-Party Security Software

Security software — including well-known products like Malwarebytes, Bitdefender, and even Windows Defender’s advanced features — can block update file writes.

1. Right-click your antivirus icon in the system tray
2. Choose “Disable” or “Pause protection” — for 15 minutes is enough
3. Try the update immediately while it’s paused
4. Re-enable your antivirus once done (whether it worked or not)

If this fixes it, add Windows Update as a trusted process/exception in your security software settings so this doesn’t happen again.

Fix 8: Perform a Clean Boot

If a background application or startup service is conflicting with the update installer, a clean boot isolates the problem.

1. Press Win + R, type msconfig, press Enter
2. Go to the Services tab
3. Check “Hide all Microsoft services” then click Disable all
4. Go to the Startup tab → click Open Task Manager
5. Disable every startup item in Task Manager
6. Close Task Manager, click OK in msconfig
7. Restart your PC
8. Attempt the update

If it succeeds in clean boot, re-enable services in small groups to identify which one was causing the conflict.

Advanced Fix: In-Place Upgrade with Media Creation Tool

If you’ve worked through every fix above and the update still fails, the most reliable last resort is an in-place upgrade — it reinstalls Windows 11 fresh while keeping all your files, apps, and settings intact.

1. Download the Windows 11 Media Creation Tool from Microsoft’s official site (search “Windows 11 download” → microsoft.com)
2. Run it and choose “Upgrade this PC now”
3. When prompted, select “Keep personal files and apps”
4. Follow the installer — it will take 30–60 minutes

After completion, your Windows version will be fully up to date. This approach works even in cases where the update infrastructure itself is broken at a deeper level.

Why Does This Keep Happening? (The Real Reason)

It’s worth understanding the root cause — because KB5066835 was unusually problematic compared to typical monthly updates.

The update included a significant security change: it strengthened how Windows handles RSA cryptography by moving operations from the older CAPI interface to the newer CNG Key Storage API. This change affected:

• Smart card authentication systems
• Some enterprise security configurations
• USB device recognition in the Windows Recovery Environment

Microsoft themselves acknowledged a known bug where, after installing KB5066835, USB keyboards and mice stop working in the Windows Recovery Environment. They issued a fix for this in subsequent updates.

The broader installation failures — particularly 0x800F0983 — were tied to the update needing more space in the EFI partition than older cumulative updates required, thanks to these additional components.

Understanding this also tells you something useful: if your system is perfectly stable and you’re not seeing any issues beyond the failed update, the 0x800F0983 error is almost certainly the EFI partition space issue (Fix 5), not a sign that anything is broken with your PC.

How to Prevent Windows Update Failures in the Future

Once you’re up to date, a few habits will keep things running smoothly:

• Set updates to install automatically — don’t defer them for months. The longer you wait, the more changes stack up and the higher the chance of conflicts
• Keep at least 15 GB free on your C: drive at all times — update installations are temporary and need staging space
• Skip third-party “registry cleaner” tools — apps like CCleaner and similar utilities regularly delete files that Windows Update needs, causing exactly the errors we’ve seen here
• Create a restore point monthly — search “Create a restore point” in Windows search, click your C: drive, then “Create”. Takes 2 minutes and gives you a safety net before any future update
• Check Microsoft’s Health Dashboard before updating — at aka.ms/WindowsReleaseHealth Microsoft lists known issues with each update before you install it

Final Thoughts

Windows updates are vital. But errors like KB5066835 or KB5066128 not installing can be annoying. Thankfully, there are many ways to fix them. Start with simple steps like running the troubleshooter. If needed, go deeper with manual downloads or DISM.

Stay patient. Try each method. Your system will be updated soon.

If you found this guide helpful, share it with others. Let’s help everyone keep their Windows running smoothly.

Frequently Asked Questions (FAQ)

Why does KB5066835 fail at 100% and roll back?

This is most commonly the 0x800F0983 error caused by insufficient EFI partition space. The update downloads fully but can’t write its boot files. Follow Fix 5 above.

Is it safe to skip KB5066835 indefinitely?

No. It patches real security vulnerabilities that are actively being exploited. If you can’t install it through Windows Update, use the manual catalog download (Fix 4) or the Media Creation Tool (Advanced Fix).

Will the manual catalog install give me the same update as Windows Update?

Yes — it’s the identical package. The .msu file from the Microsoft Update Catalog is the same file Windows Update downloads.

My EFI partition is only 100 MB. Is that normal?

Yes — 100 MB is the default size for most PCs. The issue isn’t the total size but how full it is. Clearing the font files (Fix 5) frees up enough space without needing to resize the partition.

I fixed KB5066835 but KB5066128 still won’t install. What now?

Run the Update Troubleshooter again after restarting. KB5066128 (the .NET Framework update) often installs cleanly once the system file integrity has been restored by the DISM + SFC steps.

What if the “Fix problems using Windows Update” option isn’t in my Settings?

This feature was added in Windows 11 24H2. If you’re on an older build, it won’t appear. Use the Media Creation Tool method instead.

I tried everything and my PC still can’t update. Now what?

Visit support.microsoft.com and use the Get Help app (search “Get Help” in Windows). Microsoft support agents can access your system remotely and run deeper diagnostics than any guide can cover.

Still Stuck? Here’s Your Quick Decision Tree

• Error 0x80240069 or update won’t download? → Fix 4 (Manual Catalog)
• Error 0x800F0983 or 0x800F0922? → Fix 5 (EFI partition)
• Error 0x800F0991? → Fix 3 (DISM + SFC) then Fix 4
• Update downloads fine but fails at install? → Fix 7 (antivirus) or Fix 8 (clean boot)
• Everything tried, nothing works? → Advanced Fix (Media Creation Tool)

Keep Your Windows Healthy — What to Read Next

If you found this guide useful, these will help you stay on top of your Windows setup:

• Windows 10 support ended October 2025 — find out what that actually means for your security → [Is Windows 10 Still Safe to Use?]
• What is Microsoft actually planning next? → [Is Windows 12 Coming or Just a Myth?]
• How to keep running Windows 10 safely after EOL → [How to Keep Using Windows 10 Safely After Support Ends]

Did This Fix Your Problem?

If one of the fixes above resolved your KB5066835 or KB5066128 install error, drop a comment below and tell us which one worked — it helps other readers know where to start.

If you’re still hitting a wall, describe your exact error code and what you’ve tried. We read every comment and will help you work through it.

And if this guide saved you an hour of frustration, share it — there’s someone else out there right now watching that same progress bar roll back to 0%.

Last updated: March 2026 | Applies to: Windows 11 24H2, Windows 11 25H2 Sources: Microsoft Learn Release Health Dashboard, Microsoft Q&A Community, Windows Update Catalog

Related posts:

Future of 3D printing healthcare applications Vahana Project: Airbus taxis that can go by road, and also fly The Best Final Cut Pro Alternatives For Windows How to Remove Amazon Assistant Virus? Is it a threat?