Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Release Date: January 15, 2026
Version: 16.0.4235.2
Summary
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.4235.2, file version: 2022.160.4235.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.
| 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. | Conectivity | 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
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-KB5074819-x64.exe file through the following command:
certutil -hashfile SQLServer2022-KB5074819-x64.exe SHA256
| File name | SHA256 hash |
|---|---|
| SQLServer2022-KB5074819-x64.exe | 6DD251B27E916C80231B0278A799CA8AF7479461038A53254F7C906408425591 |
Cumulative Update package file information
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:
Upgrade a failover cluster instance
Note
If you don't want to use the rolling update process, follow these steps to apply an update:
- Install the update on the passive node.
- Install the update on the active node (requires a service restart).
Upgrade and update of availability group servers that use minimal downtime and data loss
Note
If you enabled Always On together with the SSISDB catalog, see the information about SSIS with Always On about how to apply an update in these environments.
How to apply a hotfix for SQL Server in a transactional replication and database mirroring topology
How to apply a hotfix for SQL Server in a replication topology
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
- In Control Panel, open the Programs and Features item, and then select View installed updates.
- Locate the entry that corresponds to this cumulative update package under SQL Server 2022.
- 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
- 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