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, version 2603 with update rollup KB39169655 installed)
Summary of KB40345593
This update resolves a token verification issue that occurs after you install the update rollup for Microsoft Configuration Manager version 2603 (KB39169655).
After you install the update rollup, 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) to obtain a Configuration Manager-issued client authentication token.
This issue affects the bulk registration token scenario and may also affect other scenarios in which devices that aren't Microsoft Entra joined communicate through the CMG. It doesn't affect devices that use Microsoft Entra authentication.
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)
As a result, affected devices can't complete bulk registration through the CMG to obtain their individual client authentication tokens.
Update information for Microsoft Configuration Manager current branch, version 2603
This update is available in the Updates and Servicing node of the Configuration Manager console for version 2603 sites that have KB39169655 installed.
Important
This issue only affects version 2603 sites that have the update rollup (KB39169655) installed. Version 2603 sites that haven't installed the update rollup aren't affected by this issue and don't require KB40345593. This update appears in Updates and Servicing only after you install KB39169655.
Install KB40345593 to resolve this token verification issue on the management point.
Restart information
This update doesn't require a computer restart, but does require a site reset after installation.
Additional installation information
After you install this update on a primary site, preexisting secondary sites must be manually updated. To update a secondary site in the Configuration Manager console, select Administration > Site Configuration > Sites > Recover Secondary Site, and then select the secondary site. The primary site then reinstalls that secondary site by using the updated files. This reinstallation doesn't affect configurations and settings for the secondary site. New, upgraded, and reinstalled secondary sites under that primary site automatically receive this update.
Run the following SQL Server command on the site database to check whether the update version of a secondary site matches that of its parent primary site:
select dbo.fnGetSecondarySiteCMUpdateStatus ('SiteCode_of_secondary_site')
If the value 1 is returned, the site is up to date, with all the hotfixes applied on its parent primary site.
If the value 0 is returned, all the fixes that are applied to the primary site aren't installed for the secondary site. Use the Recover Secondary Site option to update the secondary site.
File information
File information is available in the following downloadable text file:
Release history
- November 2026: Initial update release