SCCM – Hung or Frozen Configuration Manager Update

email me

While using Updates and Servicing in the CM console, you notice that one of the upgrades or hotfixes is stuck at download, pre-req check, or installing.

To reset the update manager, run the CMUpdateReset.exe tool, located here:

C:\Program Files\Microsoft Configuration Manager\cd.latest\SMSSETUP\TOOLS\CMUpdateReset

 

From an admin prompt

C:\Program Files\Microsoft Configuration Manager\cd.latest\SMSSETUP\TOOLS\CMUpdateReset\CMUpdateReset.exe -S sccm.homelab.com -D CM_YourSiteCode -P EAB25B02-02DD-4A14-B6D0-BA5BDE540D66_THE_PACKAGE_GUID

or

C:\Program Files\Microsoft Configuration Manager\cd.latest\SMSSETUP\TOOLS\CMUpdateReset\CMUpdateReset.exe -FDELETE -S sccm.homelab.com -D CM_YourSiteCode -P EAB25B02-02DD-4A14-B6D0-BA5BDE540D66_THE_PACKAGE_GUID

 

Output

[Warning]
You can use this tool when an in-console update has not yet installed and is in a failed state. A failed state can mean the update download remains in progress but is stuck and taking an excessively long time, perhaps hours longer than your historical expectations for update packages of similar size. It can also be a failure to replicate the update to child primary sites. When you run the tool, it runs against the update that you specify. If the package is in pre-installation state, it will delete it. If package is in replicating state, it will reinitiate replication. Are you sure you want to run the tool? Enter Y for Yes and N for No.
y

Running CMUpdateReset.exe tool …
Verified that the SQL server FQDN belongs to the top level site.
Verified that the site servers run version 1606 or later.

Verified that replication is active.

Package is in pre-installation state. Attempting to clean up the package.

Verified that the service connection point is installed on the top level site.
Verified that the account has permission to service connection point share.
Verified that the account has permission to the inboxes\hman.box folder.

Service SMS_EXECUTIVE is  Running  on machine SCCM.homelab.com.
Verified that service SMS_EXECUTIVE is running on machine SCCM.homelab.com.

Service CONFIGURATION_MANAGER_UPDATE is  Running  on machine SCCM.homelab.com.
Verified that service CONFIGURATION_MANAGER_UPDATE is running on machine SCCM.homelab.com.

Verified that the package is not in post-replication state for all the child sites (if any).
Marking package in the package distribution list as deleted.

(0 row(s) affected.)
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Marked package in the package distribution list as deleted.

Deleting update package EAB25B02-02DD-4A14-B6D0-BA5BDE540D66 from EasySetupSettings table on site server sccm.homelab.com.

(0 row(s) affected.)
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Update package is deleted from EasySetupSettings table.

Deleting update package EAB25B02-02DD-4A14-B6D0-BA5BDE540D66 from cm_updatepackageSiteStatus table on site server sccm.homelab.com.

(1 row(s) affected.)
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Update package is deleted from cm_updatepackageSiteStatus table.

Deleting update package EAB25B02-02DD-4A14-B6D0-BA5BDE540D66 from CM_UpdatePackage_MonitoringStatus table on site server sccm.homelab.com.

(2 row(s) affected.)
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Update package is deleted from cm_updatepackageSiteStatus table.

Deleting update package EAB25B02-02DD-4A14-B6D0-BA5BDE540D66 from cm_updatepackages table on site server sccm.homelab.com.

(1 row(s) affected.)
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Update package is deleted from CM_UpdatePackage_MonitoringStatus table.

Verifying whether the table entries for package EAB25B02-02DD-4A14-B6D0-BA5BDE540D66 is deleted on site server sccm.homelab.com.

Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)

Deleting \\SCCM.homelab.com\sms_001\EasySetupPayLoad\EAB25B02-02DD-4A14-B6D0-BA5BDE540D66.cab.

\\SCCM.homelab.com\sms_001\EasySetupPayLoad\EAB25B02-02DD-4A14-B6D0-BA5BDE540D66.cab does not exist to delete.

Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)

Deleting \\SCCM.homelab.com\sms_001\EasySetupPayLoad\Offline\EAB25B02-02DD-4A14-B6D0-BA5BDE540D66.cab.

\\SCCM.homelab.com\sms_001\EasySetupPayLoad\Offline\EAB25B02-02DD-4A14-B6D0-BA5BDE540D66.cab does not exist to delete.

Deleting \\SCCM.homelab.com\sms_001\EasySetupPayLoad\Offline\ConfigMgr.Update.Manifest.cab.

\\SCCM.homelab.com\sms_001\EasySetupPayLoad\Offline\ConfigMgr.Update.Manifest.cab does not exist to delete.

Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Deleting \\SCCM.homelab.com\sms_001\EasySetupPayLoad\EAB25B02-02DD-4A14-B6D0-BA5BDE540D66.

Deleted \\SCCM.homelab.com\sms_001\EasySetupPayLoad\EAB25B02-02DD-4A14-B6D0-BA5BDE540D66.

Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Deleting cmupdate notifications.
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)

[Success]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 Update in console to redownload the package.
If the package is reinitiating replication or installation, DO NOT restart the SMS_EXECUTIVE service. You can use the flowchart at (https://docs.microsoft.com/sccm/core/servers/manage/update-replication-flowchart) to troubleshoot additional issues..