KB5104822 - Cumulative Update 8 for SQL Server 2025

Release Date:   August 13, 2026
Version:   17.0.4075.5

Summary

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

  • SQL Server - Product version: 17.0.4075.5, file version: 2025.170.4075.5
  • Analysis Services - Product version: 17.0.25.223, file version: 2025.170.25.223

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 and generate 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 '<DatabaseName>' is marked RESTORING and is in a state that does not allow recovery to be run.
***Stack Dump being sent to <SQLServerLogFolder>\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 = <frame id="00" address="0x7FFDED94970D" pdb="sqlmin.pdb" age="2" guid="E1039014-237E-4DB6-88FD-4A2AB31C651F" module="sqlmin" rva="0x2970D" />
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 in this cumulative update 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 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
4929794 Fixes an issue in which restoring a database by using Volume Shadow Copy Service (VSS) and WITH MOVE takes a long time or times out if the server contains hundreds of databases. SQL Server Engine Backup Restore Windows
5189710 Adds encryption support for communication between the PolyBase external service and clients that use gRPC on Linux. SQL Server Engine PolyBase Linux
5197076 Fixes an issue in which an index rebuild maintenance plan stops responding because of a long-running query. SQL Server Engine Maintenance Plan All
5379749 Fixes an issue in which SQL Server Setup recommends a max server memory value of 128 GB instead of 256 GB for Standard and Standard Developer editions. SQL Setup Deployment Platform Windows
5391747 Fixes an issue in which a Hekaton transaction remains in the Validating state after an internal transaction encounters a validation failure during the preparatory phase when memory-optimized tempdb metadata is enabled. SQL Server Engine In-Memory OLTP All
5400887 Fixes an issue in which changing the collation during initial setup can block mssql-conf unexpectedly on systems that have a high CPU count. SQL Server Engine Linux Linux
5414824 Adds a new optional parameter, @multi_subnet_failover, to sp_adddistributor. SQL Server Engine Replication Windows
5425855 Fixes an issue in which OPENJSON returns unexpected rows when a JSON path contains special pattern-matching characters, including %, _, [, or ]. SQL Server Engine Programmability All
5434644 Fixes an assertion and dump file that occur when DBCC CHECKTABLE runs with EXTENDED_LOGICAL_CHECKS against a persisted computed column that uses the native json data type. SQL Server Engine Programmability All
5446188 Fixes errors 13643 and 7102 that occur when JSON_MODIFY appends a value to a native json array that contains 65,535 elements. SQL Server Engine Programmability All
5446201 Fixes error 13643, state 101, that occurs when JSON_MODIFY receives a native json array that contains 65,536 or more elements as its value argument. SQL Server Engine Programmability All
5446209 Fixes errors 13647 and 13643 that occur when JSON_MODIFY overwrites or deletes a stored native json array that contains 65,536 or more elements. SQL Server Engine Programmability 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-KB5104822-x64.exe file through the following command:

certutil -hashfile SQLServer2025-KB5104822-x64.exe SHA256

File name SHA256 hash
SQLServer2025-KB5104822-x64.exe 0730D5A44A0B51454B635CA08C4174BB49BD6406CE8D154B3351B2A01D833932
Cumulative Update package file information

Download the list of files that are included in KB5104822.

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 in 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