Rediger

Del via

KB5080999 - Cumulative Update 24 for SQL Server 2022

  • Gælder for: 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 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.

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 '<YourAGListener>'. Error: 10013.
The Service Broker endpoint is in disabled or stopped state.
Stopped listening on listener network name '<YourAGListener>' (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 '<YourWSFCguid>' 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 '<YourWSFCguid>', DNS name '<YourAGListener>', 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 [<YourAGListener>]. 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.

Bug reference Description Fix Area Component Platform
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

How to obtain or download the latest cumulative update package for Windows (recommended)

The following update is available from the Microsoft Download Center:

Download the latest cumulative update package for SQL Server 2022 now

Note

  • Microsoft Download Center always offers the latest SQL Server 2022 CU release.
  • If the download page doesn't appear, contact Microsoft Customer Service and Support to obtain the cumulative update package.
How to obtain or download this cumulative update package for Windows from Microsoft Update Catalog

The following update is available from the Microsoft Update Catalog:

Note

  • Microsoft Update Catalog contains this SQL Server 2022 CU and previously released SQL Server 2022 CU releases.
  • This CU is also available through Windows Server Update Services (WSUS).
  • We recommend that you always install the latest cumulative update that is available.
How to obtain or download the latest cumulative update package for Linux

To update SQL Server 2022 on Linux to the latest CU, you must first have the Cumulative Update repository configured. Then, update your SQL Server packages by using the appropriate platform-specific update command.

For installation instructions and direct links to the CU package downloads, see the SQL Server 2022 Release Notes.

File information

File hash information

You can verify the download by computing the hash of the SQLServer2022-KB5080999-x64.exe file through the following command:

certutil -hashfile SQLServer2022-KB5080999-x64.exe SHA256

File name SHA256 hash
SQLServer2022-KB5080999-x64.exe 57FC522E34FA4654F5EE8DBC9768EFE3265971C8D6854F32118022B2610D40E2
Cumulative Update package file information

Download the list of files that are included in KB5080999.

Notes for this update

Prerequisites

To apply this cumulative update package, you must be running SQL Server 2022.

Restart information

You might have to restart the computer after you apply this cumulative update package.

Registry information

To use one of the hotfixes in this package, you don't have to make any changes to the registry.

Important notices

This article also provides the following important information.

Analysis Services CU build version

Beginning in Microsoft SQL Server 2017, the Analysis Services build version number and SQL Server Database Engine build version number don't match. For more information, see Verify Analysis Services cumulative update build version.

Cumulative updates (CU)

  • Each new CU contains all the fixes that were included with the previous CU for the installed version of SQL Server.
  • SQL Server CUs are certified to the same levels as service packs, and should be installed at the same level of confidence.
  • We recommend ongoing, proactive installation of CUs as they become available according to these guidelines:
    • Historical data shows that a significant number of support cases involve an issue that has already been addressed in a released CU.
    • CUs might contain added value over and above hotfixes. This includes supportability, manageability, and reliability updates.
  • We recommend that you test SQL Server CUs before you deploy them to production environments.
Hybrid environment deployment

When you deploy an update to a hybrid environment (such as Always On, replication, cluster, and mirroring), we recommend that you refer to the following articles before you deploy the update:

Language support

SQL Server CUs are currently multilingual. Therefore, this CU package isn't specific to one language. It applies to all supported languages.

Components (features) updated

One CU package includes all available updates for all SQL Server 2022 components (features). However, the cumulative update package updates only those components that are currently installed on the SQL Server instance that you select to be serviced. If a SQL Server feature (for example, Analysis Services) is added to the instance after this CU is applied, you must reapply this CU to update the new feature to this CU.

Support for this update

If other issues occur, or if any troubleshooting is required, you might have to create a service request. The usual support costs will apply to additional support questions and to issues that don't qualify for this specific cumulative update package. For a complete list of Microsoft Customer Service and Support telephone numbers, or to create a separate service request, go to the Microsoft support website.

How to uninstall this update

How to uninstall this update on Windows
  1. In Control Panel, open the Programs and Features item, and then select View installed updates.
  2. Locate the entry that corresponds to this cumulative update package under SQL Server 2022.
  3. Press and hold (or right-click) the entry, and then select Uninstall.
How to uninstall this update on Linux

To uninstall this CU on Linux, you must roll back the package to the previous version. For more information about how to roll back the installation, see Rollback SQL Server.

References

  • Last updated on