Fix SCCM Update Stuck Downloading State

In this post I will show you how to quickly fix SCCM updates stuck in downloading state. The most common issue that you come across while working with SCCM updates is that you cannot install the update. And you see the status of update is in downloading state and it is almost stuck.

This may happen due to various reasons but to quickly fix the SCCM update download issues, you can always make use of CMUpdateReset tool. You may also think of restarting the SCCM services or even restart the server, however that doesn’t fix the download issues most of the times.

I have seen most people in Community Forums complaining that they are unable to install the latest current branch update. When they upload the screenshots, I see the update is stuck in downloading state.

Observation – If the SCCM update shows downloading, is it actually downloading the update ?. On the site server if you go to \Program Files\Microsoft Configuration Manager\EasySetupPayload, you should see what actually is downloaded.

Fix SCCM Update Stuck Downloading State

In my lab setup I noticed SCCM update stuck in downloading state. For a long time it showed the status as downloading but the update was never downloaded.

In the SCCM console, make a note of Package GUID of the update.

SCCM update shows downloading state but it is stuck

If you go to EasySetupPayload folder, you will find a folder with name that matches the Package GUID. If you check the folder properties it shows 0 bytes.

EasySetupPayload FolderUsing SCCM update reset tool, you can either reset an update that has download problems or force delete the problematic SCCM update package. The CMUpdateReset tool is located in \cd.latest\SMSSETUP\TOOLS folder of the site server. Run the command prompt as administrator and change the path to CMUpdateReset folder.

Run the CMUpdateReset.exe (also called as update reset tool) and that will show you the tool usage options or examples.

cmupdatereset tool optionsOut from the above screenshot is listed below.

Microsoft (R) System Center Configuration Manager Update Reset Tool
Copyright (C) 2019 Microsoft. All rights reserved.

Usage: Run CMUpdateReset.exe on any server. The User that runs the tool must have administrator rights on all site servers and on the service connection point server.
[-S SQL Server FQDN of the top level site]
[-I SQL Server instance name, optional for the default instance]
[-D Database name]
[-P Package Guid]
[-FDELETE Force deletion of the package]
[-? Show syntax summary]

Example to run the default CMUpdateReset.exe:
CMUpdateReset.exe -S -D CM_XYZ -P 61F16B3C-F1F6-4F9F-8647-2A524B0C802C
CMUpdateReset.exe -S -I MyInstance -D CM_XYZ -P 61F16B3C-F1F6-4F9F-8647-2A524B0C802C

Example to force delete the package:
CMUpdateReset.exe -FDELETE -S -D CM_XYZ -P 61F16B3C-F1F6-4F9F-8647-2A524B0C802C
CMUpdateReset.exe -FDELETE -S -I MyInstance -D CM_XYZ -P 61F16B3C-F1F6-4F9F-8647-2A524B0C802C

Do not restart SMS_EXECUTIVE service if the tool is used to reinitiate replication. If the tool is used to clean up and redownload the package, you must restart the SMS_EXECUTIVE service or Check for Updates in console, after successfully running the tool.

There are two examples to run the cmupdatereset.

  • The first example resets an update (If the update is stuck downloading).
  • The second example force deletes the problematic package.

Always try resetting the update first and if you still see the same issue, try force deleting the package.

In my case, I did an update reset and that was successful. I saw the below message.

Successfully ran the CMUpdateReset.exe tool. If the tool deleted the package (check Updates and Servicing to see if the package is listed).

You must restart the SMS_EXECUTIVE service on the top level site. Or, use Check for Updates in console to re-download the package.

If the package is re-initiating replication or installation, DO NOT restart the SMS_EXECUTIVE service.

Fix SCCM Update Stuck Downloading State

11 thoughts on “Fix SCCM Update Stuck Downloading State”

  1. Hi prajwal, I am getting following error while downloading prerequisite:
    ERROR: Download() failed with 0x80004005 $$
    ERROR: Failed to download language pack manifest (0x80004005) $$

    Can you please help?

  2. I am stuck upgrading Configuration Manager to 2006 Hotfix Rollup at the Replication step. Updating the content library has not started. I’ve been looking at this for months. I do not see any errors or failures in distmgr.log. I’ve tried the CMUpdateReset tool but I get an error: 0x80131904 – A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 – The certificate chain was issued by an authority that is not trusted.) This is all on one server. I know nothing about certificates.

    This is a new server being setup for Configuration manager. I am not pushing anything to any clients until I know everything is working properly. Please help.

    • Good afternoon Alex, Running into this exact same issue. Did you find a resolution? Thank you!

  3. I have had this issue for several releases now, but the fix listed does not work. It is definitely related to a change on our SCCM server that was made regarding HTTPS communication. We still have not figured it out. Instead, I have a work around, which is to use another machine to map a drive to the SCCM server and download from there.

    Perhaps this will help someone else:

    1. Go to ConfigMgrSetup.log and review error

    View the errors for the most recent Upgrade based on Package ID

    2. Go to \Microsoft Configuration Manager\Logs\dmpdownloader.log and copy the full command for running manually.


    (Running from “otherserver” with mappings as opposed to sccm:


    >net use x: \\sccmserver\Microsoft Configuration Manager\bin\X64\

    3. verify the download with the following / verify switch::

    4. Check the logs to see whether the and / or failed to download

    If So, Use the links from the command above to manually download with IE and copy to the redist path

    5. re run the /verify command

    6. refresh the update in Congig Manager. It should now say “Ready to install”

  4. Hello
    I have an issue with updating my sccm from 1902 to 2010. I initially started the process from the configuration manager console and got stuck at installation (installing component) for 1 week. I used the reset tool to reset the process and deleted the package
    I reinitialized the process but the state is Available to Download. The package is not present in the EasySetupPayload. The process has been running for the past 3 days and is still not available in the EasySetupPayload.

    Need your assistance please

  5. What about if the files are in deed downloaded, but the download stuck in “in progress” Therefore cannot install the update

    • Same problem here, 3893 files, 706 folders, 2,44 gb are downloaded (in testing and in productive environment), but gui still shows downloading ….. A reset deletes all data, restarts the download, but no “ready to Install” message after download.

      Best Regards


        • I had the same issue; CMUpdateReset tool cleared the update; i restarted it and it was still hung. I looked at the ConfigMgrSetup.log on the root of C:\ drive, and identified the issue that it was having trouble downloading a ‘prereq’ file. So, I ran the setupdl.exe from cd.latest directory, downloaded the pre-req files and it was errored out downloading a file. I parsed thru the configmgrsetup.log again, and found that the issue is with The log file says… “INFO: Downloading as” and a couple of lines down the log, was the error. I opened IE and went to the url above “” and was prompted to save the file. I saved it as “” and copied that file to ‘D:\Program Files\Microsoft Configuration Manager\EasySetupPayload\{Package GUID from console of the Current Branch update version in error}\redist’ on the primary site server and kicked off a ‘check for updates’ again. It was successful. Hope that helps.

Comments are closed.