What Is Happening With KB5132061?
It was supposed to be a routine Tuesday night. You click restart, Windows begins installing its monthly security update, and the progress bar climbs — 30 percent, 60 percent, 71 percent — then it simply stops. The screen flickers, the machine reboots, and the same update is waiting for you again, as if nothing ever happened.
For a growing number of Windows 11 users this week, that loop is real. And Microsoft has now admitted it.
The update in question is KB5132061, the November 2026 security update for Windows 11. It arrived on Tuesday, November 10, as part of Patch Tuesday, Microsoft’s monthly security release. It covers Windows 11 versions 26H2 and 25H2 in all editions, plus version 24H2 for Enterprise and Education users, taking them to builds 26300.9974, 26200.9974 and 26100.9974.
Almost immediately, reports started piling up. Users said the update would download, begin installing, then freeze midway and fail. Some saw their machines try again and again, each attempt ending the same way.
On Wednesday, November 12, Microsoft confirmed the problem. According to BleepingComputer, which first reported the confirmation, Microsoft added a known-issue entry to the update’s support page. “When attempting to install the November 2026 Windows security update, some devices might be unable to complete the installation,” the company said. “Affected devices might repeatedly attempt to install the update or display error code 0x80070306, 0x800f0989, or 0x800f0993.”
That confirmation matters. A day earlier, the same support page had insisted Microsoft was “not currently aware of any issues with this update.” That line is now gone.
Which Windows 11 PCs Are Affected?
The good news is that most Windows 11 users are not affected at all. Microsoft says the problem hits “a limited number of devices” — specifically, machines that installed the October 2026 non-security preview update, KB5127936.
If your PC never installed that October preview, you are in the clear. Microsoft was explicit on this point: “Devices that did not install the October 2026 non-security preview update are not affected.”
That detail explains the pattern of the reports. Optional preview updates are early releases that Microsoft ships to users who choose to install them ahead of the monthly security patch. In this case, something in the October preview appears to clash with the November security update, leaving the installer unable to finish its work.
Microsoft has not said how many devices are affected, and it has not given a root cause beyond the link to the October preview. For now, the company is treating it as a narrow problem with a narrow fix.
The Three Error Codes to Watch For
If your PC is one of the affected machines, the failure will usually announce itself with one of three error codes: 0x80070306, 0x800f0989 or 0x800f0993.
The first code, 0x80070306, generally points to an installation that could not complete its final steps. The other two, 0x800f0989 and 0x800f0993, are the ones users reported most often. They appear when Windows Update gets partway through the install, hits a problem it cannot resolve, and rolls the whole thing back.
You can check whether this is happening to you in Settings, under Windows Update and then Update history. If KB5132061 sits there with one of those three codes beside it, your machine is caught in the loop.
Microsoft’s Automatic Fix Is Already Rolling Out
Here is the part Microsoft wants every affected user to hear: you do not need to do anything.
The company says a repair began rolling out on Wednesday, November 11, at 10 a.m. Pacific Time. It runs automatically in the background on affected devices that are connected to the internet and using Windows Update. “All affected devices should be repaired in 24 to 48 hours starting from November 11, 2026, 10am PT,” Microsoft said in its service update.
That puts the repair window closing on Friday morning, November 13. Microsoft told IT administrators the same thing in plainer terms: the installation issues will resolve automatically for all affected customers by Friday morning, and end users do not need to take any action to receive the fix.
Once your PC receives the repair, Windows Update will automatically download and install KB5132061, the company says. No restart dance, no manual download, no settings to change.
There is one exception. If your device is still failing to install the update after the 48-hour window has passed, Microsoft says administrators should contact Microsoft Support. For home users, that means checking the update again after Friday and, if it still fails, reaching out through the Windows Help and Learning pages.
What You Can Do While You Wait
The official advice is simple: wait. The repair is server-side, which means it arrives on its own, and forcing the update to install will not help while the underlying clash is still there.
If you are impatient, there are a couple of options. The update can be downloaded manually from the Microsoft Update Catalog and installed by hand. Some users have also reported that temporarily disabling Windows Sandbox allowed the update to install, although that is a community workaround, not something Microsoft has recommended.
It is also worth remembering why this update matters. KB5132061 is not a cosmetic patch. It is the security update that closes the Outlook zero-day, CVE-2026-124194, which attackers were already exploiting before Patch Tuesday. That is why it is worth letting the update install once the repair lands, rather than pausing updates altogether.
A Rough Week for Microsoft
The failed update caps a difficult week for Microsoft. On the very same day KB5132061 shipped, the company was hit by a major Microsoft 365 outage that knocked out Outlook, Teams and Copilot for millions of users across 74 countries. That outage, tracked as incident EX1550543, was still dragging on days later, with Microsoft warning that its first round of fixes was “not taking as expected.”
The two problems are not connected. Microsoft has said nothing linking the outage to the security patch, and the causes are different: the outage is a cloud infrastructure failure, while the update problem is a clash between two Windows packages on individual PCs. But they share a week, and for users and IT teams, they arrived as a one-two punch.
And then there is the Patch Tuesday release itself. The November update fixed 1,093 vulnerabilities, as we covered in our Microsoft November Patch Tuesday report, including the exploited Outlook flaw and a Windows Search remote-code flaw rated 9.8 out of 10. It was one of the biggest patch releases of the year — and now, for some users, one of the hardest to actually install.
A Familiar Pattern
If this story feels familiar, that is because it is. Windows update installation failures have become a recurring feature of Microsoft’s year.
In March, the company had to pull a buggy Windows 11 preview update, KB5079391, after users hit 0x80073712 errors during installation. In May, it fixed installation failures and 0x800f0922 errors with the May security update, KB5089549. And in June, Microsoft warned that some devices upgraded to Windows 11 24H2 or 25H2 might see 0x80073712 or 0x800f0993 errors when installing the latest monthly updates.
Each time, the pattern is the same: a patch ships, a subset of machines cannot install it, Microsoft confirms the problem, and an automatic repair follows. The company has got better at the repair part. The recurring failures are the part it has not yet solved.
There is a lesson in that pattern for users, too. Optional preview updates are, by definition, unfinished software. Unless a preview fixes a problem you actually have, waiting for the monthly security release is usually the safer choice.
What Happens Next
The repair window closes on Friday morning. By then, Microsoft expects every affected device to have received the automatic fix and to have installed KB5132061 without any action from its owner.
For most users, the story will end there: a failed update, a quiet repair, and a PC that is finally up to date. For IT administrators, the week is a reminder to watch the known-issues pages before rolling a Patch Tuesday release out to a whole fleet.
And for Microsoft, the week is a reminder of something simpler. Shipping a security fix is only half the job. The other half is making sure it actually installs — on every machine, the first time, without a repair crew having to follow behind it.
