SCCM 1906 Known Issues – List of Fixes

Let’s discuss the SCCM 1906 Known Issues List and FIXES. SCCM 1906 is in the slow ring now, but the SCCM 1906 update will be available for all SCCM infrastructure with the online Service Connection Point.

You should also have versions SCCM 1806SCCM 1810, or SCCM 1902. In this post, you will learn more about SCCM 1906 known issues.

This post is to help SCCM admins easily go through a list of SCCM 1906 Known Issues production versions. Most of the highlighted issues are collected via social media channels and Microsoft documentation.

Related PostsSCCM 1902 known issues & SCCM 1810 Known Issues

Patch My PC

NOTE! – These issues are not blockers for SCCM 1906 production upgrade

List of SCCM 1906 KBs

  • Fix Download Issues with SCCM 1906 Latest Rollup Hotfix
  • KB4529827 – Configuration Manager clients incorrectly detect co-management state
  • KB4529905 – Delays in content distribution in ConfigMgr CB, version 1906
  • KB4528414 – ConfigMgr SCCM console displays out-of-date Endpoint Protection Definition version and last update time
  • KB4517869 – Update Rollup for SCCM CB 1906
  • KB4516430 (Fixes issues for SCCM 1906 Fast ring)
  • KB4514258 – Summary of changes in SCCM 1906
  • KB4515740 – Custom security roles lose folder permissions
  • KB4517137 – The computer hangs at “Just a moment” in a debug deployment for an SCCM task sequence

SCCM 1906 Known Issues Not Fixed Yet?

According to the Microsoft documentation, there are some SCCM 1906 known issues. Some of them are just warnings, so you can ignore them and perform a workaround, as mentioned below.

NOTE! – All the SCCM 1906 Known Issues are FIXED with SCCM 1910 release. More details &

  • DPs show warning ⚠️, and it doesn’t go away? The reason could be old messages (2388-failed to validate pkg list) if DP were set up &pkg distr not finished when validation ran. Clean up tables distribution status/distributionpointmessages for message-id/laststatusMsgid=2388. More details on a Twitter thread
  • SCCM 1906 Deleted computer objects will not re-register (NOT Confirmed as a known issue?).
  • Peter blogged about the SCCM 1906 Azure AD Group Discovery bug. More details on his blog post –
  • SCCM 1906 Setup prerequisite warning on functional domain level on Server 2019
    • When installing the update SCCM 1906 in an environment with domain controllers running Windows Server 2019, the prerequisite check for functional domain level returns the following warning: –
    • [Completed with warning]:Verify that the Active Directory domain functional level is Windows Server 2003 or later
    • Workaround
      • Ignore the warning.
  • Azure AD user discovery and collection group sync don’t work after site expansion
    • If you then expand a standalone SCCM primary site to a hierarchy with an SCCM CAS, you’ll see the following error in SMS_AZUREAD_DISCOVERY_AGENT.log:
    • Could not obtain application secret for tenant xxxxx. If this is after a site expansion, please run "Renew Secret Key" from admin console.
    • Workaround
      • You can renew the key associated with the app registration in Azure AD. For more information, see Renew secret key.
  • Ben (@RealBenBruno) updated me about the SCCM 1906 & AirWatch Co-existence issue on Windows 10 devices. They have been engaged with Microsoft techs for over a month about this. Since updating to 1902 and 1906, if you run a 3rd party MDM (we are using AirWatch), SCCM disables its deployments and software center.

Fixed SCCM 1906 Known Issues with the latest Patches

The following are the known issues fixed with SCCM 1906 (SCCM 1906 Known Issues) slow ring version. More details available KB4516430 & KB4517869.

SCCM 1906 Known Issues - List of Fixes - Fig.1
SCCM 1906 Known Issues – List of Fixes – Fig.1
  • The SCCM console may terminate unexpectedly after reevaluating Management Insight rules or synchronizing third-party updates.
  • The Task Sequence Editor may return an Out of Memory error when trying to save large task sequences.
  • The policy for custom client settings does not define alternate content provider (ACP) settings as expected. After installing this update, affected customers should remove and recreate the original custom client settings.
  • Special characters, such as an apostrophe, cause the evaluation of application groups to fail in metadata. The SettingsAgent.log contains entries similar to the following.
    • Error 0x80040e14 occurred when executing ‘INSERT SettingProperties(SAId, Name, LanguageId, Value) VALUES(1, ‘InfoUrlText’, 0, ‘What’s new’)
  • Windows Server 2019 is Unknown in the Microsoft Defender Advanced Thread Protection dashboard.
  • Group membership data is removed if the Active Directory group discovery process fails with the following error recorded in the adgdis.log
    • INFO: Processing search path: ‘LDAP://.
    • ERROR: Decryption failed
    • ERROR: Failed to enumerate directory objects in AD container LDAP://<search path
    • The group membership data is restored after the discovery process runs successfully.
  • A management point cannot connect to a read-only replica in environments using SQL Server Always On availability groups.
  • Users in custom security roles can no longer access folders in the SCCM console.
  • The SQL view vDCMDeploymentNonCompliantRuleDetailsPerClientMachine is an incorrect version after reinitializing site replication. This affects the reporting of device compliance details in the SCCM console.
  • The installation retry will fail if the update to SCCM 1906 fails during the Upgrade SCCM database or Copy files steps. This occurs if Azure Active Directory User Discovery is configured in the environment. An error resembling the following is recorded in the CMUpdate.log.
    • Violation of UNIQUE KEY constraint ‘AADDiscovery_Settings_Ex_AK’. Cannot insert duplicate key in object ‘dbo.AADDiscovery_Settings_Ex’.
  • Administrators cannot disable the TLS 1.1 protocol after updating to version 1906.
  • The Summarize Installed Software Data fails with errors resembling the following recorded in the smsdbmon.log file.
    • Message Title – Cannot insert duplicate key row in object ‘dbo.INSTALLED_SOFTWARE_DATA_Summary’ with unique index ‘INSTALLED_SOFTWARE_DATA_Summary_idx_ByCode’.
  • The client registration process fails if the database contains duplicate client key data. This duplication may occur if the client’s certificate changes.
  • When using CMPivot from inside the SCCM console, a new client job is created after refining a query and running it again. This can delay results being returned and is more resource-intensive on client devices.
  • The Reassign Shared Distribution Point Wizard may fail with an unhandled exception, generating the following error text in the console.
    • The given key was not present in the dictionary.
  • The Site Maintenance Properties window does not show changes to the Enabled status of the site maintenance task without closing and reopening it.
  • The Connection Health dashboard in the Desktop Analytics Servicing node takes longer than expected to display results.
  • Alerts are displayed in English in the Monitoring node of the SCCM console even when another alert language setting is specified.

Issues Fixed with SCCM 1906 Upgrade

The following SCCM 1906 known issues fixes are the top reasons for upgrading SCCM 1906. Let’s check out the list of Fixes for SCCM 1906 known issues.

SCCM 1906 known issues will be discussed in the above section of this blog post.

SCCM Console

The following issues are fixed in SCCM 1906 production version. These were known cases of the previous versions of SCCM.

SCCM 1906 Known Issues - List of Fixes - Fig.2
SCCM 1906 Known Issues – List of Fixes – Fig.2
  1. The SCCM console can terminate with an unhandled exception when a non-English console is used to edit the Site System Status Summarizer database thresholds.
  2. The console’s Office 365 Client Management node may generate an exception when adding items to a new device collection. Exception text resembling the following is displayed.
    • Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException​ Not found, property = ResourceType​
  3. The Bulletin ID column is replaced with Article ID on default Software Update views in the SCCM console.
  4. The Management Insights dashboard may incorrectly show Long Term Servicing Branch (LTSB) or Long Term Servicing Channel (LTSC) versions of Windows 10 is unsupported.
  5. The SCCM console may terminate unexpectedly when nested folders are in the Packages node. This occurs when selecting the top-level folder after searching for data in the lower-level folder, such as a deployment package. An exception resembling the following is displayed on the screen.
    • System.NullReferenceException: Object reference not set to an instance of an object.
    • at
    • Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObjectBase.get_Item(String name)

SCCM 1906 Software Update Fixes

Following are the SCCM known issues fixed in the production version.

  • If the Include Microsoft Surface drivers and firmware updates option is enabled, the software update synchronization process takes longer than expected.
  • Software update content downloading may fail with a hash mismatch error. This occurs if BranchCache is enabled on the site server and the scope for multiple update packages is uploaded to a cloud-based distribution point.
    • Errors resembling the following are recorded in the ContentTransferManger.log on the client.
    • CCTMJob::_ProcessContentInfo – failed to verify hash (….
    • CCTMJob:_ProcessContentInfo failed. (0x87d00217)
  • Software update phased deployments will fail if the Suppress Reboot option is enabled for both workstation and server operating systems. The sms_PhasedDeployment.log file records an error resembling the following. Note that this entry is truncated for readability.
    • Exception: System.Data.SqlClient.SqlException (0x80131904): Parameter ‘@SuppressReboot’ was supplied multiple times.
  • Administrators cannot move updates from one software update group to another if they are not downloaded directly but distributed via BranchCache.
  • SUP synchronization in large environments may take much longer than expected due to inefficiencies in the SQL views and indexes used during the process.
SCCM 1906 Known Issues - List of Fixes - Fig. 3
SCCM 1906 Known Issues – List of Fixes – fig.3

SCCM 1906 Client Fixes

The following are the SCCM client-known issues fixed with the SCCM 1906 production release.

  • After removing the Application Catalog role from a site, clients may continuously request a non-existent policy from management. The associated web service policy is not correctly tombstoned on the client.
  • DataTransferService Jobs may fail if the client computer restarts while the job is still running. This occurs due to a timing issue during a computer shutdown that results in an incorrect status being returned for a Background Intelligent Transfer Services (BITS) job.
  • A client may become unmanaged if a wi-fi profile certificate is installed and the client is installed using the cloud management gateway.
  • After performing an in-place upgrade of the operating system from Windows Server 2012 R2 to Windows Server 2016, the SCCM Health Evaluation scheduled task no longer functions. Client check results are reported as failed, and an attempt to run the job from Task Scheduler results in the following error.
    • An error has occurred for task SCCM Health Evaluation. The error message is: A task or folder with this name already exists.
  • An update package’s automated deployment rule (ADR) may fail if software update synchronization removes expired content from the same box.
  • Clients are unable to download content or policies after repeated historical download failures. The data transfer service (DTS) jobs are suspended but restarting the SMS Agent Host (ccmexec) service causes downloads to resume. When the client is in this state, errors resembling the following are recorded in the DataTransferService.log on the client.
    • DTS job {guid} BITS job {guid 2} failed to download source file {filename}.exe to destination {client cache filename} with error 0x80072EE7
  • Users cannot search in the Software Center when the client operating system is configured with the Japanese locale and calendar.
  • User Deployments are not visible in the software center when the client communicates with a management point using a replica database.
  • A remote control session to an SCCM client will fail within a few seconds of connection. This occurs if the Teredo tunneling adapter is enabled on the client.
SCCM 1906 Known Issues - List of Fixes - Fig.4
SCCM 1906 Known Issues – List of Fixes – Fig.4

SCCM 1906 Site System Fixes

The SCCM 1906 known issues are listed below. The SCCM 1906 production version comes with the following fixes for Site system servers.

  • The SMSDPProv.log contains false errors when enhanced HTTP mode is not enabled. In this scenario, the error “Failed to verify if the cert is sccm issued, 0x800b0109” does not indicate a problem state and can be ignored.
  • The list of SMS providers is inconsistent after promoting a passive site server to an active one. The failover process succeeds, but remote providers are not listed in WMI or the Registry on the recently announced site server.
  • When custom client settings are used, changes to User Device Affinity (UDA) settings are not applied unless the “User device affinity usage threshold (minutes)” setting is also changed.
  • The SMS Executive service (smsexec.exe) may terminate unexpectedly when simultaneously distributing multiple large (multi-gigabyte) packages to a pull distribution point.

SCCM 1906 Reporting Issues

SCCM 1906 fixes the slowness in the two default reports listed below.

  • The following reports may take significantly longer (hours) to run than expected because of inefficiency in an associated SQL function.
    • Software Distribution Content / All Active Content Distribution
    • Software Distribution – Content / Application Content Distribution Status


We are on WhatsApp. To get the latest step-by-step guides and news updates, Join our Channel. Click here –HTMD WhatsApp.


Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is a Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc

23 thoughts on “SCCM 1906 Known Issues – List of Fixes”

  1. since i upgraded to 1906, i have to frequently restart WMI service on my SMSPROVIDER Servers in order to fix console crash issue.

    and i also can’t download software updates anymore (patchdownloader says :
    ERROR: DownloadContentFiles() failed with hr=0x80041013

      • Romain & Anoop, this happened in my environment as well. The 1906 upgrade installed the SMS Provider role on to my remote site database server for some reason. When I removed the SMS provider role from this server, software updates started working again.

  2. Hi,
    Are you a ware about the below:

    Current version: 1906
    Scenario: Bare-Metal deployment – PXE
    Windows 10 deployment task sequence finish successfully but then I notice the following issue on the client:
    1- SCCM agent is installed
    2- SCCM client not receiving any policy from SCCM
    3- SCCM client showing on console with No agent installed
    4- I found “unknown computer” record on console
    this issue didn’t occur when I’m using Task Sequence Media (USB)

  3. After upgrading 2 labs and Production to 1906 I noticed that the Details pane in Distribution Point Configuration Status takes a very long to load and occasionally comes back with no results (I believe the query is timing out)

    Sometimes when it does load it has lots of messages that did not show here prior to 1906 and they have no status icon. For instance it is getting Notification Server Messages

    The query shows in SQL as an Expensive Query. I was able to copy the actual query and run it directly in SQL Management Studio and it took 3 1/2 minutes to complete.

    Have you seen this behavior? Any idea if Microsoft is aware? I did send a frown this morning and am waiting to see if they reply.

    select all SMS_DPStatusDetails.DPName,SMS_DPStatusDetails.ID,SMS_DPStatusDetails.InsString1,SMS_DPStatusDetails.InsString10,SMS_DPStatusDetails.InsString2,SMS_DPStatusDetails.InsString3,SMS_DPStatusDetails.InsString4,SMS_DPStatusDetails.InsString5,SMS_DPStatusDetails.InsString6,SMS_DPStatusDetails.InsString7,SMS_DPStatusDetails.InsString8,SMS_DPStatusDetails.InsString9,SMS_DPStatusDetails.LastStatusTime,SMS_DPStatusDetails.MessageCategory,SMS_DPStatusDetails.MessageFullID,SMS_DPStatusDetails.MessageID,SMS_DPStatusDetails.MessageSeverity,SMS_DPStatusDetails.MessageState,SMS_DPStatusDetails.NALPath,SMS_DPStatusDetails.PackageID,SMS_DPStatusDetails.SiteCode,SMS_DPStatusDetails.StatusMsgID from vSMS_DPStatusDetails AS SMS_DPStatusDetails where SMS_DPStatusDetails.NALPath = N'[“Display=\\\”]MSWNET:[“SMS_SITE=”]\\\’ OPTION(USE HINT(‘FORCE_LEGACY_CARDINALITY_ESTIMATION’))

  4. I’m seeing an issue with a software deployment applied to an update group. If the deployment is “disabled”
    then “re-enabled” at runtime the client reports 0X87D00667 (No Service Window Available) Though Windows are present and available.

  5. Anyone seeing any issues on installing applications that 5 or more dependencies? Is there a setting/configuration in the SCCM console that I can tinker to resolve this issue?

  6. I also noticed that the Details pane in Distribution Point Configuration Status takes a very long to load and sometimes just time out with out any results.

    Is there any other way I can see which packages failed on DP?

  7. Anyone having issues with version 1910? I just updated and when the machines boots into PXE and gets to the PE environment it fails on the network connections section and won’t even get to the login screen we have setup. Only TS for 1809 and LTSC 2019 are deployed. I have updated the drivers on the boot images and re-deployed the boot images.

  8. Any updates on SCCM and Airwatch Co-management issue? Is there a workaround so I can deploy updates and applications SCCM 1906 to Airwatch enrolled mobile devices.

  9. Hello, we have updated SCCM 1910 & need to use Windows 10 devices with Airwatch & SCCM 1910 still facing Co-existence issue on Windows 10 device & SCCM disables it’s own deployments and software center.
    Is it fixed in MECM SCCM 1910. can you please guide.

    • I can say that even after un-enrolling from the 3rd party MDM (Airwatch) some computers software center began to work again. Some computers we actually had to go through the registry manually and delete anything that had Airwatch in the name in order to get the software center fixed.

      That all was a few months ago…

      I found out this week, that there are still a few computers having this issue. I made sure they were unenrolled from the MDM (which they were). I then made sure all of the Airwatch registry keys were deleted, and then i manually uninstalled the SCCM client, and reinstalled the client. After all of that, some of the machines are still showing in the logs that they are in co-existence mode… Is there any way to reset that??? or clear it?????

  10. Hi,
    I have an issue deploying applications to user collections, they can see it on Software Center but when clicking install it immediately fails.

    Using endpoint Url: http://P01VSCCM01.IPGLOBAL.CORP:80/CMUserService_WindowsAuth, Windows authentication (Microsoft.SoftwareCenter.Client.Data.ACDataSource+c at b__16_0) SCClient 7/07/2020 10:02:40 11 (0x000B)

    Exception caught in GetLocalInstallationInformationAsync, line 151, file X:\bt\1022889\repo\src\DataAbstractionLib\ACDataProvider\ACDataSource.cs – Type System.ServiceModel.FaultException: Server was unable to process request. —> Invalid Parameter (Microsoft.SoftwareCenter.Client.Data.ACDataSource+d__8 at MoveNext)

    StackTrace: at Microsoft.Management.Services.SelfServicePortal.Plugins.SingularAsyncManager`1.d__10.MoveNext()
    — End of stack trace from previous location where exception was thrown —
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.Management.Services.SelfServicePortal.Plugins.SingularAsyncManager`1.d__c`1.MoveNext()
    — End of stack trace from previous location where exception was thrown —
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.Management.Services.SelfServicePortal.DataAccess.SccmDataPlugin.d__26.MoveNext()
    — End of stack trace from previous location where exception was thrown —
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.SoftwareCenter.Client.Data.ACDataSource.d__8.MoveNext() SCClient 7/07/2020 10:02:41 1 (0x0001)


Leave a Comment

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