This is an early report. Microsoft is still rolling out the repair for the first issue and has not yet released the fix for the second. We wanted to get the word out now, and we will update this page as Microsoft updates its guidance.
What to do
- Windows 11 devices that installed the October preview update, KB5127936, may fail to install the November update, KB5132061. Microsoft says devices connected to the internet and using Windows Update in Settings should be repaired automatically within 24 to 48 hours of November 11, 10am PT. That window ends Friday, November 13, at 10am PT; check for devices still failing after that.
- If you run SQL Server linked servers to Oracle, PostgreSQL or other databases through OLE DB, watch for open connections building up. Microsoft says an out-of-band fix (an update released outside the monthly schedule) is coming in the next few days, and Microsoft Support for business has a mitigation now.
1. The November update might fail to install on some Windows 11 devices
Microsoft's support article for KB5132061, the November 10 security update for Windows 11 versions 24H2, 25H2 and 26H2, now lists a known issue. Microsoft says some devices "might be unable to complete the installation. Affected devices might repeatedly attempt to install the update or display error code 0x80070306, 0x800f0989, or 0x800f0993."
Which devices
BleepingComputer reports that Microsoft told administrators in a service update: "This issue affects a limited number of devices that installed the October 2026 non-security preview update (KB5127936). Devices that did not install the October 2026 non-security preview update are not affected." BleepingComputer says it saw that service update. The sentence does not appear in Microsoft's public support article, so BleepingComputer is our source for it.
Microsoft's update history lists the October preview, KB5127936, for Windows 11 versions 25H2 and 26H2 (builds 26200.9818 and 26300.9818). Microsoft's article also lists the known issue in its section for Windows 11 version 24H2, which covers Enterprise and Education editions only. Microsoft's update history does not list KB5127936 for 24H2, and Microsoft has not said whether 24H2 devices are affected.
What admins are seeing
Windows Latest reports that in its tests the update reached 99% before it failed, and that retrying made no progress. Its readers described the same error codes, including failures on four PCs and on two virtual machines. BetaNews also covered Microsoft's confirmation. Windows Latest also suggests a workaround of its own. Microsoft has not published one, so we do not repeat it here.
The repair
Microsoft says the repair runs automatically on affected devices connected to the internet and using Windows Update in Settings: "No manual action from end-users is required to receive the repair. All affected devices should be repaired in 24 to 48 hours starting from November 11, 2026, 10am PT. Once your device receives the repair, it will automatically download and install the November 2026 security update via Windows Update."
Microsoft's article does not say how the repair reaches devices updated through WSUS or other managed deployment tools. For devices still failing after 48 hours, Microsoft says to "use Windows help and learning or contact Microsoft Support."
Senserva tracking pages: KB5132061 (the November update) and KB5127936 (the October preview).
2. SQL Server linked server connections might remain open
Microsoft confirmed this issue on its Windows release health dashboard on November 11. Microsoft says that after the Windows updates released October 13, 2026, and later are installed on server devices, "connections created by SQL Server linked server queries might remain open after the queries complete."
Microsoft says: "This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected." Microsoft says the open connections can slow or degrade server performance over time, and that administrators might see a growing number of open connections to external databases after the linked server queries have finished.
Affected platforms, per Microsoft
- Server: Windows Server 2025, Windows Server 2022, Windows Server version 1809, Windows Server 2016, Windows Server 2012 R2 and Windows Server 2012.
- Client: Windows 11 versions 26H2, 26H1, 25H2, 24H2 and 23H2, Windows 10 version 1809 and Windows 10 Enterprise LTSC 2019. Microsoft added version 26H2 on its 26H2 release health page on November 12; its other release health pages had not been updated when we checked.
Microsoft describes the issue on server devices and also lists these client versions. Microsoft says the issue applies to updates released October 13, 2026, "and later", and its status is still Confirmed. The November 10 updates are in that range.
Workarounds and the fix, per Microsoft
- Closing idle connections, or restarting the SQL service, relieves the load for a while. Microsoft warns these steps "can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time."
- "A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business."
- "We will address this issue with an out-of-band update that will be released in the next few days."
BleepingComputer and The Register also reported the issue.
Senserva tracking pages for the October 13 updates Microsoft names: KB5126646 (Windows Server 2025), KB5126655 (Windows Server 2022) and KB5127648 (Windows 11 24H2, 25H2 and 26H2).
Sources
- Microsoft: KB5132061 support article, and Windows release health for Windows Server 2025
- BleepingComputer: installation issues and SQL Server performance issues
- Windows Latest: KB5132061 installation errors
- BetaNews: KB5132061 installation may fail
- The Register: SQL Server linked server connections
Senserva Watch tracks and shares this information; Microsoft is the source. Prepared with Senserva Trustworthy AI, reviewed by a person, and checked against Microsoft's published data. Join Senserva Watch for alerts like this by email. The sources behind our trackers, and their terms, are on our Data sources & thanks page.