Disclosure: do not follow these steps if you do not know what you’re doing. They should only be used as a last resort. Use with caution.
I’ve had a couple different SCCM environments get stuck during update installations that have come down through the new Updates and Servicing feature in the current branch builds. Typically, this does not happen but I have yet to determine the root cause. It’s very important to note that updates that come down through the console can take a significant amount of time to install and you should be patient. I would recommend waiting several hours for them to complete while checking dmpdownloader.log for the real-time status. You should also close and reopen the SCCM console before taking any action – it may just be waiting for you to relaunch the console to install a newer version of the console.
This fix will help you if your hotfix updates are stuck in the Installing state, like so:
There were no actions available to resolve the state of these hotfixes from the SCCM console, and restarting the SMS_EXECUTIVE service and CONFIGURATION_MANAGER_UPDATE services and the server itself did not help in this case, either. It actually looked like the hotfixes successfully applied weeks ago, yet the state had not been updated. The workaround for this was to change the status of these hotfixes directly in the CM database, which should be considered a last resort in any scenario. There’s a simple SQL query to do this from SQL Server Management Studio, which originated from this TechNet article from an earlier Technical Preview version:
EXEC spCMUSetUpdatePackageState N'd26be618-1df5-4680-a65f-03cec6abc7ec', 262146, N''
You will need to modify the above query with the metadata string from the corresponding update. To find which string to use, go to your SCCM installation directory open the EasySetupPayload folder that serves as the cache for in-console updates, and find the folder name for the hotfix that is stuck. In this case, I ran the query twice – once for each hotfix that was stuck installing.
After executing the query and refreshing the SCCM console, the status was cleared immediately and I was able to proceed with the install the latest branch release.
11 thoughts on “In-Console Updates Stuck Installing in ConfigMgr: How To Fix It”
Very helpful information Josh – thanks! I’ve had a couple different sites hung (lab experiments only thank goodness) – I teach SCCM and Packaging to guys I am contracting out to the different enterprises that I have connections with. This has happened more often than I am happy with – is there a bug in SQL or the process that SQL is receiving?
Again, thanks – Rick
I had the same issue updating 1610 to 1702, the installation was tuck in pre-req check or installation, a new program named CMUpdateReset.exe has been released in the new CB 1706 and it is applicable from CB1606, so you can use this new program to solve the update issues (downolading, pre-checking or installation) http://blog.coretech.dk/kea/configuration-manager-current-branch-upgrade-stuck-in-downloading/#comment-647162
I tried to find this new program through internet but no way, so I created a Virtual Machine with fresh installation of SCCM and I was able to install 1706 on it only for retrieving CMUpdateReset.exe, after that I copied CMUpdateReset.exe in the production SCCM and run it with -FDELETE parameter and finally the program cleaned up my SCCM and successfully download and done the update.
I shared for you the program so you can solve your issue. enjoy!
Great info! Thanks for sharing!http://220.127.116.11//wp-admin/edit-comments.php#comments-form
Thank you for this. I to have had the 1706 update stuck on prereq check and install.
Man! I have no words to thank you for share this tool. I was stucked in this issue for weeks!
Thanks a lot!
Hi Josh this just helped me with a stuck 1802 installation so very many thanks for the post.
Get stuck with 1810 update in installing state, try to run your SQL query but end-up in this sql error
EXEC spCMUSetUpdatePackageState N’454B3508-4387-4106-9441-283495DEC3EC’, 262146, N’
Msg 102, Level 15, State 1, Line 4
Incorrect syntax near ‘454’.
EXEC spCMUSetUpdatePackageState N’454b3508-4387-4106-9441-283495dec3ec’, 262146, N”
(Double single quotes at the end)
whoah this weblog is great i like reading
your posts. Keep up the good work! You realize, a
lot of persons are searching round for this info, you
could aid them greatly.
Where do I run the SQL query? I’ve got SSMS open, but do I run it against a particular DB or a table, or what?
Great Information it helps me a lot in fixing my issue..