In this post I will show you how to quickly fix SCCM update that’s 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 that the update was stuck at 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.
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.
Using 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.
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]
<strong>Example to run the default CMUpdateReset.exe:
CMUpdateReset.exe -S server1.contoso.com -D CM_XYZ -P 61F16B3C-F1F6-4F9F-8647-2A524B0C802C
CMUpdateReset.exe -S server1.contoso.com -I MyInstance -D CM_XYZ -P 61F16B3C-F1F6-4F9F-8647-2A524B0C802C</strong>
Example to force delete the package:
<strong>CMUpdateReset.exe -FDELETE -S server1.contoso.com -D CM_XYZ -P 61F16B3C-F1F6-4F9F-8647-2A524B0C802C
CMUpdateReset.exe -FDELETE -S server1.contoso.com -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.