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: November 13, 2025
Version: 16.0.4225.2
Summary
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.
| Bug reference | Description | Fix area | Component | Platform |
|---|---|---|---|---|
| 4339844 | Fixed an assertion failure File: <writeEncoded.cpp>, line='' Failed Assertion = 'pCurTargetBuf == pSource->m_pDirectEncodeTarget' during a differential backup that uses compression on databases that contain large volumes of FILESTREAM records. |
SQL Server Engine | Backup Restore | Windows |
| 4467909 | Fixes an issue in which non-yielding scheduler dump files are generated in PmmLogAcceptBlock on the Availability Group secondary replica if persistent log buffer is enabled and the database's log cache contains primarily tiny log records. | SQL Server Engine | Log Management | All |
| 4471009 | Fixes an issue in which DBCC CHECKDB with EXTENDED_LOGICAL_CHECKS fails and returns an exception if there are both persisted and non-persisted computed columns in a table while trace flag 176 is enabled. | SQL Server Engine | Programmability | All |
| 4498278 | Fixes an issue in which one or more databases enter the suspect state instead of the expected resolving state when a replica is removed from an availability group or the availability group is dropped while the associated replica is offline. | SQL Server Engine | High Availability and Disaster Recovery | All |
| 4511222 | Fixes incorrect display values of the Instant File Initialization and Lock Pages in Memory fields in SQL Server Configuration Manager. | SQL Server Client Tools | SQL Server Configuration Manager | Windows |
| 4552086 | Fixes incorrect handling of write errors during a seeding restore process that's caused by misinterpretation of system error codes. | SQL Server Engine | Backup Restore | All |
| 4573341 | Upgrade Microsoft.Rest.ClientRuntime version to 2.3.24 on SSIS to fix vulnerability (CVE-2022-26907). |
Integration Services | Integration Services | Windows |
| 4573769 | Introduces automatic cleanup of stale Log-Replay Service (LRS) metadata (older than 36 days) | SQL Satellite | Cleanup service | Windows |
| 4582175 | Enables caps for CacheStore PHDR usage when queries consume too much of the server's memory. | SQL Server Engine | SQL OS | Windows |
| 4598768 | Fixes an issue that causes inconsistent behavior when you import a certificate by using the drop-down menu or when you use the import button in the Configuration Manager. Also fixes an issue in which selecting a certificate by using the thumbprint fails if the case doesn't match. |
SQL Connectivity | SQL Connectivity | Windows |
| 4642574 | Fixes dump files during data copy from I/O pipeline when you perform a database restore process on versioned MI that has the worker.cl.wcow.sql22 app type. | SQL Server Engine | Backup Restore | All |
| 4644033 | Fixes incorrect error handling that could cause the program not to respond when you run DBCC CHECKDB, CHECKTABLE, or CHECKFILEGROUP. | SQL Server Engine | Backup Restore | All |
| 4660895 | Fixes an issue in SQL Server Analysis Services in which Row-Level Security (RLS) filters could be skipped when combined with Object-Level Security (OLS) and Column-Level Security (CLS) in certain multi-role configurations. | Analysis Services | Analysis Services | Windows |
| 4675941 | Fixes an issue in which transient negative elapsed time values on a secondary replica of an availability group causes data movement to pause. | SQL Server Engine | High Availability and Disaster Recovery | All |
| 4713355 | Fixes the sp_do_backup stored procedure under the managed_backupview to remove a SQL injection vulnerability. This stored procedure is for internal use only. |
SQL Server Engine | Management Services | All |
| 4713591 | Fixes access violation dump files during OLEDB calls if the Service Principal Name is missing. | SQL Server Engine | Security Infrastructure | All |
| 4723335 | Fixes an access violation dump file caused by an out-of-memory condition when fetching AAD authentication certificates. | SQL Server Engine | Security Infrastructure | All |
| 4723355 | Fixes an issue when the SQL Agent reads feature switches for Managed Instances (MI). | SQL Agent for Managed Instance | SQL Agent for Managed Instance | Windows |
| 4729459 | Fixes an issue in sys.database_automatic_tuning_mode in which database state transitions can cause access violations while a query is running this DMV. | SQL Server Engine | Database Automatic Tuning | All |
| 4729881 | Fixes an issue in which error codes aren't captured immediately after certain function calls. This condition causes the code to be overwritten and retry checks to behave incorrectly. | SQL Server Engine | SQL OS | All |
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-KB5068450-x64.exe file through the following command:
certutil -hashfile SQLServer2022-KB5068450-x64.exe SHA256
| File name | SHA256 hash |
|---|---|
| SQLServer2022-KB5068450-x64.exe | B06B59D7A41CC57BF0CC3EAEADB4E5FC196EA72E8FD1914C42760E31ADBF40E6 |
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