Update rollup for System Center Configuration Manager current branch, version 1806

Si applica a: System Center Configuration Manager (current branch - version 1806)


This article describes the issues that are fixed and additional hotfixes that are included in the current update rollup for Microsoft System Center Configuration Manager current branch, version 1806.

Issues that are fixed

  • The MP_GetSuperPeerContentLocations peer cache stored procedure is optimized to improve SQL performance and accuracy of results.
  • Multiple improvements are made to the Lifecycle Dashboard.
  • After you change a task sequence that contains a hidden variable, that variable may be overwritten by incorrect information that causes the task sequence not to run.
  • Third-party software update catalogs or file contents that contain a space in the URL or file name do not get synchronized or published.

  • When changes are made to controlled folders access, the Exploit Guard policy doesn't take effect on clients as expected.
  • After you update to Configuration Manager current branch, version 1806, the Browse button is incorrectly disabled for Product Codes in Windows Installer properties in the Configuration Manager console.
  • When the An administrator must approve a request for this application on the device option is enabled, Software Center displays an approved application for a given user on another device. For example, if a user request for an application from computer Desktop1 is approved, that same request is listed as approved when that user logs in on computer Desktop2.
  • The SMS Executive service (smsexec.exe) may stop unexpectedly when it processes client health data.
  • The uninstall process fails for a high availability site that was previously configured as the passive server. The FailOverMgr.log contains entries that resemble the following:
  • After you add an Azure Active Directory tenant to the Configuration Manager console, the site database may grow unexpectedly. This issue occurs because of the addition of extraneous audit information to the site database.
  • Suspending a phase deployment that's configured to start sometime in the future may cause the client to start that deployment instead.
  • Installation of a passive high availability site server may fail if the target server is configured to use a named instance of the site database in an Always On Availability Group. Additionally, errors that resemble the following are recorded in the Configuration Manager Setup log:
  • The Windows Server Update Services (WSUS) Configuration Manager component on a site server doesn't communicate with a remote WSUS Server when a proxy is configured for that site server.
  • Certificate selection parameters are not recognized during new client installation if they are passed by using a configuration file.
  • After disabling the Server Group option for a collection, member clients incorrectly look for a deployment lock. When this issue occurs, the client can't install updates.
  • After you update to Configuration Manager current branch, version 1806, co-managed devices may not run deployments that are targeted to users.
  • The Install software packages according to dynamic variable list option is automatically selected. This issue occurs after you change an existing task sequence in the task sequence editor to add Install Package actions.
  • Trying to add a Run Command Line step to an existing task sequence that updates the operating system fails. Additionally, an error that resembles the following is displayed in the Task Sequence Editor:
  • The Configuration Manager console may stop unexpectedly when you try to open a new window, such as the Task Sequence Editor window.
  • The promotion of a passive site server to active mode may fail. This issue can occur if the installation of the SDK provider on the passive server overwrites information in the SMS registry key.
  • After the Configuration Manager client is installed, the following registry key may still contain data. This leftover data can interfere with future management by either Configuration Manager or Microsoft Intune.


  • The Adjust the download speed to use the unused network bandwidth (Windows LEDBAT) distribution point property doesn't work as expected in Configuration Manager current branch, version 1806.

    Note After this update rollup is applied, new distribution points that use this property function as expected. However, for existing distribution points, you must disable and then re-enable this property in order for those existing distribution points to function correctly.

Additional hotfixes included in this update rollup

  • 4465865 Software updates aren't download in a Configuration Manager environment if WSUS is disconnected.

Known issues

  • After this update rollup is installed, the Configuration Manager console may not open. This issue occurs if there's a provider that's remote to both the site server and the server that's running SQL Server for a given site. Additionally, errors that resemble the following are recorded in the Smsprov.log file when you try to open the console in this scenario:

    To resolve this known issue, set the following registry value to 0 (zero) on the remote provider computer:


    After the registry change is made, restart the Windows Management Instrumentation (WMI) service on the provider computer.

  • After this update rollup is installed, the "Lifecycle 01A - Computers with a specific software product" report returns an error that resembles the following:

Update information for System Center Configuration Manager, version 1806

This update is available for installation in the Updates and Servicing node of the Configuration Manager console.

Note This update also applies to customers who are running Configuration Manager version 1806, first wave.

If the service connection point is in offline mode, you must reimport the update so that it's listed in the Configuration Manager console. See Install in-console Updates for System Center Configuration Manager for detailed 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, 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. Configurations and settings for the secondary site aren't 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 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, the site hasn't installed all the fixes that were applied to the primary site, and you should use the Recover Secondary Site option to update the secondary site.

Update replacement

This update replaces previously released update KB 4346645 or KB 4459354, depending on the different first wave version.

For first wave customers: After this update rollup is applied, update KB 4346645 or KB 4459354 may still appear in the Updates and Servicing with a state of “Ready to Install.” You can safely ignore this display.

File information

The English version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.


Learn about the standard terminology Microsoft uses to describe software updates.