Forum Discussion
KB5132061 failed to install 10 times with error code 0x80070306
My laptop is running Windows 11 25H2 Home Edition. I don't have the Windows Sandbox feature, and the update failed 11 times. This is the first time I've encountered this problem.
KB5132061 failed to install 10 times with error code 0x80070306. Although the KB5132061 folder exists in C:\Windows\WinSxS and I didn't touch anything, the Event Viewer says it was successfully updated.
It kept retrying automatically. I didn't click reinstall, so I had no choice but to delete the $WinREAgent folder.
I used the following steps:
sfc /scannow
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
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
After deleting SoftwareDistribution.old, the update history for KB5132061 is gone.
This is the first time I have ever encountered this error.
Updates were suspended yesterday.
My feedback report:
If you encounter this problem after the update, please come here to second my opinion and provide feedback.
2 Replies
You have conflicting evidence: repeated 0x80070306 failures, a success event and files present in WinSxS. A component folder alone does not establish that the cumulative update completed. First record winver: Microsoft lists KB5132061 as builds 26300.9974, 26200.9974 or 26100.9974, depending on Windows version. In elevated PowerShell, run Get-WindowsPackage -Online and inspect the relevant servicing package’s state; distinguish Installed from Staged or InstallPending. An empty update history after cache cleanup is not a substitute for checking the installed build and package state. Before deleting more folders, preserve CBS and Windows Update logs and correlate the latest failure timestamp with the exact package being processed. Also check the release note’s prerequisites for your Windows version before another manual installation. I cannot identify the cause from 0x80070306 alone. Please add your Windows version, current build and package-state result to your existing Feedback Hub report, with sensitive log information removed.
- sheratonSteel Contributor
I have no contradiction. The "Patch Tuesday" update in November 2026 failed at 99% and there was no progress even after reinstalling.