Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


Release version 1810 of System Center Configuration Manager Current Branch contains fixes and feature improvements.

The "Issues that are fixed" list is not inclusive of all changes. Instead, it highlights the changes that the product development team believes are the most relevant to the broad customer base for Configuration Manager. Many of these changes were made in response to customer feedback about product issues and product improvements.


Issues that are fixed and improvements

Configuration Manager console

  • The Configuration Manager console may terminate unexpectedly after regular editing of a large task sequence when you use the keyboard for navigation.


  • The update schedule for the All Systems collection is now configurable.


  • The drop-down list of Target Collections only shows collections that have 0 members in the Create Servicing Plan pane of the Windows 10 servicing dashboard. Selecting the Advanced settings shows all available collections as expected.


  • The Cloud Management Gateway Connection analyzer  terminates unexpectedly if a .cer certificate file is selected instead of a .pfx file. With this update only .pfx files can be selected.


  • Adding a script that has parameters by using the Run Scripts feature may result in an exception that resembles the following example in the Configuration Manager console:


    This implementation is not part of the Windows Platform FIPS-validated cryptographic algorithms.


Software Updates Management

  • The “No deployment package” option is not saved when modifying an existing automatic deployment rule (ADR).


  • The software update deployment status that's displayed in the Configuration Manager console doesn't match the status that's displayed in Software Center on the client. This issue occurs if an assigned update is installed manually in Software Center while a maintenance window is pending.



  • The “Status of a specified Package and Program Deployment” report displays incorrect data if the Deployment Date selected as a parameter does not match the Deployment Date of the selected program.


  • The values displayed for Client OS Distribution and Co-management Status do not match as expected in the co-management dashboard.


  • The Client Data Sources report returns an error message resembling the following example:

    An error has occurred during report processing. (rsProcessingAborted)
    Query execution failed for dataset 'DataSet0'. (rsErrorExecutingCommand)


  • Multiple improvements are made to Asset Intelligence-related data for reports that contain SQL licensing information.


  • Applications that contain nonprintable characters in their titles can't be viewed correctly in Add or Remove Programs data-based reports. This includes built-in reports such as Count of all instances of software registered by using Add or Remove Programs and customer reports.


Remote Tools

  • The Configuration Manager Remote Control service is disabled after an in-place upgrade Task Sequence is used to upgrade a Windows 10 client.



  • Removing the first or last item in the Controlled folder access component of an Exploit Guard policy doesn't take effect on client computers.


  • Client site assignment may revert to a prior value during upgrade or repair if the site code was changed after the original installation.


  • Remote viewing of the WMI class SMS_Desiredconfiguration fails with a generic error after you update clients to Configuration Manager current branch, version 1806.


Site Systems

  • The site recovery process is improved for environments by using SQL Server Always On availability groups.

  • When a Software Update Point (SUP) is installed on a server in a remote domain that uses a different fully qualified domain name (FQDN), the SUP won't connect to Microsoft Update. This issue occurs if the primary site server is configured to use a proxy server to communicate with Microsoft Update. The site server and remote SUP attempt to communicate by using the proxy. Error messages that resemble the following example are recorded in the WCM.log file:

    System.Net.WebException: The proxy name could not be resolved: ''~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~


  • During installation or upgrade of a primary site, the ConfigMgr_DViewAccess local security group isn't added as a user in the site SQL database. This group is created when you use distributed views for database replication between sites.


Software Distribution and Content Management

  • Content isn't sent to a cloud distribution point if it's a member of a distribution point group.


  • If the Package Transfer Manager component can't connect to the Windows Management Instrumentation (WMI) service on a distribution point, it will retry indefinitely until it can connect successfully.


  • Pre-production (pilot) client files are copied to distribution points even if pre-production client deployment isn't enabled for the site.


  • An application deployment type that includes a backslash (“\”) in the name stops Configuration Item (CI) processing on targeted clients. Error messages that resemble the following example are recorded in the CIDownload.log file:

    hr == WBEM_S_NO_ERROR, HRESULT=87d00235
    Compiler lPhaseError: 2, ObjectNum: 0, hRes: 80044007


  • Content transfers between a client computer and a cloud-based distribution point fail when you use the Background Intelligent Transfer Server (BITS), and the client computer is restarted during the transfer. The installation state will stay listed as “Downloading” until the job times out.


  • After you update to Configuration Manager current branch, version 1806, attempts to stream App-V applications from a distribution point fail. Error messages that resemble the following are recorded in the Appenforce.log on the client:

    Add-AppvClientPackage : Application Virtualization Service failed to complete requested operation.
    Operation attempted: Retrieve Package and Version IDs From Package URL.
    AppV Error Code: 0C80072EF3


  • When you move a content library to a new server, the process may take longer than expected or stop responding and display a status of "In Progress" without finishing. This issue may occur if changes are being made to the original content library during the move, or there are orphaned files in the original content library.


Operating System Deployment

  • The following tabs are missing from Boot Image properties if the installed version of the Windows Assessment and Deployment Kit (ADK) doesn't match the version of the boot image:

    • Images

    • Drivers

    • Customization

    • Optional Components

    The absence of the Images tab prevents administrators from loading relevant boot image data after they update the image by using the latest ADK.

  • Multicast deployment of an operating system images fails if the client and distribution point are in different DNS zones. Error messages that resemble the following example are recorded in the mcsisapi.log file:

    Encountered error transferring file (0x800706BA).


  • The download of task sequence content from an HTTPS-enabled distribution point in the full operating system may take longer than expected. This issue occurs when the content contains multiple files because of certificate checks that occur at the file level instead of at the package level. This issue is fixed in Configuration Manager current branch version 1810 only when boot images and client binaries are updated to version 1810.


Hotfixes that are included in this update

  • KB 4471892 PXE Responder doesn't work across subnets in Configuration Manager 1806


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


Dependency changes

The following dependent components that are included with Configuration Manager version 1810 are updated to the specified version:

  • SQL Native Client to version 11.4.7001.0

  • SQL Server Express to version 13.2.5026.0

  • microsoft.aspnet.odata.versioning.dll to version 2.2.6579.17762

  • microsoft.aspnet.webapi.versioning.dll to version 2.3.6665.24663


Learn about the terminology Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!