- Microsoft says the November 2026 Windows security update fails to install on some Windows 11 devices that installed the October preview update (KB5127936).
- Microsoft says repairs began rolling out November 11, 10am PT and take 24 to 48 hours. Devices without the preview update are not affected.
- IT leaders should check which machines took optional preview updates and ask whether early installs belong in their patch policy.
Some early adopters got stuck
Security updates are meant to be the boring part of IT. This week, one stalled on a specific group of machines. These were the ones that had taken an optional update early.
Microsoft has confirmed that the November 2026 Windows security update (KB5132061) fails to install on some Windows 11 devices. BleepingComputer reported the confirmation. It cited a Microsoft service update it had seen.
The lesson here is that the optional preview channel has a price. It gives a team early fixes. It also puts those machines on a different path from the rest of the fleet. That path can break when the next mandatory patch arrives.
What Microsoft says is happening
Microsoft says affected devices may try to install the update again and again. They may also show error code 0x80070306, 0x800f0989 or 0x800f0993. BleepingComputer reported that users saw the install lock up partway through.
Microsoft describes the scope as limited. In its words, the issue "affects a limited number of devices that installed the October 2026 non-security preview update (KB5127936)." Devices that did not install that preview are not affected.
Microsoft has not said how many devices are affected. The report gives no cause beyond the link to the October preview update.
How the update chain works
Windows ships fixes in two layers. On Patch Tuesday, Microsoft releases the monthly security update. Late in the month before, Microsoft releases an optional non-security preview update. The October one shipped October 28. The preview gives an early look at fixes that later join the monthly release.
Many organisations wait for the security update. Some install the preview early to get a fix sooner. Microsoft says some of those early machines are now failing to take the November update.
Microsoft has not disclosed why the failure happens. The sources describe the update sequence, not the fault inside it.
There is an irony here. Microsoft's release-health page says the update released October 28 (KB5127936) resolved a Remote Desktop failure. That failure hit non-admin users connecting to hosts with Administrator protection enabled. A team that installed the preview to fix that problem may now be seeing install errors. The sources do not confirm that overlap. The timing is worth checking.
The fix is automatic, but the gap is real
Microsoft's release-health page says the security update shipped November 10. The repair began rolling out from November 11, 10am PT. Microsoft says it takes 24 to 48 hours.
Microsoft told IT administrators that end users do not need to take any action. It said affected devices "should be repaired in 24 to 48 hours" and will then install the November update through Windows Update. It put the full fix by Friday morning.
Microsoft also asked admins who still see install problems after 48 hours to contact Microsoft Support.
That leaves a gap. An affected device goes without the November update from its release until its repair arrives. That can be roughly three days.
The source does not say which vulnerabilities the update covers for these devices. So the exposure cannot be sized from this report. The point is simple. A security update was delayed by a process the organisation did not control.
One incident, and some background
BleepingComputer notes that this is not Microsoft's first install problem this year. In March, Microsoft pulled a non-security preview update (KB5079391) after 0x80073712 errors. In May, it fixed failures with 0x800f0922 errors on the May security update (KB5089549).
A June warning followed. Microsoft cautioned that some devices upgraded to Windows 11 24H2 or 25H2 could see 0x80073712 or 0x800f0993 errors when installing monthly updates.
These are earlier install problems, with some error codes that overlap and some that differ. The sources do not say whether they share a cause. They show that install problems appear in Microsoft's notes this year. They do not show a trend in how often updates fail. The sources give no rates.
What to ask your IT team
Ask which devices installed the October preview update (KB5127936). Ask whether that was a decision or a default. Ask how many of them have not yet received the November update.
Ask who watches Microsoft's release-health page. Ask who owns the call to contact Microsoft Support after the 48-hour window.
Finally, ask whether your patch policy treats previews as a deliberate choice for a pilot group. A pilot group that takes previews and the next monthly update first would limit how many machines meet this failure at once.
Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: BleepingComputer.
