Update Rollup for Microsoft Endpoint Configuration Manager current branch, version 1910

Applies to: Microsoft Endpoint Configuration Manager (current branch)


This article describes issues that are fixed in this update rollup for Microsoft Endpoint Configuration Manager current branch, version 1910. This update applies both to customers who opted in through a PowerShell script to the early update ring deployment, and customers who installed the globally available release.

For additional information on changes in Configuration Manager version 1910, refer to:
What’s new in version 1910 of Configuration Manager current branch

Summary of changes in Microsoft Endpoint Configuration Manager current branch, version 1910

Issues that are fixed

  • The Configuration Manager console may terminate unexpectedly when viewing the properties of a third-party software updates catalog. 


  • Local policy instances are not copied to Actual (current) policy on clients if there are no policies downloaded from the site server.


  • Distribution Points incorrect display a failed status for deployment packages. This occurs if the Distribution Point is removed from a Distribution Point group while it is in maintenance mode.


  • The SCCMPXE service consumes more memory than expected after updating to Configuration Manager version 1910.


  • The Create Cloud Management Gateway Wizard only displays the first 50 Subscription ID's for a given account. Any subscriptions beyond the first 50 are not available for use in the wizard.


  • Powershell.exe terminates unexpectedly when importing modules using the Connect via PowerShell option in the Configuration Manager console.


  • The BitLocker drive status shows as non-compliant when the drive is encrypted. This occurs when using Microsoft BitLocker Administration and Monitoring (MBAM) policies and the policies are set to disabled or not configured.


  • Clients within the boundaries of a secondary site repeatedly send registration requests until the secondary site server is restarted. After a client is successfully registered, a message resembling the following is recorded in the ClientIDManagerStartup.log file, indicating that the client will register again.



  • Personal view preferences for the Configuration Manager console are lost when connecting back to the console via a Remote Desktop session.


The following additional issue is resolved with the installation of this update rollup.

  • KB 4542722 SQL database compatibility level changes after applying Configuration Manager updates

Additional hotfixes contained in this rollup

  • KB 4535819 Update for Microsoft Endpoint Configuration Manager version 1910, early update ring
  • KB 4538488 Clients immediately upgrade after updating to Configuration Manager current branch, version 1910
  • KB 4538166 Client update for Configuration Manager current branch, version 1910
  • KB 4537369 The Delete Aged Discovery Data task incorrectly removes active records in Configuration Manager

Update information for Microsoft Endpoint Configuration Manager current branch, version 1910

This update is available in the Updates and Servicing node of the Configuration Manager console for environments that were installed by using early update ring or globally available builds of version 1910.

Members of the Configuration Manager Technology Adoption Program (TAP) must first apply the private TAP rollup before this update is displayed.

To verify which build is in use, look for a Package GUID by adding the Package GUID column to the details pane of the Updates and Servicing node in the console. The update applies to installations of version 1910 from packages that have the following GUIDs:

  • AC004944-98BC-44C2-A129-320285EC683F
  • 6630E282-AA3F-4921-A65D-4CF493C42066
  • 5AF6B247-224C-49AB-BE48-8909B3689D5E
  • B1E6FEC0-5A6E-4B56-8F27-7406F9A79CFB
  • 0BB82139-0DC3-4B18-B219-97FB2EFD9E56
  • E2F7B2F9-4828-4650-9144-5DC7956781B7
  • 4CE24C49-E6B0-4B4F-9AD8-CA31FF269F23

The update is also applicable to the following package GUID with the private TAP rollup installed:

  • 3B4824FF-02FC-40B8-95AB-2AE986B0B63F

Restart information

You do not have to restart the computer after you apply this update.

Additional installation information

After you install this update on a primary site, pre-existing secondary sites must be manually updated. To update a secondary site in the Configuration Manager console, click Administration, click Site Configuration, click Sites, click Recover Secondary Site, and then select the secondary site. The primary site then reinstalls that secondary site by using the updated files. Configurations and settings for the secondary site are not affected by this reinstallation. The 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 a value of 1 is returned, the site is up to date, with all the hotfixes applied on its parent primary site.

If a value of 0 is returned, the site has not installed all the fixes that are applied to the primary site, and you should use the Recover Secondary Site option to update the secondary site.