Microsoft's support page for KB5132061, the November 10 cumulative update for Windows 11, lists an installation problem and marks it resolved as of November 16. If your PC has not offered you the update, or offered it and failed, that is the change worth knowing. Separately, Microsoft has acknowledged a printing bug in the November update that, in the coverage we found, had no fix yet.
The install failure, and who it hit
According to BleepingComputer on November 12, Microsoft said a limited number of Windows 11 devices might repeatedly fail to install the update, with error codes 0x80070306, 0x800f0989 or 0x800f0993. Microsoft tied it to devices that had installed the October 2026 optional preview update, KB5127936. A PC that skipped that preview update was not affected.
Microsoft said it would repair affected devices on its side, within 24 to 48 hours from 10am Pacific on November 11, after which Windows Update would download and install the security update by itself. No action from the user was described. The KB5132061 support page now marks the issue resolved on November 16.
Outlets describe the scope a little differently. The support page's own entry for this problem names 24H2 Enterprise and Education, while the coverage speaks of Windows 11 in general. The update itself applies to Windows 11 26H2 and 25H2 in all editions, and to 24H2 Enterprise and Education. If you run Home or Pro on 24H2, this is not your update; see our piece on 24H2 Home and Pro updates ending October 13.
What the update fixes
The same support page lists four fixes. One matters for a problem we covered earlier: the page says USB Audio Class 1.0 devices could show error code 10 in Device Manager, and that this is fixed in KB5132061. When we wrote about the AC-3 crash fix, that Code 10 problem was still open. If you have a USB headset or interface that vanished after an update, this build is the one Microsoft says addresses it. We have no report from someone with the hardware confirming it.
The page also lists a fix for adding an Active Directory published printer, which could fail with error 87 after the October update, a fix for Remote Desktop connections failing on a certificate mismatch, and a fix for HDMI or DisplayPort audio on certain AMD graphics cards on 24H2. Those last three are mostly an office or a specific-hardware matter.
The printing bug that is still open
On November 13, BleepingComputer reported that Microsoft acknowledged a different printing problem after the November security update or later ones. Printing might fail for documents that contain images whose height or width is zero at the selected print resolution. Microsoft describes these as images used for things like invisible watermarks or layout anchoring. The report says it mainly shows up when printing from Microsoft Word through the Windows GDI printing path, and may happen in other apps. It affects Windows 10 and later, not only Windows 11.
The report did not include a fix, a workaround or a date from Microsoft. The service alert it cites sits in the Microsoft 365 admin portal and needs an admin sign-in, so we could not read it ourselves. We did not find a later update on the issue; check the Windows release health page before assuming it is still open.
What to do on your own PC
If the update already installed and printing works, there is nothing to do. If a document prints blank or fails after November 10, the cause may be an invisible zero-size image in the file. That is our inference from Microsoft's description, not a step Microsoft has published. Uninstalling a security update to fix it would trade a printing problem for a security gap, and Microsoft has not suggested it in anything we read.
If the update shows a failed install, wait for the automatic repair first. The page marks that resolved, so a PC that still fails is a different case, and the order of steps in our Windows Update guide applies.
The update to keep an eye on is the printing one: Microsoft has acknowledged it but, in what we read, has not said when it will be fixed. For the checks that apply when an update refuses to install, start with Windows Update stuck or failing: what to try, in order.
Last updated November 18, 2026