SQL Server 2022 Updates & Release Notes

This article describes Cumulative Update package 27 (CU27) for Microsoft SQL Server 2022. This update contains 42 fixes that were issued after the release of SQL Server 2022 Cumulative Update 26. It updates components in the following builds:

• SQL Server - Product version: 16.0.4295.3, file version: 2022.160.4295.3
• Analysis Services - Product version: 16.0.43.252, file version: 2022.160.43.252

Important

To help secure SQL Server on Windows, enable encryption with Extended Protection.

Known issues in this update

Incorrect behavior of SESSION_CONTEXT in parallel plans

Queries that use the built-in SESSION_CONTEXT function might return incorrect results or trigger access violation (AV) dump files when run in parallel query plans. This issue occurs because of the manner in which SESSION_CONTEXT interacts with parallel execution threads, particularly if the session is reset for reuse.
For more information, see the Known issues section in SESSION_CONTEXT.

Linked server queries that use MSDASQL fail with error 7416

Linked server queries that use the MSDASQL (OLE DB Provider for ODBC Drivers) provider and specify a provider string (@provstr) fail and return the following error message:

Msg 7416, Level 16
Access to the remote server is denied because no login-mapping exists.

A stricter connection validation check in the Database Engine can reject connections for certain linked server configurations that use the MSDASQL provider, even if earlier builds allowed those connections.
For more information and workarounds, see Linked server queries that use MSDASQL fail with error 7416.

Access violation when you query sys.dm_exec_requests during database recovery

Queries against sys.dm_exec_requests might raise an access violation and generate a dump file if they run while a database is still recovering. This issue can occur during a database RESTORE operation, during startup recovery, or before an availability group replica finishes coming online.

The SQL Server error log contains entries that resemble the following text:

The database '' is marked RESTORING and is in a state that does not allow recovery to be run.
***Stack Dump being sent to \SQLDump0215.txt
SqlDumpExceptionHandler: Process 77 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

BEGIN STACK DUMP:
07/30/26 07:37:23 spid 77

Exception Address = 0x7FFDED94970D
Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
Access Violation occurred reading address 00000000000000F0
Input Buffer bytes -
<dbo.sp_YourMonitoringStoredProcedure>

This issue occurs because of a change that causes internal in-memory structures to be referenced before they're fully initialized.

Microsoft is aware of this issue and is investigating a fix. Until a fix is available, use one of the following mitigations:

• Enable trace flag 4696 to opt out of the code change that causes this issue. If you enable this trace flag, monitoring queries that query sys.dm_exec_requests or sys.sysprocesses on secondary replicas might return error 976 or error 978, as they did before you installed this update.
• Avoid queries against sys.dm_exec_requests for databases that are recovering.
• Uninstall this update.

Improvements and fixes included in this update

A downloadable Microsoft Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017. Download this Excel file now.

Note

Individual entries in the following table can be referenced directly through a bookmark. If you select any bug reference ID in the table, a bookmark tag is added to the URL by using the "#NNNNNNN" format. You can then share this URL with others so that they can jump directly to the desired fix in the table.

For more information about the bugs that are fixed and enhancements that are included in this cumulative update, see the following table.

[Table of bug fixes and improvements with bug reference IDs, descriptions, fix areas, components, and platforms]

How to obtain or download this or the latest cumulative update package

File information

Notes for this update

How to uninstall this update

References

• Announcing updates to the SQL Server Incremental Servicing Model (ISM)
• SQL Server Service Packs are no longer supported starting from SQL Server 2017
• Determine which version and edition of SQL Server Database Engine is running
• Servicing models for SQL Server
• Naming schema and Fix area descriptions for SQL Server software update packages
• Description of the standard terminology that is used to describe Microsoft software updates

Original source

This article describes Cumulative Update package 27 (CU27) for Microsoft SQL Server 2022. This update contains 41 fixes that were issued after the release of SQL Server 2022 Cumulative Update 26. It updates components in the following builds:

• SQL Server - Product version: 16.0.4295.3, file version: 2022.160.4295.3
• Analysis Services - Product version: 16.0.43.252, file version: 2022.160.43.252

Important

To help secure SQL Server on Windows, enable encryption with Extended Protection.

Known issues in this update

Incorrect behavior of SESSION_CONTEXT in parallel plans

Queries that use the built-in SESSION_CONTEXT function might return incorrect results or trigger access violation (AV) dump files when they're run in parallel query plans. This issue occurs because of the manner in which SESSION_CONTEXT interacts with parallel execution threads, particularly if the session is reset for reuse.

For more information, see the "Known issues" section in SESSION_CONTEXT.

Linked server queries that use MSDASQL fail with error 7416

Linked server queries that use the MSDASQL (OLE DB Provider for ODBC Drivers) provider and specify a provider string (@provstr) fail and return the following error message:

Msg 7416, Level 16
Access to the remote server is denied because no login-mapping exists.

A stricter connection validation check in the database engine can reject connections for certain linked server configurations that use the MSDASQL provider. This is true even if earlier builds allowed those connections.

For more information and workarounds, see Linked server queries that use MSDASQL fail with error 7416.

Access violation when you query sys.dm_exec_requests during database recovery

Queries against sys.dm_exec_requests might raise an access violation and generate a dump file if they run while a database is still recovering. This issue can occur during a database RESTORE operation, during startup recovery, or before an availability group replica finishes coming online.

When this issue occurs, the SQL Server error log contains entries that resemble the following text:

The database '' is marked RESTORING and is in a state that does not allow recovery to be run.
***Stack Dump being sent to \SQLDump0215.txt
SqlDumpExceptionHandler: Process 77 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

BEGIN STACK DUMP:
07/30/26 07:37:23 spid 77

Exception Address = 0x7FFDED94970D
Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
Access Violation occurred reading address 00000000000000F0
Input Buffer bytes -
<dbo.sp_YourMonitoringStoredProcedure>

This issue occurs because of a change that causes internal in-memory structures to be referenced before they're fully initialized.

Microsoft is aware of this issue and is investigating a fix. Until a fix is available, use one of the following mitigations:

• Enable trace flag 4696 to opt out of the code change that causes this issue. If you enable this trace flag, monitoring queries that query sys.dm_exec_requests or sys.sysprocesses on secondary replicas might return error 976 or error 978, as they did before you installed this update.
• Avoid queries against sys.dm_exec_requests for databases that are recovering.
• Uninstall this update.

Improvements and fixes included in this update

A downloadable Microsoft Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017. Download this Excel file now.

Note

Individual entries in the following table can be referenced directly through a bookmark. If you select any bug reference ID in the table, a bookmark tag is added to the URL by using the "#NNNNNNN" format. You can then share this URL with others so that they can jump directly to the desired fix in the table.

For more information about the bugs that are fixed and enhancements that are included in this cumulative update, see the following table.

[Table of bug fixes and improvements with bug reference IDs, descriptions, fix areas, components, and platforms]

How to obtain or download this or the latest cumulative update package

File information

Notes for this update

How to uninstall this update

References

Original source

This article describes Cumulative Update package 26 (CU26) for Microsoft SQL Server 2022. This update contains 12 fixes that were issued after the release of SQL Server 2022 Cumulative Update 25. It updates components in the following builds:

• SQL Server - Product version: 16.0.4265.3, file version: 2022.160.4265.3
• Analysis Services - Product version: 16.0.43.252, file version: 2022.160.43.252

Important

To help secure SQL Server on Windows, enable encryption with Extended Protection.

Known issues in this update

Incorrect behavior of SESSION_CONTEXT in parallel plans

Queries that use the built-in SESSION_CONTEXT function might return incorrect results or trigger access violation (AV) dump files when run in parallel query plans. This issue occurs because of the manner in which SESSION_CONTEXT interacts with parallel execution threads, particularly if the session is reset for reuse.

For more information, see the Known issues section in SESSION_CONTEXT.

Linked server queries that use MSDASQL fail with error 7416

Linked server queries that use the MSDASQL (OLE DB Provider for ODBC Drivers) provider and specify a provider string (@provstr) fail and return the following error message:

Msg 7416, Level 16
Access to the remote server is denied because no login-mapping exists.

A stricter connection validation check in the Database Engine can reject connections for certain linked server configurations that use the MSDASQL provider, even if earlier builds allowed those connections.

For more information and workarounds, see Linked server queries that use MSDASQL fail with error 7416.

Access violation when you query sys.dm_exec_requests during database recovery

Queries against sys.dm_exec_requests might raise an access violation and generate a dump file if they run while a database is still recovering. This issue can occur during a database RESTORE operation, during startup recovery, or before an availability group replica finishes coming online.

The SQL Server error log contains entries that resemble the following text:

The database '' is marked RESTORING and is in a state that does not allow recovery to be run.
***Stack Dump being sent to \SQLDump0215.txt
SqlDumpExceptionHandler: Process 77 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

BEGIN STACK DUMP:
  07/30/26 07:37:23 spid 77

Exception Address = 0x7FFDED94970D
Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
Access Violation occurred reading address 00000000000000F0
Input Buffer <size> bytes -
        <dbo.sp_YourMonitoringStoredProcedure>

This issue occurs because of a change that causes internal in-memory structures to be referenced before they're fully initialized.

Microsoft is aware of this issue and is investigating a fix. Until a fix is available, use one of the following mitigations:

• Enable trace flag 4696 to opt out of the code change that causes this issue. If you enable this trace flag, monitoring queries that query sys.dm_exec_requests or sys.sysprocesses on secondary replicas might return error 976 or error 978, as they did before you installed this update.
• Avoid queries against sys.dm_exec_requests for databases that are recovering.
• Uninstall this update.

Improvements and fixes included in this update

A downloadable Microsoft Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017. Download this Excel file now.

Note

Individual entries in the following table can be referenced directly through a bookmark. If you select any bug reference ID in the table, a bookmark tag is added to the URL by using the "#NNNNNNN" format. You can then share this URL with others so that they can jump directly to the desired fix in the table.

For more information about the bugs that are fixed and enhancements that are included in this cumulative update, see the following table.

[Table of bug fixes and descriptions omitted for brevity]

How to obtain or download this or the latest cumulative update package

File information

Notes for this update

How to uninstall this update

References

Original source

This article describes Cumulative Update package 26 (CU26) for Microsoft SQL Server 2022. This update contains 12 fixes that were issued after the release of SQL Server 2022 Cumulative Update 25. It updates components in the following builds:

• SQL Server - Product version: 16.0.4265.3, file version: 2022.160.4265.3
• Analysis Services - Product version: 16.0.43.252, file version: 2022.160.43.252

Important

To help secure SQL Server on Windows, enable encryption with Extended Protection.

Known issues in this update

Incorrect behavior of SESSION_CONTEXT in parallel plans

Queries that use the built-in SESSION_CONTEXT function might return incorrect results or trigger access violation (AV) dump files when they're run in parallel query plans. This issue occurs because of the manner in which SESSION_CONTEXT interacts with parallel execution threads, particularly if the session is reset for reuse.

For more information, see the "Known issues" section in SESSION_CONTEXT.

Linked server queries that use MSDASQL fail with error 7416

Linked server queries that use the MSDASQL (OLE DB Provider for ODBC Drivers) provider and specify a provider string (@provstr) fail and return the following error message:

Msg 7416, Level 16
Access to the remote server is denied because no login-mapping exists.

A stricter connection validation check in the Database Engine can reject connections for certain linked server configurations that use the MSDASQL provider, even if earlier builds allowed those connections.

For more information and workarounds, see Linked server queries that use MSDASQL fail with error 7416.

Improvements and fixes included in this update

A downloadable Microsoft Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017. Download this Excel file now.

Note

Individual entries in the following table can be referenced directly through a bookmark. If you select any bug reference ID in the table, a bookmark tag is added to the URL by using the "#NNNNNNN" format. You can then share this URL with others so that they can jump directly to the desired fix in the table.

For more information about the bugs that are fixed and enhancements that are included in this cumulative update, see the following table.

Bug Reference Description Fix area Component Platform 5132800 Adds more detailed error information to the Windows Server Failover Cluster log if the availability group resource DLL can't retrieve diagnostic column information. SQL Server Engine High Availability and Disaster Recovery Windows 5138995 Adds support for removing an IP address from an availability group listener by using the ALTER AVAILABILITY GROUP ... MODIFY LISTENER ... REMOVE IP command. SQL Server Engine High Availability and Disaster Recovery Windows 5196012 Fixes a SQL injection vulnerability in the sys.sp_MSforeachdb stored procedure that allows an authorized attacker to elevate privileges over a network. SQL Server Engine Management Services All 5197074 Fixes an issue in which an index rebuild maintenance plan stops responding because of a long-running query. SQL Server Engine Maintenance Plan All 5216517 Fixes an issue in which monitoring queries that use sys.dm_exec_requests or sys.sysprocesses intermittently fail and return error "976" or "978" on a secondary replica in an availability group. SQL Server Engine High Availability and Disaster Recovery Windows 5219564 Fixes an issue in the interpolation calculation of the new cardinality estimator for very large values that can cause an ALTER INDEX operation to choose a serial plan. SQL Server Engine Query Execution All 5240249 Removes the deprecated RSA32Lib cryptographic library as part of ongoing cryptography modernization. SQL Server Engine Universal Communication Stack Windows 5272424 Fixes an access violation that occurs when you run ALTER PARTITION FUNCTION ... SPLIT RANGE against a partition function that's used by a table that has an identity column that's also referenced by a clustered index on a schema-bound view. SQL Server Engine Programmability All 5285172 Fixes a nonyielding scheduler condition that can occur when SQL Server writes certain errors to the error log. SQL Server Engine Programmability All 5293216 Adjusts the sampling rate for incremental statistics if the last sampling rate was 100 percent and many new rows are inserted into the table. SQL Server Engine Query Execution All 5300009 Improves memory management during query compilation for columnstore indexes to reduce query compilation time. SQL Server Engine Methods to access stored data Windows 5347342 Fixes a nonyielding scheduler condition that can occur if sys.dm_db_index_operational_stats iterates through a large number of cached heaps or B-trees. SQL Server Engine Methods to access stored data All

How to obtain or download this or the latest cumulative update package

File information

Notes for this update

How to uninstall this update

References

• Announcing updates to the SQL Server Incremental Servicing Model (ISM)
• SQL Server Service Packs are no longer supported starting from SQL Server 2017
• Determine which version and edition of SQL Server Database Engine is running
• Servicing models for SQL Server
• Naming schema and Fix area descriptions for SQL Server software update packages
• Description of the standard terminology that is used to describe Microsoft software updates

Original source

This article describes Cumulative Update package 25 (CU25) for Microsoft SQL Server 2022. This update contains 12 fixes that were issued after the release of SQL Server 2022 Cumulative Update 24. It updates components in the following builds:

• SQL Server - Product version: 16.0.4255.1, file version: 2022.160.4255.1
• Analysis Services - Product version: 16.0.43.252, file version: 2022.160.43.252

Important

To help secure SQL Server on Windows, enable encryption with Extended Protection.

Known issues in this update

Incorrect behavior of SESSION_CONTEXT in parallel plans

Queries that use the built-in SESSION_CONTEXT function might return incorrect results or trigger access violation (AV) dump files when run in parallel query plans. This issue occurs because of the manner in which SESSION_CONTEXT interacts with parallel execution threads, particularly if the session is reset for reuse.

For more information, see the Known issues section in SESSION_CONTEXT.

Linked server queries that use MSDASQL fail with error 7416

Linked server queries that use the MSDASQL (OLE DB Provider for ODBC Drivers) provider and specify a provider string (@provstr) fail and return the following error message:

Msg 7416, Level 16
Access to the remote server is denied because no login-mapping exists.

A stricter connection validation check in the Database Engine can reject connections for certain linked server configurations that use the MSDASQL provider, even if earlier builds allowed those connections.

For more information and workarounds, see Linked server queries that use MSDASQL fail with error 7416.

Improvements and fixes included in this update

A downloadable Microsoft Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017. Download this Excel file now.

Note

Individual entries in the following table can be referenced directly through a bookmark. If you select any bug reference ID in the table, a bookmark tag is added to the URL by using the "#NNNNNNN" format. You can then share this URL with others so that they can jump directly to the desired fix in the table.

For more information about the bugs that are fixed and enhancements that are included in this cumulative update, see the following table.

Bug reference - Description - Fix area - Component - Platform

4954485 - Fixes an issue in Contained Availability Groups in which DatabaseMail sends email messages without attachments. - SQL Server Client Tools - Database Mail - All

4999187 - Fixes an issue in which permissions on stored procedures and other objects in msdb are lost during the SQL Server upgrade process. This issue causes users to lose granted permissions. - SQL Server Engine - Management Services - Windows

5028794 - Fixes an access violation error that occurs when querying sys.dm_xe_session_targets on SQL Server instances that are running on Windows Server 2025. - SQL Server Engine - SQL OS - Windows

5033534 - Fixes an issue in Contained Availability Group connections in which T-SQL allows only adding a database to the currently connected Contained Availability Group, and also causes additional restrictions for DBCreator roles. - SQL Server Engine - High Availability and Disaster Recovery - All

5034739 - Fixes a memory leak issue in which parallel execution of SHORTEST_PATH queries in Graph databases causes persistent OBJECTSTORE_SOSTASK growth. - SQL Server Engine - Query Optimizer - All

5090699 - Fixes an issue in which a self-assignment update on a small off-row XML column by having compression enabled causes XML data corruption and a subsequent transport-level error when selecting the data. - SQL Server Engine - Access Methods - All

5126699 - Fixes an issue in which using the Oracle ODBC driver together with the ODBC connector in SSIS packages might cause heap corruption and data loss. - Integration Services - Integration Services - All

5130873 - Fixes a heap corruption issue in the generic ODBC connector when using the Oracle ODBC driver. - Integration Services - Integration Services - All

5131000 - Fixes an XML External Entity (XXE) vulnerability in the Web Service Task by blocking the file:// protocol in WSDL service endpoints to prevent unauthorized file access and denial-of-service attacks. - Integration Services - Integration Services - Windows

5157137 - Fixes CPU starvation issues by adding yields at regular intervals during in-memory OLTP garbage collection scan of hash indexes. - SQL Server Engine - In-Memory OLTP - All

5208913 - Fixes an error that occurs when an online index operation runs concurrently with data manipulation language (DML) operations in a database that has Change Data Capture (CDC) enabled. - SQL Server Engine - Storage Engine - All

5213660 - Fixes a back-up cleanup issue on Linux that could cause SQL Server to stop responding when a network share becomes full or unreachable. - SQL Server Engine - Linux - Linux

How to obtain or download this or the latest cumulative update package

File information

Notes for this update

How to uninstall this update

References

• Announcing updates to the SQL Server Incremental Servicing Model (ISM)
• SQL Server Service Packs are no longer supported starting from SQL Server 2017
• Determine which version and edition of SQL Server Database Engine is running
• Servicing models for SQL Server
• Naming schema and Fix area descriptions for SQL Server software update packages
• Description of the standard terminology that is used to describe Microsoft software updates

Original source

This article describes Cumulative Update package 25 (CU25) for Microsoft SQL Server 2022. This update contains 11 fixes that were issued after the release of SQL Server 2022 Cumulative Update 24. It updates components in the following builds:

• SQL Server - Product version: 16.0.4255.1, file version: 2022.160.4255.1
• Analysis Services - Product version: 16.0.43.252, file version: 2022.160.43.252

Important

To help secure SQL Server on Windows, enable encryption with Extended Protection.

Known issues in this update

Incorrect behavior of SESSION_CONTEXT in parallel plans

Queries that use the built-in SESSION_CONTEXT function might return incorrect results or trigger access violation (AV) dump files when run in parallel query plans. This issue occurs because of the manner in which SESSION_CONTEXT interacts with parallel execution threads, particularly if the session is reset for reuse.

For more information, see the Known issues section in SESSION_CONTEXT.

Improvements and fixes included in this update

A downloadable Microsoft Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017. Download this Excel file now.

Note

Individual entries in the following table can be referenced directly through a bookmark. If you select any bug reference ID in the table, a bookmark tag is added to the URL by using the "#NNNNNNN" format. You can then share this URL with others so that they can jump directly to the desired fix in the table.

For more information about the bugs that are fixed and enhancements that are included in this cumulative update, see the following table.

Bug reference - Description - Fix area - Component - Platform

• 4954485 - Fixes an issue in Contained Availability Groups in which DatabaseMail sends email messages without attachments. - SQL Server Client Tools - Database Mail - All
• 4999187 - Fixes an issue in which permissions on stored procedures and other objects in msdb are lost during the SQL Server upgrade process. This issue causes users to lose granted permissions. - SQL Server Engine - Management Services - Windows
• 5028794 - Fixes an access violation error that occurs when querying sys.dm_xe_session_targets on SQL Server instances that are running on Windows Server 2025. - SQL Server Engine - SQL OS - Windows
• 5033534 - Fixes an issue in Contained Availability Group connections in which T-SQL allows only adding a database to the currently connected Contained Availability Group, and also causes additional restrictions for DBCreator roles. - SQL Server Engine - High Availability and Disaster Recovery - All
• 5034739 - Fixes a memory leak issue in which parallel execution of SHORTEST_PATH queries in Graph databases causes persistent OBJECTSTORE_SOSTASK growth. - SQL Server Engine - Query Optimizer - All
• 5090699 - Fixes an issue in which a self-assignment update on a small off-row XML column by having compression enabled causes XML data corruption and a subsequent transport-level error when selecting the data. - SQL Server Engine - Access Methods - All
• 5126699 - Fixes an issue in which using the Oracle ODBC driver together with the ODBC connector in SSIS packages might cause heap corruption and data loss. - Integration Services - Integration Services - All
• 5130873 - Fixes a heap corruption issue in the generic ODBC connector when using the Oracle ODBC driver. - Integration Services - Integration Services - All
• 5131000 - Fixes an XML External Entity (XXE) vulnerability in the Web Service Task by blocking the file:// protocol in WSDL service endpoints to prevent unauthorized file access and denial-of-service attacks. - Integration Services - Integration Services - Windows
• 5157137 - Fixes CPU starvation issues by adding yields at regular intervals during in-memory OLTP garbage collection scan of hash indexes. - SQL Server Engine - In-Memory OLTP - All
• 5213660 - Fixes a back-up cleanup issue on Linux that could cause SQL Server to stop responding when a network share becomes full or unreachable. - SQL Server Engine - Linux - Linux

Original source

This article describes Cumulative Update package 24 (CU24) for Microsoft SQL Server 2022. This update contains 14 fixes that were issued after the release of SQL Server 2022 Cumulative Update 23. It updates components in the following builds:

• SQL Server - Product version: 16.0.4245.2, file version: 2022.160.4245.2
• Analysis Services - Product version: 16.0.43.252, file version: 2022.160.43.252

Known issues in this update

Incorrect behavior of SESSION_CONTEXT in parallel plans

Queries that use the built-in SESSION_CONTEXT function might return incorrect results or trigger access violation (AV) dump files when run in parallel query plans. This issue occurs because of the manner in which SESSION_CONTEXT interacts with parallel execution threads, particularly if the session is reset for reuse.
For more information, see the Known issues section in SESSION_CONTEXT.

Linked server queries that use MSDASQL fail with error 7416

Linked server queries that use the MSDASQL (OLE DB Provider for ODBC Drivers) provider and specify a provider string (@provstr) fail and return the following error message:

Msg 7416, Level 16
Access to the remote server is denied because no login-mapping exists.

A stricter connection validation check in the Database Engine can reject connections for certain linked server configurations that use the MSDASQL provider, even if earlier builds allowed those connections.
For more information and workarounds, see Linked server queries that use MSDASQL fail with error 7416.

Availability group listener error 10013 in error log

If you configure a SQL Server availability group with a listener, when the SQL Server service starts or an availability group failover occurs, you might see errors in the SQL Server error log that indicate a problem with the listener object. The following example shows what these errors look like:

The Service Broker endpoint is in disabled or stopped state.
Error: 26075, Severity: 16, State: 1.
Failed to start a listener for virtual network name ''. Error: 10013.
The Service Broker endpoint is in disabled or stopped state.
Stopped listening on listener network name '' (VNN or DISTRIBUTED_NETWORK_NAME). No user action is required.
The Service Broker endpoint is in disabled or stopped state.
Error: 10800, Severity: 16, State: 1.
The listener for the WSFC resource '' failed to start, and returned error code 10013, 'An attempt was made to access a socket in a way forbidden by its access permissions. '. For more information about this error code, see "System Error Codes" in the Windows Development Documentation.
Error: 19452, Severity: 16, State: 1.
The availability group listener (network name) with Windows Server Failover Clustering resource ID '', DNS name '', port 1433 failed to start with a permanent error: 10013. Verify port numbers, DNS names and other related network configuration, then retry the operation.

Additionally, after you apply this update, if you create a new listener, you might see an error similar to this example:

Msg 19486, Level 16, State 1, Line 3
The configuration changes to the availability group listener were completed, but the TCP provider of the instance of SQL Server failed to listen on the specified port []. This TCP port is already in use. Reconfigure the availability group listener, specifying an available TCP port. For information about altering an availability group listener, see the "ALTER AVAILABILITY GROUP (Transact-SQL)" topic in SQL Server Books Online.

This update also causes SQL Server to try to open a TCP port that's already in use when it starts or when a listener is created. This only results in error messages being logged and doesn't affect functionality. Listener connections continue to work.
Microsoft is aware of this issue and is investigating a fix.

Improvements and fixes included in this update

A downloadable Microsoft Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017.
Download this Excel file now.

Note

Individual entries in the following table can be referenced directly through a bookmark. If you select any bug reference ID in the table, a bookmark tag is added to the URL by using the "#NNNNNNN" format. You can then share this URL with others so that they can jump directly to the desired fix in the table.
For more information about the bugs that are fixed and enhancements that are included in this cumulative update, see the following table.

[Table of bug fixes and descriptions omitted for brevity]

How to obtain or download this or the latest cumulative update package

File information

Notes for this update

How to uninstall this update

References

Original source

KB5080999 - Cumulative Update 24 for SQL Server 2022

Applies to: SQL Server 2022 on Windows, SQL Server 2022 on Linux

Release Date: March 12, 2026
Version: 16.0.4245.2

Summary

This article describes Cumulative Update package 24 (CU24) for Microsoft SQL Server 2022. This update contains 15 fixes that were issued after the release of SQL Server 2022 Cumulative Update 23. It updates components in the following builds:

• SQL Server - Product version: 16.0.4245.2, file version: 2022.160.4245.2
• Analysis Services - Product version: 16.0.43.252, file version: 2022.160.43.252

Known issues in this update

Incorrect behavior of SESSION_CONTEXT in parallel plans

Queries that use the built-in SESSION_CONTEXT function might return incorrect results or trigger access violation (AV) dump files when run in parallel query plans. This issue occurs because of the manner in which SESSION_CONTEXT interacts with parallel execution threads, particularly if the session is reset for reuse.

For more information, see the Known issues section in SESSION_CONTEXT.

Improvements and fixes included in this update

A downloadable Microsoft Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017. Download this Excel file now.

Note

Individual entries in the following table can be referenced directly through a bookmark. If you select any bug reference ID in the table, a bookmark tag is added to the URL by using the "#NNNNNNN" format. You can then share this URL with others so that they can jump directly to the desired fix in the table.

For more information about the bugs that are fixed and enhancements that are included in this cumulative update, see the following table.

Improvements and fixes included in this update (table)

• 4838719 — Fixes an issue in StripedVdiTests to improve test reliability and stability. — SQL Server Engine — Backup Restore — Windows
• 4868211 — Adds a new optional parameter, @multi_subnet_failover, to sp_adddistributor. — SQL Server Engine — Replication — All
• 4874339 — Fixes an issue that occurs when creating or restoring a database on a contained availability group connection. — SQL Server Engine — High Availability and Disaster Recovery — All
• 4911747 — Fixes an issue in the in-memory sort buffer calculation that causes an infinite loop when the required page count exceeds supported limits. — SQL Server Engine — Backup Restore — All
• 4917971 — Fixes a floating point exception that occurs when switching from a Hekaton to a non-Hekaton stack. This action causes query execution to break. — Hekaton — Query Processing — All
• 4931278 — Fixes an issue in which a sort operation on a rowset that's larger than four billion rows fails and generates an assertion error. — SQL Server Engine — Access Methods — All
• 4931830 — Fixes an issue in which the distributor is part of an availability group (AG) and uses case-sensitive (_CS) collation. The distribution agent incorrectly uses the AG primary replica name instead of the AG listener name. — SQL Server Engine — Replication — All
• 4953763 — Fixes an issue in which the configure-only replica of a Contained Availability Group cannot be connected after a restart because of a startup failure. — SQL Server Engine — High Availability and Disaster Recovery — All
• 4955136 — Fixes an issue that occurs when using a local monitor server for Log Shipping and Contained Availability Group after failover. — SQL Server Engine — High Availability and Disaster Recovery — All
• 4955493 — Fixes a typo in sys.dm_os_linux_disk_stats by correcting ios_in_progess to ios_in_progress. — SQL Connectivity — Linux — Linux
• 4976761 — Fixes an issue in which altering a disabled DDL trigger causes a memory access violation. — SQL Server Engine — Programmability — All
• 4984502 — Adds a configurable full-text search batch timeout by using sp_fulltext_service 'batch_timeout'. Specify a value between one minute and one hour, in milliseconds. By default, batches time out after 10 minutes if there are no progress updates. — SQL Server Engine — Search — All
• 5005885 — Addresses contention on security-related metadata tables by adding sysowners to frequently accessed metadata tables check. — SQL Server Engine — Security Infrastructure — All
• 5011606 — Adds support for symbolic links in the getattribute API. — SQL Server Engine — Linux — Linux
• 5011720 — Adds a configuration option to add Bulkadmin operations to the allowlist. — SQL Server Engine — Linux — Linux

How to obtain or download this or the latest cumulative update package

File information

Notes for this update

Prerequisites

Restart information

Registry information

Important notices

Hybrid environment deployment

Language support

Components (features) updated

Support for this update

How to uninstall this update

• How to uninstall this update on Windows
• How to uninstall this update on Linux

References

• Announcing updates to the SQL Server Incremental Servicing Model (ISM)
• SQL Server Service Packs are no longer supported starting from SQL Server 2017
• Determine which version and edition of SQL Server Database Engine is running
• Servicing models for SQL Server
• Naming schema and Fix area descriptions for SQL Server software update packages
• Description of the standard terminology that is used to describe Microsoft software updates

Original source

This article describes Cumulative Update package 23 (CU23) for Microsoft SQL Server 2022. This update contains 15 fixes that were issued after the release of SQL Server 2022 Cumulative Update 22. It updates components in the following builds:

• SQL Server - Product version: 16.0.4236.2, file version: 2022.160.4236.2
• Analysis Services - Product version: 16.0.43.252, file version: 2022.160.43.252

Important

The initial release of this cumulative update (KB5074819), released on January 15, 2026, contained an issue that caused Database Mail to stop working. You might also see the following error message:

Could not load file or assembly 'Microsoft.SqlServer.DatabaseMail.XEvents, Version=17.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.

This issue affects SQL Server product version 16.0.4235.2 and file version 2022.160.4235.2.

This issue is resolved in the current version of this cumulative update (KB5078297).

If you downloaded the initial release of this update, don't install it. Download and install the current version instead.

If you already installed the initial release, uninstall it or install the current version on top of the initial CU23 release (KB5074819) to restore Database Mail functionality.

Future cumulative updates also contain the fix for this issue. You can install them regardless of which version of this cumulative update is currently installed.

Email messages queued through Database Mail while the initial release was installed aren't automatically resent when you uninstall it or install a cumulative update that contains the fix.

Known issues in this update

Incorrect behavior of SESSION_CONTEXT in parallel plans

Queries that use the built-in SESSION_CONTEXT function might return incorrect results or trigger access violation (AV) dump files when run in parallel query plans. This issue occurs because of the manner in which SESSION_CONTEXT interacts with parallel execution threads, particularly if the session is reset for reuse.

For more information, see the Known issues section in SESSION_CONTEXT.

Improvements and fixes included in this update

A downloadable Microsoft Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017. Download this Excel file now.

Note

Individual entries in the following table can be referenced directly through a bookmark. If you select any bug reference ID in the table, a bookmark tag is added to the URL by using the "#NNNNNNN" format. You can then share this URL with others so that they can jump directly to the desired fix in the table.

For more information about the bugs that are fixed and enhancements that are included in this cumulative update, see the following table.

[Table of bug fixes and descriptions omitted for brevity]

How to obtain or download this or the latest cumulative update package

[Sections on how to obtain or download the update]

File information

[File hash and package file information]

Notes for this update

[Prerequisites, restart information, registry information, important notices, hybrid environment deployment, language support, components updated, support for this update]

How to uninstall this update

[Instructions for uninstalling on Windows and Linux]

References

• Announcing updates to the SQL Server Incremental Servicing Model (ISM)
• SQL Server Service Packs are no longer supported starting from SQL Server 2017
• Determine which version and edition of SQL Server Database Engine is running
• Servicing models for SQL Server
• Naming schema and Fix area descriptions for SQL Server software update packages
• Description of the standard terminology that is used to describe Microsoft software updates

Original source

Release notes for SQL Server 2022 CU23

This article describes Cumulative Update package 23 (CU23) for Microsoft SQL Server 2022. This update contains 15 fixes that were issued after the release of SQL Server 2022 Cumulative Update 22. It updates components in the following builds:

• SQL Server - Product version: 16.0.4236.2, file version: 2022.160.4236.2
• Analysis Services - Product version: 16.0.43.252, file version: 2022.160.43.252

Important

The initial release of this cumulative update (KB5074819), released on January 15, 2026, contained an issue that caused Database Mail to stop working. You might also see the following error message:
Could not load file or assembly 'Microsoft.SqlServer.DatabaseMail.XEvents, Version=17.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
This issue affects SQL Server product version 16.0.4235.2 and file version 2022.160.4235.2.
This issue is resolved in the current version of this cumulative update (KB5078297).
If you downloaded the initial release of this update, don't install it. Download and install the current version instead.
If you already installed the initial release, uninstall it or install the current version to restore Database Mail functionality.
Future cumulative updates also contain the fix for this issue. You can install them regardless of which version of this cumulative update is currently installed.
Email messages queued through Database Mail while the initial release was installed aren't automatically resent when you uninstall it or install a cumulative update that contains the fix.

Known issues in this update

Incorrect behavior of SESSION_CONTEXT in parallel plans
Queries that use the built-in SESSION_CONTEXT function might return incorrect results or trigger access violation (AV) dump files when run in parallel query plans. This issue occurs because of the manner in which SESSION_CONTEXT interacts with parallel execution threads, particularly if the session is reset for reuse.
For more information, see the Known issues section in SESSION_CONTEXT.

Improvements and fixes included in this update

A downloadable Microsoft Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017. Download this Excel file now.

Note
Individual entries in the following table can be referenced directly through a bookmark. If you select any bug reference ID in the table, a bookmark tag is added to the URL by using the "#NNNNNNN" format. You can then share this URL with others so that they can jump directly to the desired fix in the table.
For more information about the bugs that are fixed and enhancements that are included in this cumulative update, see the following table.

Bug reference Description Fix Area Component Platform 4676249 Fixes an issue in which backup log operations fail and return an error that indicates that BACKUP LOG is not allowed while the recovery model is SIMPLE. - SQL Server Engine - Backup Restore - Windows 4710575 Fixes an AV assertion issue in DbMgrPartner that's related to new log readiness notifications. - SQL Server Engine - High Availability and Disaster Recovery - All 4769216 Fixes an issue in which non-yielding scheduler dump files are generated when SSL connections are closed under high CPU load. - Connectivity - Protocols - All 4783675 Fixes an issue in which upgrading from SQL Server 2019 to SQL Server 2022 might cause the upgrade process to stop responding during the model database upgrade phase. - SQL Server Engine - Programmability - All 4783748 Changes the behavior of the program to return error 19544 instead of returning an assert when you create an availability group that has a name that's longer than 64 characters by using cluster_type = NONE or EXTERNAL. - SQL Server Engine - High Availability and Disaster Recovery - All 4796333 Fixes an issue that causes crashes when an invalid ID type is returned from the Domain Controller in LookupAccountSid. - SQL Server Engine - Linux - Linux 4796376 Fixes an issue that prevents Active Directory logins from working if the keytab file is updated too long after the privileged user password is rotated. - SQL Server Engine - Linux - Linux 4798276 Fixes an issue in which Distributed Availability Group seeding fails if the local Availability Group is offline. - SQL Server Engine - High Availability and Disaster Recovery - Windows 4807292 Fixes a failure to configure multiple concurrent auditing to write to the Security Event log during updates. - SQL Server Engine - Security Infrastructure - All 4811256 Fixes a crash that's caused by a missing partition in a common table expression (CTE). - SQL Server Engine - Programmability - All 4818763 Fixes a bug that causes memory allocation failure during VDI restore operations if memory is limited through cgroupsv2 on Linux. - SQL Server Engine - Linux - Linux 4837925 Fixes an issue in which SSCM fails when it imports certain certificates, including self-signed certificates that are password protected and certificates exported from Azure AKV that are not password protected. - SQL Server Configuration Manager - Certificate Import - Windows 4838959 Restricts privileges for dbcc stackdump so that only the sysadmin can invoke the dump file. - SQL Server Engine - Security Infrastructure - All 4849635 Fixes an issue in which AppDomains in a DOOMED state are not unloaded correctly. - SQL Server Engine - Query Execution - All 4866387 Allows using the sys.fn_xe_file_target_read_file() function to read system_health event session data in Azure SQL Managed Instance. - SQL Server Engine - SQL OS - Windows

How to obtain or download this or the latest cumulative update package

File information

Notes for this update

How to uninstall this update

References

Last updated on 01/29/2026

Original source

This article describes Cumulative Update package 22 (CU22) for Microsoft SQL Server 2022. This update contains 20 fixes that were issued after the release of SQL Server 2022 Cumulative Update 21. It updates components in the following builds:

• SQL Server - Product version: 16.0.4225.2, file version: 2022.160.4225.2
• Analysis Services - Product version: 16.0.43.252, file version: 2022.160.43.252

Known issues in this update

Incorrect behavior of SESSION_CONTEXT in parallel plans

Queries that use the built-in SESSION_CONTEXT function might return incorrect results or trigger access violation (AV) dump files when run in parallel query plans. This issue occurs because of the manner in which SESSION_CONTEXT interacts with parallel execution threads, particularly if the session is reset for reuse.

For more information, see the Known issues section in SESSION_CONTEXT.

Improvements and fixes included in this update

A downloadable Microsoft Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017. Download this Excel file now.

Note

Individual entries in the following table can be referenced directly through a bookmark. If you select any bug reference ID in the table, a bookmark tag is added to the URL by using the "#NNNNNNN" format. You can then share this URL with others so that they can jump directly to the desired fix in the table.

For more information about the bugs that are fixed and enhancements that are included in this cumulative update, see the following table.

[Table of bug fixes with references, descriptions, fix areas, components, and platforms]

How to obtain or download this or the latest cumulative update package

File information

Notes for this update

How to uninstall this update

References

• Announcing updates to the SQL Server Incremental Servicing Model (ISM)
• SQL Server Service Packs are no longer supported starting from SQL Server 2017
• Determine which version and edition of SQL Server Database Engine is running
• Servicing models for SQL Server
• Naming schema and Fix area descriptions for SQL Server software update packages
• Description of the standard terminology that is used to describe Microsoft software updates

Original source

Known issues in this update

Incorrect behavior of SESSION_CONTEXT in parallel plans
Queries that use the built-in SESSION_CONTEXT function might return incorrect results or trigger access violation (AV) dump files when run in parallel query plans. This issue occurs because of the manner in which SESSION_CONTEXT interacts with parallel execution threads, particularly if the session is reset for reuse.
For more information, see the Known issues section in SESSION_CONTEXT.

Improvements and fixes included in this update

A downloadable Microsoft Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017. Download this Excel file now.

Note
Individual entries in the following table can be referenced directly through a bookmark. If you select any bug reference ID in the table, a bookmark tag is added to the URL by using the "#NNNNNNN" format. You can then share this URL with others so that they can jump directly to the desired fix in the table.

For more information about the bugs that are fixed and enhancements that are included in this cumulative update, see the following table.

[Table of fixes with Bug reference, Description, Fix area, Component, Platform]

How to obtain or download this or the latest cumulative update package

File information

Notes for this update

How to uninstall this update

References

Original source

This article describes Cumulative Update package 21 (CU21) for Microsoft SQL Server 2022. This update contains 17 fixes that were issued after the release of SQL Server 2022 Cumulative Update 20. It updates components in the following builds:

• SQL Server - Product version: 16.0.4215.2, file version: 2022.160.4215.2
• Analysis Services - Product version: 16.0.43.247, file version: 2022.160.43.247

Known issues in this update

Incorrect behavior of SESSION_CONTEXT in parallel plans

Queries that use the built-in SESSION_CONTEXT function might return incorrect results or trigger access violation (AV) dump files when run in parallel query plans. This issue occurs because of the manner in which SESSION_CONTEXT interacts with parallel execution threads, particularly if the session is reset for reuse.

For more information, see the Known issues section in SESSION_CONTEXT.

Improvements and fixes included in this update

A downloadable Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017. Download this Excel file now.

Note

Individual entries in the following table can be referenced directly through a bookmark. If you select any bug reference ID in the table, a bookmark tag is added to the URL by using the "#NNNNNNN" format. You can then share this URL with others so that they can jump directly to the desired fix in the table.

For more information about the bugs that are fixed and enhancements that are included in this cumulative update, see the following table.

[Table of bug fixes with references, descriptions, fix areas, components, and platforms]

How to obtain or download this (or the latest) cumulative update package

[Instructions and disclosure triangles for obtaining or downloading the update for Windows and Linux]

File information

[File hash information and cumulative update package file information]

Notes for this update

[Prerequisites, restart information, registry information, important notices, hybrid environment deployment, language support, components updated, support for this update]

How to uninstall this update

[Instructions for uninstalling on Windows and Linux]

References

• Announcing updates to the SQL Server Incremental Servicing Model (ISM)
• SQL Server Service Packs are no longer supported starting from SQL Server 2017
• Determine which version and edition of SQL Server Database Engine is running
• Servicing models for SQL Server
• Naming schema and Fix area descriptions for SQL Server software update packages
• Description of the standard terminology that is used to describe Microsoft software updates

Original source