A Windows release health dashboard notification released Wednesday confirmed that patches distributed since October 2026 Patch Tuesday are responsible for SQL Server performance degradation and stability problems. The root cause stems from server queries maintaining open connections even after execution finishes, with these idle connections accumulating and consuming resources over time.
Microsoft stated that "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."

According to Microsoft, "In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running."
The company noted that system administrators have temporary options available: manually terminating orphaned connections or restarting the SQL service can provide short-term relief from performance and stability problems. However, these workarounds carry risks—service restarts can terminate active queries, and the underlying issue will resurface after some time since the root cause remains unaddressed.
Both client platforms (Windows 10 and Windows 11) and server platforms (Windows Server 2012 and later) experience this defect. Microsoft committed to releasing an out-of-band update within the next few days to permanently resolve the issue. Until the fix becomes available, IT administrators can contact Microsoft Support for Business to obtain a mitigation strategy.
This represents the latest in a series of Windows-related SQL Server problems. In September, Microsoft released a temporary workaround for SQL Server crashes affecting certain Windows Server 2025 deployments caused by recent memory management modifications. That bug, which surfaces when the Lock Pages in Memory (LPIM) Windows policy is enabled, can trigger SQL Server crash dumps, unexpected service stops or restarts, database maintenance failures, memory corruption errors, and access violation exceptions displaying 0xC0000005 error codes.
Additionally, Microsoft confirmed yesterday that November 2026 security updates are failing to install on Windows 11 systems where the October preview update was previously applied. Affected systems display error codes 0x80070306, 0x800f0989, or 0x800f0993 during deployment attempts.