Troubleshoot Failed to download easy setup payload with Exception Errors

Suppose while downloading the SCCM update, you see Failed to download easy setup payload with exception in dmpdownloader.log. Or Failed to download Admin UI content payload with exception. What can you do to fix this issue ?. Let’s explore the solutions for Failed to download easy setup payload with exception in SCCM.

The SCCM updates appear in updates and servicing node of Configuration Manager console. And you always review dmpdownloader.log file to troubleshoot updates and servicing issues in SCCM. The dmpdownloader.log file is located on computer installed with the service connection point.

Configuration Manager admins usually encounter one of these issues while working on updates.

Suppose you go to Updates and Servicing node of ConfigMgr console and you notice that an SCCM update isn’t available, you run check for updates. After sometime you still don’t see the current branch update in the console. Now you review dmpdownloader.log file and you notice an error – Failed to download easy setup payload with exception.

The above error is a generic error and what you must look for is the exception error. In most cases you see the easy setup payload fails to download but the solution is based on the error that you see after the exception.

Failed to download easy setup payload with exception: The remote name could not be resolved: ‘go.microsoft.com’

The remote name could not be resolved: ‘go.microsoft.com‘ is the most common error that you will see in the dmpdownloader.log. And the solution is very simple. The log file clearly tells that it cannot resolve the go.microsoft.com and hence it will not download the update.

The error is not at Microsoft end rather it has to do with your server and network. You can try the following steps to resolve this error.

  • Ensure the anti-virus installed on SCCM server isn’t blocking the update download. To establish if AV is the culprit, you can temporarily disable it and then run check for updates. In most cases AV or security software is the cause of this issue.
  • If it’s not antivirus, it could be your corporate firewall or a device that sits between the internet and your organization. If you are not a network guy, you never know how your network is configured and what rules are put in place to filter the traffic. So in this case, I would suggest to do a network trace with Wireshark or contact your networking team to determine the problem.
Failed to download easy setup payload with exception: The remote name could not be resolved go.microsoft.com
Failed to download easy setup payload with exception: The remote name could not be resolved go.microsoft.com
ERROR: Failed to download Admin UI content payload with exception: The remote name could not be resolved: 'go.microsoft.com'    SMS_DMP_DOWNLOADER
 Failed to call AdminUIContentDownload. error = Error -2146233079
 AdminUI Content Download thread is exiting…
 ERROR: GetSccmConnectedServiceUrl Exception System.Net.WebException: The remote name could not be resolved: 'go.microsoft.com' at Microsoft.ConfigurationManager.DmpConnector.Connector.SCCMConnectorUtility.GetSccmConnectedServiceUrl(IWebProxy prx)
 WARNING: Failed to download easy setup payload with exception: The remote name could not be resolved: 'go.microsoft.com'
 WARNING: Retry in the next polling cycle

Failed to download Admin UI content payload with exception: Unable to connect to the remote server

The exception Unable to connect to the remote server is actually a warning seen in dmpdownloader.log file. So again you must involve your networking here because as per the log file we see unable to connect to remote server message.

Typically the Unable to connect to the remote server issue is fixed by ensuring the Configuration Manager Proxy Exceptions are in place. Configuration Manager requires URLs to be allowed through the firewall. There are many SCCM components that require this and you must allow these URL’s to ensure the updates download correctly.

SourceDestination URLComponent
Service Connection Point*akamaiedge.netUpdates and Servicing
Service Connection Point.manage.microsoft.comUpdates and Servicing
Service Connection Pointgo.microsoft.comUpdates and Servicing
Service Connection Pointblob.core.windows.netUpdates and Servicing
Service Connection Pointdownload.microsoft.comUpdates and Servicing
Service Connection Pointsccmconnected-a01.cloudapp.netUpdates and Servicing
Service Connection Pointhttp://silverlight.dlservice.microsoft.comUpdates and Servicing
Service Connection Point*.manage.microsoft.comMicrosoft Intune
Service Connection Pointhttps://bspmts.mp.microsoft.com/V1/ MicrosoftMicrosoft Intune
Service Connection Pointhttps://login.microsoftonline.com/Microsoft Intune
Service Connection Pointdownload.microsoft.com, https://go.microsoft.com/fwlink/?LinkID=619849Windows 10 Servicing

Once again, if you are not managing the network and firewalls in your organization, you must contact the network team for this.

Failed to download Admin UI content payload with exception: Unable to connect to the remote server
Failed to download Admin UI content payload with exception: Unable to connect to the remote server
ERROR: Failed to download Admin UI content payload with exception: Unable to connect to the remote server
 Failed to call AdminUIContentDownload. error = Error -2146233079
 WARNING: Failed to download easy setup payload with exception: Unable to connect to the remote server
 WARNING: Retry in the next polling cycle

Failed to download easy setup payload with exception: The remote server returned an error: (400) Bad Request

Suppose you see the following error logged in DMPDownloader.log. WARNING: Failed to download easy setup payload with exception: The remote server returned an error: (400) Bad Request.

To fix the issue, try these steps as suggested by Microsoft :-

  • Check the ProxyName value of the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\AIUS registry subkey.
  • Verify the current proxy configuration by running the following commands – netsh winhttp show proxy and netsh winhttp show proxy source=ie.
  • Check the bypass list, and make sure that *.microsoft.com and *.windowsupdate.com are added to the bypass list. Otherwise, run the following command:
  • You can run the following command to bypass the list – netsh winhttp set proxy proxy-server=”ProxyServerName” bypass-list=”.microsoft.com”, “.windowsupdate.com”
  • Restart the SMS Executive Service (SMSExec).
  • If the issue persists, reinstall the Service Connection Point role.

Failed to download Admin UI content payload with exception: The underlying connection was closed

We have another variant of Failed to download Admin UI content payload with exception. The underlying connection was closed. Could not establish trust relationship for the SSL/TLS secure channel. You may also see The remote certificate is invalid according to the validation procedure.

ERROR: Failed to download Admin UI content payload with exception: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. The remote certificate is invalid according to the validation procedure.

I have not experienced this error before but some of you may have. So I decided to cover the error in this post. According to Microsoft, you can first launch the Internet Explorer and test if you can access the below URL.

http://download.windowsupdate.com/windowsupdate/redist/standalone/7.4.7600.226/windowsupdateagent30-x86.exe

If you can access the above URL but if it fails to download the executable, you must check the firewall to make sure that it doesn’t block the connection.

You must ensure TCP port 443 and 80 are exempted from the following. Usually these ports are allowed but do have a check.

  • Source = SiteServer or proxy server (if proxy is used)
  • Destination = windowsupdate.com and microsoft.com

Failed to download Admin UI content payload with exception: Access to the ConfigMgr.AdminUIContent.AUC is denied

Once again, the access to the ConfigMgr.AdminUIContent.AUC is denied is a rare error. I haven’t seen this error on any ConfigMgr setups except one.

The ConfigMgr.AdminUIContent.AUC is denied could be due to the installed antivirus that could be blocking this file. The ConfigMgr update could be stuck in downloading state with following errors logged in dmpdownloader.log file.

Take a look at Configuration Manager antivirus exclusions. The article lists recommended antivirus exclusions for Configuration Manager site servers, site systems, and clients. Ensure you exclude the folder paths and test if the ConfigMgr.AdminUIContent.AUC is not blocked.

Download manifest.cab
 Redirected to URL https://configmgrbits.azureedge.net/adminuicontent/ConfigMgr.AdminUIContent.cab
 Got fwdlink and recreating the httprequest/response
 **ERROR: Failed to download Admin UI content payload with exception: Access to the path 'C:\Program Files\Microsoft Configuration Manager\AdminUIContentPayload\ConfigMgr.AdminUIContent.AUC' is denied.
 Failed to call AdminUIContentDownload. error = [error code: -2147024891, error message: Access is denied.]
 AdminUI Content Download thread is exiting…    **

Failed to call AdminUIContentDownload error code: -2147467261

The following error is logged in DMPDownloader.log. Failed to call AdminUIContentDownload. error = error code: -2147467261, error message: Invalid pointer. To fix this issue, use the below solution.

  • Check the ProxyName value of the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\AIUS registry subkey.
  • Verify the current proxy configuration by running the following commands – netsh winhttp show proxy and netsh winhttp show proxy source=ie.
  • Run the following command to bypass the list – netsh winhttp set proxy proxy-server=”ProxyServerName” bypass-list=”.microsoft.com”, “.windowsupdate.com”.
  • Restart the SMS Executive Service (SMSExec). If the issue persists, reinstall the Service Connection Point role.

Failed to call Initialize. Error code: -2147467261. Error message: Invalid pointer

To fix this issue, check whether the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SMS_DMP_CONNECTOR registry subkey exists. If it does not, create the subkey.

Finally, delete all files in the Hman.box\CFD folder, and restart the SMS Executive Service (SMSExec).

Need Assistance?

Send us a message or post your question in forums.