Fix KB5073455 first by repairing the Windows component store with DISM, then run SFC, and only then reset Windows Update services if the install still fails. Microsoft supports DISM and System File Checker for repairing Windows image and system file corruption, which is exactly the type of damage that can block cumulative updates such as KB5073455 [source: Microsoft]. Do not start by deleting random folders or forcing the update manually. That often wastes time and can make the error harder to read.
TLDR: Run DISM /RestoreHealth, then sfc /scannow, restart, and try Windows Update again. If KB5073455 still fails, reset the Windows Update cache by stopping update services and renaming the SoftwareDistribution and Catroot2 folders. For example, on a typical office laptop with an SSD, the full repair process may take 20 to 45 minutes, with DISM usually taking the longest. If 8 out of 10 failed update cases are caused by cache damage or corrupted servicing files, these three steps target the most common causes first.
Contents
Before you start
Make sure you are signed in with an administrator account. Plug in the charger if this is a laptop. Restart once before doing anything else. It sounds basic, but pending update work can sit half-finished after a failed install.
Also check that you have enough free space. Windows 11 cumulative updates can fail when the system drive is tight. Keep at least 15 GB to 20 GB free on drive C. Honestly, it feels like Windows Update should explain this better instead of throwing a vague error code after ten minutes.
- Do not interrupt DISM or SFC. If the percentage looks stuck, wait.
- Create a restore point if the PC is used for work.
- Pause third-party antivirus only if it is known to interfere with updates.
- Disconnect unnecessary USB devices, especially external drives.
Step 1: Run DISM to repair the Windows image
DISM stands for Deployment Image Servicing and Management. In plain English, it checks and repairs the Windows component store. SFC depends on that store, so DISM should usually run first.
- Right-click the Start button.
- Select Terminal Admin or Windows PowerShell Admin.
- Approve the User Account Control prompt.
- Run the command below.
DISM /Online /Cleanup-Image /RestoreHealth
Let it finish. It may sit at 62.3% or another number for a while. That is annoying, but normal. On slower drives, expect the command to take longer than 20 minutes. If it completes with The restore operation completed successfully, move to SFC.
If DISM reports that source files could not be found, connect to the internet and run it again. If it still fails, mount a Windows 11 ISO that matches your installed version, then use it as a repair source. Most home users will not need that extra step.
Step 2: Run SFC to repair protected system files
After DISM completes, keep the same admin Terminal open and run:
sfc /scannow
SFC checks protected Windows files and replaces bad copies. You may see one of four common results:
- No integrity violations: System files look fine.
- Found corrupt files and repaired them: Good. Restart next.
- Found corrupt files but could not fix some: Restart and run SFC again.
- Windows Resource Protection could not perform the requested operation: Boot into Safe Mode and run SFC there.
After SFC finishes, restart the PC. Then go to Settings > Windows Update and click Check for updates. Try KB5073455 again before using reset scripts. The reset step is useful, but it is heavier.
Step 3: Reset Windows Update components
If KB5073455 still fails, the Windows Update cache may be broken. This is where reset scripts help. The goal is simple: stop update services, rename update cache folders, reset network update settings, and start the services again.
Use this only from an elevated Terminal. Copy the commands below into Notepad first if you want to review them. Save the file as Reset-WindowsUpdate.bat, right-click it, and choose Run as administrator.
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
netsh winsock reset
netsh winhttp reset proxy
net start msiserver
net start bits
net start cryptSvc
net start wuauserv
Restart after the script finishes. Windows will rebuild the renamed folders automatically. Your update history may look cleaner or shorter after this, but installed updates are not removed just because the cache was reset.
If the script shows access denied
Access denied usually means the Terminal was not opened as administrator, or a service did not stop cleanly. Reboot and try again. If it still fails, run the commands one at a time and check which line breaks.
For locked catroot2 folders, stop the Cryptographic Services again:
net stop cryptSvc
Then retry the rename command:
ren C:\Windows\System32\catroot2 catroot2.old
Do not delete catroot2 outright. Renaming is safer. It gives you a fallback if something acts strangely after the repair.
Step 4: Run Windows Update again
After the restart, open Settings > Windows Update. Click Check for updates. Let Windows download KB5073455 again from scratch. Do not run other installers at the same time.
If the update reaches 100% and then fails during reboot, check the error code. Common codes such as 0x800f081f, 0x80073712, or 0x80070002 point to damaged files, missing payloads, or cache problems. DISM, SFC, and the reset script are built to address those causes.
When to install KB5073455 manually
If Windows Update still fails after these repairs, try a manual install from the Microsoft Update Catalog. Search for KB5073455, then download the package that matches your system type, such as x64 or ARM64. You can check this under Settings > System > About.
Run the downloaded .msu file as administrator. If it says the update is not applicable, do not force it. That usually means the update does not match your Windows 11 build, edition, processor type, or installed servicing stack.
Check the repair logs if it still fails
At this point, stop guessing. Check the logs. DISM writes to:
C:\Windows\Logs\DISM\dism.log
SFC writes details into the CBS log:
C:\Windows\Logs\CBS\CBS.log
You do not need to understand every line. Search for terms like error, corrupt, failed, and the KB number. These clues help if you contact Microsoft Support, your IT team, or a repair technician.
Final checks that often fix stubborn failures
- Disable VPN temporarily. Some update downloads fail through filtered connections.
- Set the correct date, time, and region. Certificate checks can fail when the clock is wrong.
- Run Disk Cleanup. Remove temporary Windows Update files.
- Check drive health. A failing SSD can corrupt downloaded update files.
- Boot clean. Disable non-Microsoft startup items and retry the update.
If KB5073455 continues to fail after DISM, SFC, a Windows Update reset, and a manual install attempt, consider an in-place repair upgrade using the latest Windows 11 ISO. Choose the option to keep personal files and apps. This refreshes Windows without the pain of a full reinstall, and it often fixes servicing problems that normal update repair cannot touch.
The best order is still simple: DISM first, SFC second, Windows Update reset third. That order repairs the base image, repairs system files, and clears the update cache. It is the cleanest path before taking stronger actions.