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.
Applies to: Configuration Manager (current branch)
With Configuration Manager, product release notes are limited to urgent issues. These issues aren't yet fixed in the product, or detailed in a troubleshooting article.
Feature-specific documentation includes information about known issues that affect core scenarios.
This article contains release notes for the current branch of Configuration Manager. For information on the technical preview branch, see Technical Preview.
For information about the new features introduced with different versions, see the following articles:
Tip
You can use RSS to be notified when this page is updated. For more information, see How to use the docs.
Set up and upgrade
ODBC driver version 18.7.1.1 can block site configuration before updating to 2609
Applies to: upgrades to version 2609
Microsoft ODBC Driver for SQL Server version 18.7.1.1 has a known issue with Configuration Manager version 2603 and earlier that can block site configuration.
To avoid this issue, don't install ODBC driver version 18.7.1.1 before updating Configuration Manager. Use ODBC driver version 18.6.2.1, the validated version shipped with Configuration Manager 2609, for the update. Complete the Configuration Manager update to version 2609 before you install ODBC driver version 18.7.1.1.
For more information, see ODBC driver for SQL Server.
Configuration Manager performance counters are missing on Windows Server 2025
Applies to: primary site servers and management points running Windows Server 2025
On Windows Server 2025, Configuration Manager performance counter registration can fail, leaving the counters unavailable in Performance Monitor. This issue can occur after a clean installation of Windows Server 2025 or an in-place upgrade from Windows Server 2022.
Perfsetup.log records errors similar to the following:
Error: InstallSMSObjectAndCounterKeySettingsIntoRegistry() could not get the "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\SMS_SOFTWARE_INVENTORY_PROCESSOR\Performance" registry key; error = 6 (0x6).
Perfsetup can also exit with code 1000. The affected component name in the registry path can vary.
To resolve this issue, install the update rollup for Configuration Manager version 2603 (KB39169655) or update to Configuration Manager version 2609, which also includes this fix.
OS deployment
Task sequence status messages fail in the full OS with CNG/KSP boot media certificates
Applies to: version 2609
After you upgrade to Configuration Manager version 2609, task sequences that use boot media with an imported public key infrastructure (PKI) certificate backed by a Cryptography Next Generation (CNG) key storage provider (KSP) might fail to send status messages after restarting from Windows PE into the full Windows OS.
smsts.log records error 0x80072f9a (ERROR_WINHTTP_CLIENT_CERT_NO_ACCESS_PRIVATE_KEY). Each failed attempt to send a status message is retried, adding delays to OS deployment. The Windows PE phase isn't affected.
To work around this issue, import the certificate's private key into a legacy cryptographic service provider (CSP), export the certificate and private key to a new Personal Information Exchange (PFX) file, and recreate the bootable media.
Use an RSA certificate with an exportable private key. Protect the PFX files and their passwords from unauthorized access.
Open a Command Prompt window in the folder that contains the original PFX file. Run the following command to import the certificate into the current user's Personal certificate store by using the Microsoft Enhanced RSA and AES Cryptographic Provider:
certutil -user -csp "Microsoft Enhanced RSA and AES Cryptographic Provider" -p "<pfxpassword>" -importPFX My boot-media-original.pfxReplace
<pfxpassword>with the original PFX file's password andboot-media-original.pfxwith its file name.Run
certmgr.mscto open the certificate management console for the current user. Expand Personal, and then select Certificates.Right-click the imported certificate, select All Tasks, and then select Export. In the Certificate Export Wizard, select Next.
Select Yes, export the private key, and then select Next. Select Personal Information Exchange - PKCS #12 (.PFX) and Include all certificates in the certification path if possible, and then select Next.
Select Password, enter and confirm a strong password, and then select Next. Specify a new file name, such as
boot-media-legacy-csp.pfx, select Next, and then select Finish.Verify the exported PFX file by running the following command. Replace
<pfxpassword>with the new PFX file's password:certutil -p "<pfxpassword>" -dump boot-media-legacy-csp.pfxVerify that the provider is Microsoft Enhanced RSA and AES Cryptographic Provider before you use the certificate to create media.
Create new bootable media. On the Security page of the Create Task Sequence Media Wizard, select Import PKI certificate and specify the new PFX file
boot-media-legacy-csp.pfxand its password. Use the new media for subsequent deployments.
For more information, see certutil and Export a certificate with its private key.
Content management
Content downloads fail with HTTP 403.7 from PKI HTTPS distribution points
Applies to: version 2609
After you upgrade to Configuration Manager version 2609, clients and pull-distribution points might fail to download content from HTTPS distribution points that use public key infrastructure (PKI) certificates. Downloads can fail even when the downloading client or pull-distribution point has a valid client certificate.
The source distribution point's IIS log records HTTP status 403.7. DataTransferService.log and, for pull-distribution points, PullDP.log can record error 0x80190193. Not all downloads are affected; connections that have already negotiated a valid client certificate might succeed.
To identify whether a failed content download is affected by this issue, update the SSL settings on the affected distribution point and retry the download:
Important
This procedure briefly changes client certificate enforcement. Don't leave Client certificates set to Accept.
- On the affected distribution point server, open Internet Information Services (IIS) Manager as an administrator.
- In the Connections pane, expand the server, expand Sites, and then expand the website that hosts the distribution point virtual directories. Select SMS_DP_SMSPKG$.
- In Features View, double-click SSL Settings.
- On the SSL Settings page, verify that Require SSL is selected. Under Client certificates, select Accept, and then select Apply in the Actions pane.
- Under Client certificates, select Require, and then select Apply in the Actions pane. Keep Require SSL selected.
- Select the SMS_DP_SMSSIG$ virtual directory and repeat steps 3 through 5.
- Retry the previously failed content download from the same distribution point. If the download succeeds after you apply these settings, this result confirms the issue described in this release note.
This change isn't permanent. Configuration Manager reapplies the affected settings every 48 hours and when the distribution point is reconfigured or upgraded.
For more information, see Configure client certificates in IIS.
Client authentication and registration
Microsoft Entra token validation fails when the management point can't access the internet
Applies to: version 2603 and later
Starting in version 2603, the management point uses Microsoft Identity Service Essentials (MISE) for Microsoft Entra token validation and requires internet access. This requirement affects sites configured to support Microsoft Entra joined users and devices when clients authenticate using Microsoft Entra tokens, typically through a cloud management gateway (CMG). Environments that only use on-premises Active Directory authentication without Microsoft Entra integration aren't affected.
If the management point can't reach the required endpoints, CCM_STS_ManagedBase.log on the management point records a MiseAuthenticationTicketProviderException with an underlying network error, for example:
Microsoft.Identity.ServiceEssentials.Exceptions.MiseAuthenticationTicketProviderException: MISE12034: AuthenticationTicketProvider Name:AuthenticationTicketProvider
System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it
Important
The MISE12034 exception can also occur for other reasons. Before applying this resolution, verify that the underlying exception indicates a network connectivity problem, such as a SocketException, HttpRequestException, or connection timeout.
To resolve this issue, allow the management point server to access the following Microsoft Entra authentication endpoints through the proxy and firewall in the Local System context:
https://login.microsoftonline.comhttps://sts.windows.net
If the management point uses a proxy, configure it in the Local System context. In version 2603, the proxy set in the site system properties and a WinHTTP-only proxy (netsh winhttp set proxy) aren't used for this validation path.
For configuration steps and the full list of required endpoints, see Management point proxy configuration and Management point internet access requirements.
Bulk registration token verification fails after installing the version 2603 update rollup
Applies to: version 2603 with update rollup KB39169655 installed
After you install the update rollup for Configuration Manager version 2603 (KB39169655), bulk registration token verification fails on the management point for devices that aren't Microsoft Entra joined and connect through a cloud management gateway (CMG). Affected devices can't complete bulk registration through the CMG to obtain their individual Configuration Manager-issued client authentication tokens. Other CMG communication scenarios for these devices may also be affected.
This issue doesn't affect devices that use Microsoft Entra authentication or version 2603 sites that haven't installed KB39169655.
On the management point, errors similar to the following are recorded in <MP_InstallDir>\Logs\CCM_STS.log:
ProcessRequest - Start
Incoming request URL: https://<management-point>/CCM_STS
Validated PreAuth SelfProve token. UniqueId: <client-id>. ClientKey: <public-key>
ProcessRequest - Exception: System.IO.FileLoadException:
Could not load file or assembly
'mpisapiclr, Version=5.0.9146.1045, Culture=neutral,
PublicKeyToken=31bf3856ad364e35' or one of its dependencies.
The located assembly's manifest definition does not match the assembly reference.
(Exception from HRESULT: 0x80131040)
To resolve this issue, install KB40345593, which is available in Updates and Servicing after you install KB39169655. This update requires a site reset after installation, but doesn't require a computer restart.
Collection management
Collections based on Active Directory group membership lose members after upgrading to version 2609
Applies to: version 2609
After you upgrade to Configuration Manager version 2609, a full Microsoft Entra user group discovery cycle might remove Active Directory user-group relationships from the Configuration Manager database. User collections with query-based membership rules that depend on Active Directory group membership might lose some or all members after collection evaluation. Deployments targeted to these collections might no longer reach the intended users.
To prevent further occurrences, disable Microsoft Entra user group discovery. Disabling discovery doesn't restore user-group relationships that have already been removed.
Software updates
Devices continue scanning Windows Update after moving the update workload back to Configuration Manager
Applies to: version 2503 with update rollup KB32851084 and KB36495448 installed, version 2509 with KB36495448 installed, and later releases that inherit this behavior
After you move the Windows Update policies co-management workload from Intune back to Configuration Manager, devices might continue scanning Windows Update or Microsoft Update instead of WSUS, even after a machine policy cycle completes.
Starting with KB36495448, the Configuration Manager client no longer sets or removes Windows Update scan source policies. Moving the workload slider doesn't automatically remove the Windows Update client policy state previously configured by Intune. This state can persist on the device after the Intune policy assignment is removed.
To address this issue, review the effective scan source for each update category and explicitly manage scan source policies through Group Policy or Intune. As a best practice, remove or reassign the device's Intune Windows Update client policy assignment before moving the workload back. For the cleanup procedure and alternative policy configuration, see Moving the workload back to Configuration Manager.
Reset default value of superseding age in months for software updates
Applies to: version 2303
Removing SUP role in Admin Console doesn't reset the superseding age property in WMI. As a result, while reconfiguring the role, the previously configured value is shown in the configuration window. This property needs to be reset to default value on role removal. For more information, see supersedence rules for installing a software update point.
Cloud services
CMG shared key access changes
Applies to: version 2609 updates with an existing cloud management gateway
Version 2609 automatically disables shared key access for CMG storage. The CMG enhanced security workflow prepares the Azure prerequisites and configures the content uploader to use Microsoft Entra authentication instead of shared key authentication.
Before updating, consider enabling CMG enhanced security with an authorized Azure administrator. For a running virtual machine scale set CMG, use the following steps when the action is available:
- In the Configuration Manager console, go to the Administration workspace, expand Cloud Services, and select Cloud Management Gateway.
- Select the CMG, then select CMG enhanced security. For more information, see CMG enhanced security option.
- Select the appropriate tenant and sign in with an Azure account authorized to assign the required roles at the CMG resource group and register resource providers in the subscription. Select Update and verify that the workflow completes successfully.
- Allow any resulting CMG deployment work and permission propagation to complete. Verify the server application's Azure RBAC permissions and the required resource provider registration.
If you don't enable enhanced security before updating, the transition away from shared key access can result in either of the following scenarios. Use the symptoms and logs to identify the applicable guidance.
CMG update to version 2609 fails when Azure permissions or resource provider registration are missing
Existing CMG deployment updates can fail if Azure permissions or resource provider registration required for the transition are missing.
To address this failure, verify both prerequisites, even if you've run the CMG enhanced security workflow:
Azure role-assignment permissions: CloudMgr.log can report HTTP
403,DeploymentFailed, and a deniedMicrosoft.Authorization/roleAssignments/writeaction. Configure the server application's permissions as described in Configure Azure RBAC permissions for the server app. Contributor alone doesn't grant role-assignment permissions.Microsoft.Maintenance registration: Verify that this resource provider is Registered in each subscription that hosts a CMG. Have an authorized Azure administrator complete any missing registration. For instructions, see Configure Azure resource providers.
Allow permission changes and registration to complete, then verify the CMG deployment update and client communication. See Verify CMG deployment and client communication.
Content uploads to existing CMGs fail after updating to version 2609
Packages and applications might fail to upload to an existing content-enabled CMG or repeatedly retry. This scenario can affect CMGs created before version 2409 that haven't had enhanced security enabled. The site-side content uploader can continue using shared key authentication after the Azure storage account has disabled it.
Unlike the deployment update failure, content uploads can fail even when the CMG deployment update completes and the Azure prerequisites are met. Previously uploaded content isn't necessarily unavailable to clients.
PkgXferMgr.log can record storage account key retrieval followed by errors similar to the following:
Resource Manager - Key retrieved for storage service
Getting container Ids for StorageAccount: ...
CheckServiceStatus() failed
Failed to distribute content to the cloud DP.
Sending failed. Failure count = ...
The preferred workaround for an affected, running virtual machine scale set CMG is to enable CMG enhanced security, when the action is available, by using the procedure earlier in this section. After the workflow and any resulting deployment work complete, retry content distribution and verify successful package uploads.
Important
This workflow is expected to correct the authentication setting, but recovery hasn't been validated for every affected configuration. The action might be unavailable, including when the CMG is in an error state. If it isn't available or doesn't restore content uploads, contact Microsoft Support for recovery guidance. Don't directly modify the Configuration Manager database or re-enable shared key access in Azure.
Verify recovery through PkgXferMgr.log and Monitor content you distribute.