Skip to content

35877153.md

Latest commit

 

History

History
133 lines (94 loc) · 7.26 KB

35877153.md

File metadata and controls

133 lines (94 loc) · 7.26 KB
title Summary of changes in Configuration Manager current branch, version 2509
description Article listing changes in Configuration Manager current branch, version 2509
ms.date 11/11/2025
ms.subservice core-infra
ms.topic reference
ms.collection tier3

Summary of changes in Configuration Manager current branch, version 2509

Applies to: Configuration Manager (current branch, version 2509)

Summary of KB35877153

Release version 2509 of Configuration Manager current branch contains fixes and feature improvements. The "Issues that are fixed" list isn't inclusive of all changes. Instead, it highlights changes the product development team believes are most relevant to the broad Configuration Manager customer base. These changes were made in response to direct customer feedback about product issues and improvements.

Notes

Issues that are fixed

  • Task sequences fail to run on ARM64 clients due to reading an incorrect registry key.
  • ARM64 clients are unable to retrieve policy after upgrading from Windows 10 to Windows 11.
  • The site server recovery process is optimized to prevent updating statistics on all tables. This change improves the performance of the recovery process.
  • Boundary group data is now replicated to the central administration site (CAS). The "Boundary Group(s)" column can now be added and populated when viewing devices from the console.
  • The SCCMReporting.log file is optimized to more accurately show specific errors; this reduces troubleshooting time needed for reporting services.
  • The message "Violation of PRIMARY KEY constraint 'CI_DocumentStore_PK'" can occur when trying to create new applications or synchronize Windows Server Update Services (WSUS). This error happens after updating to a new version of Configuration Manager.
  • Active Directory (Microsoft Entra) discovery processing and logging is updated to improve stability and troubleshooting of the discovery process.
  • The content library cleanup process now handles multiple SMS providers correctly. Previously it might fail if a provider was offline or otherwise unavailable.
  • Configuration Manager updates can fail after upgrading to Windows Server 2019 or 2022. Errors similar to the following are recorded in the CMUpdate.log file. 
    ERROR: CompileMOFFile: Failed to compile MOF E:\ConfigMgr\bin\x64\TaskSequenceProvider.mof, error -1
ERROR: Failed to compile MOF file E:\ConfigMgr\bin\x64\TaskSequenceProvider.mof.
ERROR: Failed to install/Upgrade SDK Server on {SiteServer}.
InstallComponents failed

In some cases after this error occurs, the server may fail to restart normally. Booting into safe mode results in the following message:

LogonUI.exe - System Error : 
The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
  • Deployed Task Sequences that are configured to only run and restart in a Maintenance Window fail to reboot using the "Restart Computer" step when only using a "Task sequences" Maintenance Window (Type 5).
  • Phased deployments can fail after updating to a new version of Configuration Manager. Errors similar to the following are recorded in the PhasedDeployment.log file. 
    Exception: System.Data.SqlClient.SqlException (0x80131904): A trigger returned a result set and/or was running with SET NOCOUNT OFF while another outstanding result set was active.
  • The Microsoft Entra discovery process can time out in environments with a large number of clients.
  • Disabling a "Monthly by Weekday" offset schedule for maintenance windows results in an invalid policy distributed to clients. This error has the side effect of preventing any service windows from being applied.
  • The distribution point usage summary report isn't updated correctly in environments using the enhanced HTTP configuration.
  • Logging is improved for multiple site server components to improve ease of troubleshooting.
  • Client agent installation fails during OSD if the client.msi parameter CCMALWAYSINF=1 is provided and the device booted through the PXE Responder service.
  • The Start-CMContentDistribution cmdlet doesn't distribute content for task sequences.
  • Group membership data for machines and users is removed if the discovery process fails with error 0x8007200F (ERROR_DS_UNAVAILABLE).
  • The size of the client content cache is reported incorrectly when partial content is downloaded.
  • Content can fail to download onto a client if the computer enters a connected standby state during the download process.
  • The service connection tool now checks for the required ODBC driver version. Logging is also improved for easier troubleshooting.
  • A management point in an untrusted forest can fail to manage clients due to a SQL connection error.
  • The create task sequence media process fails when creating bootable media if the SMS provider isn't installed on the management point.
  • The New-CMAdministrativeUser cmdlet doesn't work as expected if the Name value in Microsoft Entra doesn't match the SamAccountName value.
  • Available user deployments don't appear in Software Center when the Configuration Manager client is installed on Windows Server 2025.
  • The Install Software Updates task sequence step fails on new computer (bare metal) installations after installing KB32851084 on version 2503.

Hotfixes that are included in this update

  • KB 32851084: Update rollup for Microsoft Endpoint Configuration Manager current branch, version 2503
  • KB 33177653: Azure for US Government update for Microsoft Configuration Manager
  • KB 34503790: Revised security update for Microsoft Configuration Manager
  • KB 35958849: Cloud management gateway deployment maintenance update

Dependency changes

  • The Microsoft SQL Server Management Objects and Microsoft System CLR Types for SQL Server are updated to the 2016 versions.