[Fix] List of SCCM 1806 Known Issues – Documented

Let us learn about [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 understand how to install SCCM 1806 hotfix.

The Microsoft SCCM team has already fixed SCCM 1806 known issues.

Are you looking for SCCM 1810 Known issues?

[Fix] List of SCCM 1806 Known Issues – Documented

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

Patch My PC

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 has 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.

SCCM updates and servicing are intelligent enough to filter out unwanted updates and 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 the previous update, KB 4346645 or KB 4459354, depending on the different SCCM first wave versions.

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
[Fix] List of SCCM 1806 Known Issues – Documented 2

List of SCCM 1806 Known Issues

The 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 area 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 are set to SCCM, and pilot collection is empty.
  12. CRP certificate revocation is slowly processing and blocking the main thread in SMS_CERTIFICATE_MANAGER.
  13. On upgrade, if you have deployments requiring 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. The 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 site’s performance 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 was reported as critical because of a backlog of Script state messages with no output data reported as corrupt.
  20. Download fails when you use the 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 the Distribution Manager runs 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 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 is without WDS enabled.
  26. CMPivot returns NULL if any registry entity values are NULL.
  27. BCP for BGB_NetworkInfo lives data fails if there is the same subnet for the same IP address and 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 begin at the same time. SMSTS.log shows that the password is incorrect even though the wizard is not displayed and no password is set. SCCM 1806 Known Issues fixed.
  30. The state message files in the management point staging folder may not process on a passive site server.
  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 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 the 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 area remains in either an “active” or “deleting” state.
  39. After updating 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. Maybe this will help AutoPilot Rip and Reuse where the client shows as MDM/ConfigMgr Agent managed rather than MDM managed client.
  42. Adjusting 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, which 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 controlled folder access, the Exploit Guard policy does not affect 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 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 listed as approved when logged 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 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. The site database may grow unexpectedly after you add an Azure Active Directory tenant to the SCCM console. This issue occurs because of the addition of extraneous audit information to the site database.
  55. Suspending a phased 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 using a configuration file.
  59. Member clients incorrectly look for a deployment lock after disabling the Server Group option for a collection. When this issue occurs, the client cannot install updates.
  60. After you update SCCM 1806, co-managed devices may not run deployments targeted to users.
  61. The Install software packages, according to the dynamic variable list option, are automatically selected. This issue occurs after changing 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 the 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


37 thoughts on “[Fix] List of SCCM 1806 Known Issues – Documented”

  1. hi sir,i am try to install the sccm client in a test machine but the sccm client is not installed in a test machine.i tried many ways but the sccm client is not installed in a test machine.please help me on this sir


  2. Hi Anoop,

    Can you please guide me how I can fix KB4465865 installation error?
    When I am trying to install Hotfix Rollup on SCCM 2016 (1806) facing following error:
    Failed to apply update changes 0x80004005
    Error information persisted in the database.
    ERROR: Failed to process configuration manager update.

  3. Why the KB # 4462978 (10/25/2018) is lower than KB # 4465865 (10/02/2018) ?
    Any interaction between both KBs?
    I have a lot of issues with Software Updates and always the answer looks like KB4462978… (KB4465865 already installed)

    • Additional hotfixes included in this update rollup KB 4462978 is KB 4465865 Software updates aren’t download in a Configuration Manager environment if WSUS is disconnected.

      Are you facing the issue like the client is not getting software updates ? The SCCM 1806 client version is updated KB 4462978? If so, I have heard someother customer that they also faced similar issue after upgrade. I would try to reinstall SUP but raising a ticket with MS would be better option.

  4. Very good update.
    I have an issue, like a known issue sl no 39. but my sccm version is 1702.While downloading windows 10 update binaries .cab files getting downloaded but along with a blank express file is getting downloaded.Also in console download status is NO.
    In patchdownloader.log –ERROR: DownloadContentFiles() failed with hr=0x80070002 $$
    Can you please guide me to resolve this issue.

  5. No connectivity issues.Other OS updates are getting downloaded from same source.but problem with windows 10 updates.
    Also in shared folder windows 10 updates binaries getting downloaded along with blank express files.Also download status is NO.

  6. Hi Anoop, are you guys maybe aware of a possible Windows 10 1809 issue whereby adding a task sequence to upgrade clients. It doesn’t cache the latest Windows 10 at all on the clients. I still have my 1803 Task sequence and if I redeploy it to the same test group, it cache’s fine but not on 1809. Redone the whle thing and matched settings with my 1803 and nothing

    Latest SCCM version installed as well 1806 kb4462978

  7. I have updated my site server to the latest 1802 update but when trying to update to 1806 I get a .NET Framework Unhandled exception:

    Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit the application will close immediately.

    Value of ‘01/01/40 00:00:00’ is not valid for ‘Value’. ‘Value’ should be between ‘MinDate’ and ‘MaxDate’
    Parameter name: Value

    Any help would be appreciated!

      • Hi Anoop,

        I have done a restart as a test already and there is no difference.
        the error happens immediately after right clicking the update in the Updates and Servicing pane.

        I get 4 entries in the Application event viewer, details for each are:
        1. Old ClientPilotingConfigs: IsEnabled = False, IsAccepted = False

        2. Old ClientPilotingConfigs: TargetCollectionID is NULL

        3. Application: Microsoft.ConfigurationManagement.exe
        Framework Version: v4.0.30319
        Description: The process was terminated due to an unhandled exception.
        Exception Info: System.InvalidOperationException
        at System.ThrowHelper.ThrowInvalidOperationException(System.ExceptionResource)
        at System.Collections.Generic.List`1+Enumerator[[System.__Canon, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e119]].MoveNextRare()
        at System.Collections.Generic.List`1+Enumerator[[System.__Canon, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e119]].MoveNext()
        at Microsoft.ConfigurationManagement.AdminConsole.ScopeNodeBase.Dispose(Boolean)
        at Microsoft.ConfigurationManagement.AdminConsole.SnapIn.Dispose(Boolean)
        at Microsoft.ConfigurationManagement.AdminConsole.Console.Dispose(Boolean)
        at Microsoft.EnterpriseManagement.ConsoleFramework.ConsoleApplication.ApplicationExit(System.Object, System.EventArgs)
        at System.Windows.Forms.Application.RaiseExit()
        at System.Windows.Forms.Application+ThreadContext.Dispose(Boolean)
        at System.Windows.Forms.Application+ThreadContext.ExitCommon(Boolean)
        at System.Windows.Forms.Application.ExitInternal()
        at System.Windows.Forms.Application+ThreadContext.OnThreadException(System.Exception)
        at System.Windows.Forms.Control.WndProcException(System.Exception)
        at System.Windows.Forms.Control+ControlNativeWindow.OnThreadException(System.Exception)
        at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)

        4. Faulting application name: Microsoft.ConfigurationManagement.exe, version: 5.1802.1024.1000, time stamp: 0x5a979ea2
        Faulting module name: KERNELBASE.dll, version: 10.0.14393.2636, time stamp: 0x5bda8043
        Exception code: 0xe0434352
        Fault offset: 0x000db0b2
        Faulting process id: 0x1904
        Faulting application start time: 0x01d490e1f835bd78
        Faulting application path: D:\Program Files\Microsoft Configuration Manager\AdminConsole\bin\Microsoft.ConfigurationManagement.exe
        Faulting module path: C:\Windows\System32\KERNELBASE.dll
        Report Id: 487de2cd-a04f-4155-99f4-934c0bd7eb7b
        Faulting package full name:
        Faulting package-relative application ID:

  8. Hi Sir,

    I am trying to deploy System Centre Endpoint protection update signatures through SCCM. But the SCEP is not getting updated.
    I have UNC (\\Server Name\Packages and Applications\SCEPUPDATES\x64\x64)path where i update the signature through a script via Task scheduler
    ID:2001 Source Microsoft Antimalware
    Message: %Microsoft Antimalware has encountered an error trying to update signatures. New Signature Version: Previous Signature Version: Update Source: %File Share Update Stage: %Search Source Path: \\MM01-MCCS-01\Packages and Applications\SCEPUPDATES\x64\x64 Signature Type: %AntiSpyware Update Type: User: NT AUTHORITY\NETWORK SERVICE Current Engine Version: Previous Engine Version: 1.1.15400.5 Error code: 0x80070002 Error description: The system cannot find the file specified.

    • I will try to redistribute the content if the issue is for all the devices. But if the issue is only for some devices, then it’s better to go through client side troubleshooting to get more details. Try to reinstall the client ect

  9. Hi Sir,

    This issue is only seen in the servers which doesnt have internet connectivity and i had given internet access to this servers then the SCEP is up to date but when i take off the internet connection above error comes up and idoesnt gets the update. is there any version issue? which can lead to this?

  10. does anybody notice after the upgrade the custom settings in discovery are being reset to default and other client settings too ? is that normal and should happen ?

      • So Far I noticed this under user discover. under search option we had “Discover objects within Active Directory Groups” unchecked. after the upgrade i found this options is checked.
        for the client settings portion I found that “use the new software center” was set to NO after the upgrade it has been reset to yes.

  11. Hi Anoop sir,

    Please assist for resolution.

    Here we are upgrading client 1202 to 1806. Getting download update connecting to Server.
    By console thorough getting error but when we tried clean and install manual its working means client upgrading to 1806.

    How to fix . Here more than 7k stuck with same error code.. please help..

    Dinesh G

  12. Hi Anoop,
    I had recently Install SCCM 1902 version on test lab, installation went fine, after that I tried to discover my client nothing has updated in the log files. During troubleshooting I checked components status on the console all discover agent type shows unknown and status shows unknown at the same time I have checked SMS_providers type and status shows unknown.


Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.