KB5127648 Won't Install? Fix 0x800f0845 & Other Errors

You click Restart now on the October Windows 11 update, the PC sits on “Working on updates” for a while, and then you land back on the lock screen with the message Something didn’t go as planned. Undoing changes. Windows Update now lists KB5127648 as failed, often with a code like 0x800f0845 or 0x800f0922. It is annoying, because this is a security update you actually want installed.

This guide explains what KB5127648 is, what each error code usually points to, and the fixes that make sense, ordered from the quickest to the most thorough. It also covers what to check after the update installs, and what the update means if you still run Windows 11 24H2. Last updated: October 21, 2026.

Quick Answer

KB5127648 is Microsoft’s October 13, 2026 cumulative update for Windows 11 versions 24H2, 25H2 and 26H2. Some users report that it fails to install with errors 0x800f0845, 0x80070306, 0x800f0989 or 0x800f0922, or that it installs and then rolls back after a restart. At the time of writing, Microsoft has not published a dedicated fix for these install failures. The usual path that helps is this: restart, free up disk space and disconnect any VPN, run the Windows Update troubleshooter, clear the update cache, repair system files with DISM and SFC, and if it still fails, install the update by hand from the Microsoft Update Catalog. If your PC has been failing several monthly updates in a row, the repair steps matter more than the retries. For a wider look at stuck or failing updates, see our guide on Windows 11 updates that get stuck or fail to install.

Which Update Does Your PC Need?

Windows 11 has several versions, and each gets its own October update. Open Settings > System > About and check the Version line under Windows specifications, then match it below.

Windows 11 Version	October 2026 Update	Build After Install
24H2	KB5127648	26100.9711
25H2	KB5127648	26200.9711
26H2	KB5127648	26300.9711
23H2	KB5126653	22621.7652
26H1	KB5127646	28000.3231

If your build number already matches the last column, the update is installed and you can skip to the section on problems after installing. Microsoft lists the full details on its KB5127648 support page.

What Is Inside KB5127648?

It is worth knowing what you are trying to install, because it helps you decide how hard to push.

Security fixes: it belongs to a Patch Tuesday that, according to IT-Connect’s report, patched more than 1,400 vulnerabilities, a record number.
September preview features: it includes everything from the optional September 22 update KB5124010, such as automatic previews for downloaded PDFs in File Explorer and the option to remap the Copilot key.
Bug fixes: it fixes the black screen after sign-in on multi-user setups, crashes in apps that use AC-3 (Dolby Digital) audio, Always On VPN connection problems, printing failures with RAW or Generic Text Only drivers, mouse stutter in some games, and fingerprint sign-in failing after a full restart.
Support milestone: it is the last update for Windows 11 24H2 Home and Pro.

In short, it is not an update to skip casually, especially if you use Windows Hello fingerprint sign-in, print often, or play games on your PC.

What the Error Codes Mean

Microsoft has not documented a specific cause for the codes people are reporting on KB5127648. In general, they point to problems with the update components or the Windows servicing store, which is why the repair steps below target those. Use this table to decide where to start.

Error Code	What It Usually Points To	Start With
0x800f0845	Update components or servicing store problem	Fix 4, then Fix 5
0x80070306	Update install interrupted or damaged update files	Fix 4
0x800f0989	Servicing store or component problem	Fix 5
0x800f0922	Low disk space, a VPN, or a full System Reserved partition	Fix 2
0xC1900101	Driver conflict during the restart	Fix 7
0x80070002 or 0x8007000d	Corrupt update cache	Fix 4
0x80070057	Damaged system files	Fix 5
“Undoing changes” after restart	Any of the above, often drivers or space	Fix 2, then Fix 7

Why This Is Happening

1. A damaged Windows Update cache

Windows stores downloaded update files in a folder before installing them. If a download was cut short, the saved files can be incomplete, and every retry reuses the same broken files.

Clue: the update fails at the same point every time, or you see 0x80070306, 0x80070002 or 0x8007000d.

2. A damaged component store or system files

Windows keeps a store of system components that updates modify. If part of it is corrupt, new updates cannot be applied cleanly, and the failures tend to repeat month after month.

Clue: older updates, such as the August or September ones, also show as failed in your update history, often with the same code.

3. Not enough free space, a VPN, or a full system partition

An update needs room to unpack and a clean connection to Microsoft’s servers. A nearly full C: drive, an active VPN, or a very full System Reserved partition can stop it.

Clue: you see 0x800f0922, or the C: drive shows almost no free space in File Explorer.

4. A driver or hardware conflict during the restart

The most delicate part of an update happens while the PC restarts. If an old driver or an attached device interferes, Windows undoes the changes and boots back into the old version.

Clue: you see the “Undoing changes” screen, or the code 0xC1900101, and a dock, external drive or old graphics driver is connected.

5. Security software or system tools interfering

Third-party antivirus, disk cleaners and “optimizer” tools can lock files that the update needs.

Clue: the update works in a clean boot, or it started failing right after you installed a security or cleanup tool.

Fix 1: Note the Exact Error and Check Your Version

Open Settings > Windows Update > Update history.
Find KB5127648 under failed updates and write down the error code.
Open Settings > System > About and note your Windows version and build number.
Look at whether older updates also show as failed.

This takes two minutes and saves you from guessing. Many people lose time because the code on the failed entry is different from the one they remember from the restart screen.

Test: you know your version, your build number and the exact code, and you have picked the matching starting point from the table above.

Fix 2: Restart, Free Up Space and Disconnect Extras

Restart the PC once, then try Check for updates again.
Open Settings > System > Storage and free up space. Aim for at least 20 GB free on the C: drive to be safe.
Turn off any VPN, and pause any third-party antivirus for the install.
Unplug external drives, docks, printers and USB gadgets you do not need.
Plug a laptop into power and use a wired connection if you can.

This fixes more cases than people expect, especially 0x800f0922 and the “Undoing changes” loop.

Test: Windows Update downloads and installs without failing, or at least gets past the point where it failed before.

Fix 3: Run the Windows Update Troubleshooter

Open Settings > System > Troubleshoot > Other troubleshooters.
Click Run next to Windows Update.
Apply any fix it offers, then restart and check for updates again.

The troubleshooter will not repair deep corruption, but it resets some common settings and takes seconds to run.

Test: the troubleshooter reports that it fixed something, and KB5127648 now downloads.

Fix 4: Clear the Windows Update Cache

This is the most useful fix for 0x80070306, 0x80070002 and 0x8007000d, and it often helps with 0x800f0845 as well. It forces Windows to download fresh copies of the update files.

Type cmd in the Start search box, right-click Command Prompt and choose Run as administrator.
Stop the update services by running these four lines, one at a time:

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

Rename the two cache folders:

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

Start the services again:

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

Restart the PC, open Settings > Windows Update and click Check for updates.

Renaming is safer than deleting, because you can restore the old folders if something looks wrong. Windows rebuilds both folders on its own. Your update history may look empty for a short while, which is normal.

Test: the download restarts from zero and KB5127648 reaches 100% and installs.

Fix 5: Repair System Files with DISM and SFC

If the same codes keep returning, or older updates failed too, the Windows component store may be damaged. Two built-in tools repair it. Run them in an administrator Command Prompt, in this order.

DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Run the DISM line first and wait until you see The restore operation completed successfully. It can sit at a percentage for several minutes, so do not close the window.
Run sfc /scannow and wait for it to reach 100%.
Restart the PC and check for updates again.

If DISM reports an error, make sure you are connected to the internet, because it downloads clean files from Windows Update.

Test: DISM finishes successfully, SFC reports no integrity violations or says it repaired files, and the update now installs.

Fix 6: Install KB5127648 Manually from the Microsoft Update Catalog

When Windows Update keeps failing, the standalone installer often works, because it skips the download step that causes many errors.

Check your system type in Settings > System > About. Most PCs say 64-bit operating system, x64-based processor. Some say ARM.
Open the Microsoft Update Catalog and search for KB5127648.
Download the entry that matches your version (24H2, 25H2 or 26H2) and your system type.
Double-click the downloaded .msu file and follow the prompts.
Restart when asked.

If the installer says the update does not apply to your computer, you may already have it, or you picked the wrong version or architecture. Check the build number first.

Test: Settings > System > About shows build 26100.9711, 26200.9711 or 26300.9711, depending on your version.

Fix 7: Update Drivers and Try a Clean Boot

Open Device Manager and look for any device with a yellow warning icon. If you find one, see our guide on the yellow warning icon in Device Manager.
Update your graphics and network drivers from the PC maker’s website or the chip maker’s official page.
Press Win + R, type msconfig and press Enter. On the Services tab, tick Hide all Microsoft services, then click Disable all.
Restart, install the update, and then undo the change in msconfig so your normal services come back.

A clean boot removes third-party software from the equation. If the update installs in a clean boot, one of your background programs was the cause, and a security or system tool is the most likely suspect.

Test: the update completes during the clean boot, or the “Undoing changes” loop stops after the driver update.

Fix 8: Reinstall Windows 11 Without Losing Your Files

This is the heaviest option, so keep it for last. Windows can reinstall the version you already have, keeping your files and apps, and that often repairs whatever blocks updates.

Back up anything important first.
Open Settings > System > Recovery.
Next to Fix problems using Windows Update, click Reinstall now.
Wait for the process to finish. The PC will restart a few times.
Run Check for updates afterwards.

Reports say this is not a confirmed fix for the KB5127648 codes, but it is a reasonable last step before a full in-place upgrade using the Windows 11 Installation Assistant. If your drive uses BitLocker, make sure you have your recovery key saved first. Our guide on the BitLocker recovery loop after a Windows update explains why.

Test: the reinstall finishes, your files are intact, and KB5127648 installs on the next check.

Problems After KB5127648 Installs

Once the update is in, a few known issues can still show up. Microsoft’s release health pages list two that remain open after October 13, and both are marked Mitigated, which means a workaround exists but not a final fix. The third row in the table is based on user reports and has not been confirmed by Microsoft.

What You See	Who Is Affected	What To Do
USB headset or speaker shows Code 10 or no sound	USB Audio Class 1.0 devices	Use another output or the 2-channel workaround
Remote Desktop error 0xC000000D for non-admin users	Mostly managed work PCs with Administrator protection	IT can adjust the policy until Microsoft ships a fix
Xbox sign-in error 0x87dd0005	Reported by some users, not confirmed	Restart, sign out and back in, and watch for updates

The USB audio problem began with the September update, so skipping KB5127648 does not avoid it. If your headset is affected, our guide to fixing USB audio Code 10 on Windows 11 walks through the workarounds. A home PC with no USB audio gear and no Remote Desktop host role falls outside the two confirmed issues.

Still on Windows 11 24H2? Read This

KB5127648 is the final update for Windows 11 24H2 Home and Pro, which reached the end of updates on October 13, 2026. The PC keeps running, but it stops getting monthly security updates. Enterprise and Education editions of 24H2 stay supported until October 12, 2027.

If you see “24H2” under Settings > System > About, plan to move up:

25H2: supported for Home and Pro until October 2027.
26H2: started rolling out on September 29, 2026, and is supported until October 2028.

Both versions share the same platform as 24H2, so the upgrade is small and quick, and it does not need a clean install. Open Settings > Windows Update and look for the message offering Windows 11 version 26H2 or 25H2. Microsoft is rolling 26H2 out in phases, so it may not appear yet on every PC. If your cumulative updates keep failing, getting onto a newer version is worth trying, though it is not guaranteed to cure update errors.

Troubleshooting Table

What You See	Most Likely Cause	Start With
Fails with 0x800f0845	Update cache or component store	Fix 4
Fails with 0x80070306	Interrupted or damaged update files	Fix 4
Fails with 0x800f0989	Component store	Fix 5
Fails with 0x800f0922	Space, VPN or system partition	Fix 2
Rolls back after restart	Driver or device conflict	Fix 2 and Fix 7
Every Windows Update fails	Broader system corruption	Fix 5, then Fix 8
Windows Update will not work at all	Blocked or damaged update service	Fix 6

Should You Just Skip This Update?

For most people, no. KB5127648 carries a large batch of security fixes, and skipping it leaves known holes open. The one reason to hold off is if you rely on a specific feature that a known issue affects, and in that case it is the issue that matters, not this particular update. If you decide to pause, do it for a short time through Settings > Windows Update > Pause updates, then come back and fix the install problem properly.

Pro Tips

Install updates when you are not in a hurry, so you can leave the PC alone during the restart.
Keep at least 20 GB free on the C: drive at all times.
Note your build number before and after every update so you can tell what changed.
Create a restore point before a big update with Create a restore point in the Start menu.
Save your BitLocker recovery key somewhere safe before any major update.
If updates fail month after month, fix the root cause with DISM and SFC rather than retrying.

Common Mistakes to Avoid

Retrying the same update again and again. If the cache or component store is damaged, it will fail the same way each time.
Deleting random system folders. Rename the two cache folders as shown instead, so you can undo it.
Downloading update files from unofficial sites. Use only the Microsoft Update Catalog.
Ignoring low disk space. A nearly full C: drive causes many update failures.
Leaving a VPN or old docks connected. They are common causes of 0x800f0922 and rollbacks.
Skipping the backup before a repair install. A short backup is far cheaper than lost files.

FAQs

Why does KB5127648 fail to install on my PC?

Common reasons are a damaged update cache, a damaged component store, low disk space, a VPN, or a driver conflict during the restart. Users report errors such as 0x800f0845, 0x80070306, 0x800f0989 and 0x800f0922, and Microsoft has not published a dedicated fix for them yet.

What does error 0x800f0845 mean?

Microsoft has not documented a specific cause for it on this update. It generally points to a problem with update components or the servicing store, so clearing the update cache and running DISM and SFC are the best first steps.

How do I install KB5127648 manually?

Download the file that matches your Windows version and system type from the Microsoft Update Catalog, then double-click the .msu file and restart when asked. Check Settings > System > About afterwards to confirm the new build number.

Which Windows 11 versions get KB5127648?

Versions 24H2, 25H2 and 26H2. Windows 11 23H2 gets KB5126653, and 26H1 gets KB5127646.

Is it safe to skip KB5127648?

It is better not to. The update carries security fixes and several bug fixes. If it will not install, fix the underlying problem or use the manual install, instead of leaving the PC unpatched.

Why does Windows say “Something didn’t go as planned. Undoing changes”?

It means the update failed during the restart and Windows rolled back to the previous version. Free up disk space, disconnect external devices and any VPN, update drivers, and try again. A clean boot can help show whether other software is blocking it.

Does KB5127648 fix the USB audio Code 10 problem?

No. Microsoft still lists the USB Audio Class 1.0 issue as Mitigated after the October updates. The problem began with the September update, so skipping KB5127648 does not avoid it.

Do I need to upgrade from Windows 11 24H2?

If you use the Home or Pro edition, yes, because it stopped receiving security updates on October 13, 2026. Upgrading to 25H2 or 26H2 is quick, since they share the same platform as 24H2.

Windows 11 KB5127648 Won’t Install? How to Fix Errors 0x800f0845, 0x80070306 and 0x800f0922