Edit

Share via


KB5075211 - Cumulative Update 2 for SQL Server 2025

Release Date:   February 12, 2026
Version:   17.0.4015.4

Summary

This article describes Cumulative Update (CU2) for Microsoft SQL Server 2025. This update package contains six fixes that were issued after the initial release of SQL Server 2025. It updates components in the following builds:

  • SQL Server - Product version: 17.0.4015.4, file version: 2025.170.4015.4
  • Analysis Services - Product version: 17.0.25.223, file version: 2025.170.25.223

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 2025, 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
4838699 Fixes an issue that causes StripedVdi tests to fail if the Sqlvdi.dll file isn't registered on running instances. SQL Server Engine Backup Restore Windows
4860948 For cluster_type = NONE or EXTERNAL, availability group (AG) properties exist on only the local replica. This update writes the properties to the AG configuration so that all AG replicas receive the same properties. SQL Server Engine High Availability and Disaster Recovery All
4869015 Fixes a potential inaccuracy in resource governor accounting for the tempdb space if accelerated database recovery is enabled for tempdb. SQL Server Engine Resource Governor All
4924793 Fixes an issue in which an assertion and a dump file are generated around midnight on New Year’s Day during an operation that accesses Azure Blob Storage. SQL Server Engine Storage Management All
4925942 Fixes an issue that triggers nonyielding scheduler dump files in PmmLogAcceptBlock on the availability group (AG) secondary replica. The issue occurs if the persistent log buffer is enabled, and the database log cache contains primarily tiny log records. SQL Server Engine Log Management All
4931611 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 AG listener name. SQL Server Engine Replication All

How to obtain or download this CU or the latest CU 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 2025 now

Note

  • Microsoft Download Center always offers the latest SQL Server 2025 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 2025 CU and previously released SQL Server 2025 CU releases.
  • This CU is also available through Windows Server Update Services (WSUS).
  • We recommend that you always install the latest cumulative update that's available.
How to obtain or download the latest cumulative update package for Linux

To update SQL Server 2025 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 2025 Release Notes.

File information

File hash information

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

certutil -hashfile SQLServer2025-KB5075211-x64.exe SHA256

File name SHA256 hash
SQLServer2025-KB5075211-x64.exe 96ECDF19BBAA193D3689F22DE20E122656F9AD9357B851A3D0FA3FCBEECC9525
Cumulative Update package file information

Download the list of files that are included in KB5075211.

Notes for this update

Prerequisites

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

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 was already addressed in a released CU.
    • CUs might contain added value over and above hotfixes, such as 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 2025 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 2025.
  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