Known issues — All products

Fix addresses certain Windows licensing failures with error 0x80041008

Some organizations can now complete certain Windows licensing and activation operations that previously failed. The fix mainly helps systems that use commands or automated processes to manage KMS activation and product keys.

SLMGR activation failures fixed for KMS and license tasks

Some Windows licensing and activation commands that failed with error 0x80041008 now work again. The fix mainly matters to organizations managing KMS activation, product keys, or Windows licenses.

Parallel SESSION_CONTEXT queries can return wrong results

Queries using SESSION_CONTEXT might return wrong results or create crash dump files when they run in parallel; this remains a known issue. CU11 includes 70 fixes for SQL Server 2025.

Replication safeguards, SQL engine fixes, and new link tools

SQL Server 2022 CU28 adds replication and database safety checks, fixes a range of engine and integration issues, and adds tools for Azure SQL Managed Instance links. Queries using SESSION_CONTEXT in parallel plans might still return wrong results or cause access violations.

Remote Desktop and USB audio fixes; NTLM signing strengthened

Remote Desktop connections and some USB audio devices get fixes, while NTLM signing is enabled by default for more connections. The update also closes a publicly disclosed Brotli decoder flaw.

NTLM signing defaults strengthened; Exchange mail issues remain

NTLM clients now offer message signing by default for non-anonymous connections, helping limit relay attacks. Some on-premises Exchange servers might still have email access or delivery problems.

Critical Windows Search remote-code flaw patched

A critical Windows Search flaw and other serious security bugs get fixes, alongside Exchange, printer, and Remote Desktop repairs. Some Exchange and WSUS problems remain open.

Recovery monitoring queries can crash the database engine

Queries against `sys.dm_exec_requests` might raise an access violation while a database is recovering. The release also fixes security flaws across SQL Server components.

Recovery-time queries may trigger access violations

Database monitoring queries during recovery might cause an access violation and create a dump file. The security update also fixes vulnerabilities; avoid those queries or use trace flag 4696 as a mitigation.

File Explorer gains a customizable menu; recovery adds cloud rebuild

File Explorer gets a faster, customizable right-click menu, and Windows adds Cloud rebuild for recovery. The preview also fixes Remote Desktop failures for some non-admin users.

DPAPI prompt warning and new touchpad gestures

A warning flags the planned April 2027 retirement of prompt-based DPAPI protection. New touchpad gestures, Emoji 17.0, and other Windows features also arrive in this optional preview.

Offline devices receive updated trusted root certificates

Devices that miss automatic certificate trust updates get an updated trusted-root payload. The package also updates AI components and improves update installation reliability.

Offline devices get updated trusted certificates

Devices that cannot reach Microsoft’s certificate service get updated trusted certificate data. Support for this edition ended October 13, 2026.

Offline servers get updated trusted root certificates

Devices that cannot reach Microsoft's certificate-update service get an updated trusted root certificate payload. Hotpatch-enrolled devices that install this update will not receive hotpatch updates until after they install the January 2027 baseline.

Root certificates updated for isolated servers; Exchange mail can fail

An updated trusted root certificate list helps servers that cannot reach Microsoft's certificate service. Some on-premises Exchange servers might also have trouble with sign-in and mail delivery.

Recovery checks can trigger access violations

Queries against `sys.dm_exec_requests` during database recovery can trigger access violations and dump files. CU10 also leaves open an issue where parallel `SESSION_CONTEXT` queries can return wrong results.

Backup and PolyBase flaws fixed; recovery queries can crash

Security fixes cover SQL Server components used for backup, PolyBase, and replication. Queries during database recovery can still trigger an access violation; a trace-flag mitigation is available.

23 SQL vulnerabilities addressed; MSDASQL linked queries still fail

Addresses 23 SQL Server vulnerabilities, including 22 rated Important. Linked server queries using MSDASQL can still fail with error 7416 in some configurations.

Recovery queries may raise access violations; security flaws fixed

Security fixes cover SQL Server components. Queries against `sys.dm_exec_requests` during database recovery might raise an access violation and create a dump file.

PolyBase security flaws addressed; linked server queries can fail

Fixes 22 Important SQL Server vulnerabilities. Linked server queries using MSDASQL and a provider string might fail with error 7416.

Database Engine vulnerabilities fixed; MSDASQL queries can fail

Fixes 21 vulnerabilities in SQL Server 2019. Linked-server queries using MSDASQL with a provider string can fail with error 7416.