[Fix] List of SCCM 1806 Known Issues – Documented

SCCM 1902 Production Upgrade GuideMicrosoft released a couple of update rollups (hotfixes) for the latest production version of SCCM 1806. In this post, we will see the SCCM 1806 known issues and how to fix those known issues. The Video tutorial will help you to understand how to install SCCM 1806 hotfix. SCCM 1806 known issues are already fixed by Microsoft SCCM team.

Are you looking for SCCM 1810 Known issues?


Patch My PC

[Related PostSCCM 1902 Production Upgrade Guide, How to Upgrade SCCM Infra to 1806 Production Version and SCCM 1806 New Features Changes a Video Walkthrough]

Fix to SCCM 1806 Known Issues?

Microsoft fixed many issues in the latest version SCCM 1810. Also, Microsoft updated the fixed list of issues in the KB 4482169.

Microsoft already released two hotfixes to fix all the documented known issues for the 1806 version of SCCM. So all the issues highlighted in the post are already fixed with the latest hotfixes or the latest version of 1806.

1E Nomad

SCCM updates and servicing is intelligent enough to filter out unwanted updates hotfixes from your SCCM console. So most probably if your SCCM  environment requires an update, it would be visible in your SCCM console.

Updated on 25th Oct

Microsoft Released RollUP update KB 4462978  for SCCM 1806.


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

Updated on 2nd Oct 

Microsoft released another hotfix for SCCM 1806.


How to Confirm Hotfix is Required for SCCM Environment?

You can confirm whether the SCCM 1806 hotfix is required for your environment by comparing the SCCM updates and servicing package guide. To verify which wave build is installed, look for a package GUID by adding the Package GUID column to the details pane of the Updates and Servicing node in the SCCM console.

SCCM 1806 Known Issues

List of SCCM 1806 Known Issues

Following list provides SCCM 1806 Known issues. I will try to update it whenever Microsoft releases new hotfixes.

  1. After the WDS-less PXE responder service is configured after an upgrade to SCCM 1806, it may reject PXE-boot requests from clients when the management point (MP) is remote.
  2. Task sequences that have a restart action before an Install Packages action may fail. SCCM 1806 Known Issues fixed.
  3. Unable to delete a secondary site. After the deletion action, the site remains in either an “active” or “deleting” state
  4. CMPivot cannot run a PowerShell script that contains a command to retrieve a registry entry if the registry contains a NULL value.
  5. The SCCM console crashes if you create or edit an ADR and set the deployment package to “No deployment package.”
  6. CMPivot is missing the “not like” operator.
  7. CMPivot fails to run a PowerShell script that contains a command to retrieve a registry entry if the registry value contains a NULL.
  8. Ccmexec crashes continuously when Pull DPs are installed.
  9. OfflineServicingMgr fails to find the content library location when the Content Library is on a Universal Naming Convention (UNC) path.
  10. OfflineServicingMgr leaks handle and cause a decrease in performance if it fails to find the content library location on a UNC path.
  11. When you edit an existing co-management policy, instead of the changes being saved, the policy is reset to the default state of No AutoEnroll, all workloads set to SCCM, and pilot collection is empty.
  12. CRP certificate revocation is processing slowly and is blocking the main thread in SMS_CERTIFICATE_MANAGER.
  13. On upgrade, if you have any deployments that require approvals that reference built-in CIs created before 1706, you will see significant SQL I/O and high CPU utilization on the MPs as the CIs and deployments are updated.
  14. Phased Deployment Status Wizard shows multiple rows for the same phase with inconsistent data when a collection has machines spread across multiple sites.
  15. Count of AADJoined and HybridAADJoined may be incorrect on the Co-Management dashboard.
  16. Excessive client request time-outs on the cloud management gateway.
  17. After an upgrade to 1806, the performance of the site may be decreased with high I/O and CPU use by sp_UpdResPolicyMap_PolicyAssignment.
  18. Super peers may fail to download partial content when the management point is remote.
  19. State message component SMS_STATE_SYSTEM reported as critical because of a backlog of Script state messages with no output data reported as corrupt.
  20. Download fails when you use CCM client Delta Download channel to download express updates full files.
  21. The process MP_GetSuperPeerContentLocations stored proc may cause decreased SQL performance and block threads.
  22. Pull DPs may fail to be upgraded because MOFCOMP silently fails when Distribution Manager run it. If the Pull DPs are not upgraded, content cannot be downloaded.
  23. The online client status chart on the CMG Dashboard does not aggregate hourly data correctly from multiple MPs.
  24. When you create an SRM based CMG or CDP by using an existing resource group, the region of the resource group is used to create the resources regardless of the region that you specified.
  25. DP upgrade fails If PXE without WDS enabled.
  26. CMPivot returns NULL if any registry entity values are NULL.
  27. BCP for BGB_NetworkInfo live data fails if there is a duplicate subnet for the same IP address and same client.
  28. CMG HTTP listener stops because of an HttpListenerException.
  29. After WDS-Less PXE is enabled, some clients may not start Task Sequence Wizard because a password is incorrectly expected when multiple clients start at the same time. SMSTS.log shows that the password is incorrect even though the wizard not displayed and no password is set. SCCM 1806 Known Issues fixed.
  30. On a passive site server, the state message files in the management point staging folder may not process.
  31. The WDS-less PXE responder service, configured after upgrade to SCCM 1806, may reject PXE-boot requests from clients when the management point (MP) is remote.
  32. AtomicUpdate and BundledUpdate metadata used for delta download can get truncated. This causes Unified Update Platform (UUP) updates not to be downloaded.
  33. When the SCCM generated certificate option is selected for the site, and a client fails to download content because it does not have the client public key infrastructure (PKI) certificate if the client is restarted it will still fail to download content even if token-based content locations are available.
  34. After the 1806 upgrade, SCCM clients fail to send client or Management Point (MP) communication status Fallback Status Point (FSP) messages.
  35. When content that downloads from delta download or CMBITSMgr, the optimal content location is not chosen for all content within a package.
  36. Some client state messages may not be sent, resulting in some reports such as co-management, Windows Upgrade for Business and deployment upgrade reporting being out of sync. SCCM 1806 Known Issues fixed.
  37. An Internet-only AAD-joined device cannot register if an MP was removed from cloud management gateway.
  38. Task sequences that have a restart action before an Install Packages action may fail.
    Unable to delete a secondary site. After the deletion action, the site remains in either an “active” or “deleting” state.
  39. After you update to SCCM, version 1806, software updates do not download. This failure occurs only in environments that use Windows Server Update Services (WSUS) on a disconnected (air gapped) network.
  40. For software updates that contain express installation files, SCCM synchronizes the Express.cab file and distributes it to the client. This behavior occurs even if the client does not require the Express.cab file for a given deployment. SCCM 1806 Known Issues fixed.
  41. After the SCCM client is installed, the following registry key may still contain data. This leftover data can interfere with future management by either SCCM or Microsoft Intune. May be this will help AutoPilot Rip and Reuse where the client shows as MDM/ConfigMgr Agent managed rather than MDM managed client.
  42. The Adjust the download speed to use the unused network bandwidth (Windows LEDBAT) distribution point property does not work as expected in SCCM 1806. SCCM 1806 Known Issues fixed.
  43. 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.
  44. The SCCM console may stop unexpectedly when you try to open a new window, such as the Task Sequence Editor window.
  45. The MP_GetSuperPeerContentLocations peer cache stored procedure is optimized to improve SQL performance and accuracy of results.
  46. Multiple improvements are made to the Lifecycle Dashboard.
  47. After you change a task sequence that contains a hidden variable, that variable may be overwritten with incorrect information that results in the task sequence failing to run.
  48. Third-party software update catalogs or file contents that contain a space in the URL or file name do not synchronize or publish.
  49. When changes are made to a controlled folders access, the Exploit Guard policy does not take effect on clients as expected. SCCM 1806 Known Issues fixed.
  50. After you update to SCCM 1806, the Browse button is disabled incorrectly for Product Codes in Windows Installer properties in the SCCM console.
  51. 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 requests and is approved for an application from computer Desktop1, that same request is are listed as approved when that user logs into computer Desktop2. SCCM 1806 Known Issues fixed.
  52. The SMS Executive service (smsexec.exe) may stop unexpectedly when it processes client health data.
  53. The uninstall process may fail for a high availability site that was previously configured as the passive server. The FailOverMgr.log contains entries that resemble the following:  Failed to get installation directory for site server {old_site_server_name}
  54. After you add an Azure Active Directory tenant to the SCCM console, the site database may grow unexpectedly. This issue occurs because of the addition of extraneous audit information to the site database.
  55. Suspending a phase deployment configured to begin sometime in the future may result in the client starting that deployment instead.
  56. 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 SCCM Setup log: CTool::ConvertNETBIOSToFQDN: getaddrinfo failed on {server_name}\{instance_name}, WSA error = 11001
  57. The Windows Server Update Services (WSUS) SCCM component on a site server does not communicate with a remote WSUS Server when a proxy is configured for that site server.
  58. Certificate selection parameters are not recognized during new client installation if they are passed by using a configuration file.
  59. After disabling the Server Group option for a collection, member clients incorrectly look for a deployment lock. When this issue occurs, the client cannot install updates.
  60. After you update to SCCM 1806, co-managed devices may not run deployments targeted to users.
  61. 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.
  62. 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:

ConfigMgr Error Object:
Instance of SMS_ExtendedStatus
Description = “Failed to validate property TargetDrive.”;
ErrorCode = 2147500037

63. Replication failed between CAS and Primary site as Site Data “Site Server Monitor Status” was failing with following error in rcmctrl.log:

Error: Exception message: [Cannot drop type ‘SCCM_DRS_AlwaysOn_Server_MonitoringStatus_TYPETEMP’ because it is being referenced by object ‘spUpsertAlwaysOn_Server_MonitoringStatus’. There may be other objects that reference this type.] SMS_REPLICATION_CONFIGURATION_MONITOR  


1806 Slow Ring – https://support.microsoft.com/en-us/help/4459354/interoperability-update-for-system-center-configuration-manager

1806 Fast Ring – https://support.microsoft.com/en-gb/help/4346645/update-for-system-center-configuration-manager-version-1806-first-wave