SCCM 1906 Hotfix Download Issues
All of sudden a lot of people started to report about the SCCM 1906 hotfix download issues. The SCCM 1906 hotfix doesn’t download and shows the status as Available to Download.
The dmpdownloader.log file doesn’t help here because when you download the hotfix, it doesn’t log anything. In addition to that, a CMUpdateReset tool also won’t help here.
I first got to know about this issue when I read some comments posted on my KB4517869 hotfix installation post. It’s not a good experience when you update your Configuration Manager from 1902 to 1906 and you cannot install any hotfixes.
This hotfix rollup KB4517869 will not download. When I go to Updates and Servicing, it shows up and has a status of “Available to download”. It never changes. I had successfully updated from 1902 to 1906 3 days ago. The subsequent check pulled in the hotfix, but it will not download. If I click on “Download” (all other options are grayed out), it says either Checking for updates or Still checking for updates. I tried the reset tool and the update disappeared, came back on next check, but no change in status – still won’t download. I let it sit for a day and a half to see if things would change… nope.
We are experiencing the same issue. Upgraded from 1902 to 1906 this weekend, but when we wanted to apply the Hotfix it never downloaded. Also tried the CM update reset tool, tried removing the DB object and restart SMS_EXEC, still nothing.
Watching the log, it seems that it doesn’t find anything to download to the EasySetup… as if it doesn’t find anything.
I’d appreciate getting any help proceeding with this.
On Twitter, I got to know that this is a known issue in SCCM 1906 and has been resolved in SCCM 1910. While the tweet didn’t mention about the actual workaround, you could get that only when you open a case with CSS.
When I did some research the workaround was posted in this reddit forum thread. The same workaround is covered in this post along with screenshots to make it easy to follow.
If you notice issues with SCCM 1906 hotfix download, this workaround works. I had to revert my lab VM’s running SCCM 1910 to SCCM 1906 to test the workaround.
In the Configuration Manager console, go to Updates and Servicing node. Right click hotfix KB4517869 and click Download.
As I mentioned before the dmpdownloader.log doesn’t log anything.
Fix SCCM 1906 Hotfix Download Issues
First of all, you need to find the Package GUID of the problematic hotfix. Right click and select the Package GUID column.
Make a note of Package GUID of the hotfix. Copy it to a notepad or any text editor.
Open SQL Server Management Studio, connect to the database. On the top-level site and run the below query against the SCCM database.
EXEC spAddPackageToDownload 'PACKAGEGUIDHERE'
Restart the SMS_EXEC service and monitor your dmpdownloader.log file. You will notice the hotfix download begins.
The SCCM 1906 hotfix now shows the state as Ready to Install. You can proceed with installing the hotfix.
Always quality stuff here! Was stuck on this issue when upgrading from 1906 to 1910 and was considering jumping on Early Release Ring for 2002 version. Pleased I was able to progress with 1910 installation with this hint.
Glad to hear that.
Awesome sauce! thank you sir d: )
Darn good advice. Worked like a champ. Thanks very much.
Your are au King! Thanks
Did the trick. Thanks for the information.
it was great ,downloading fine now
Perfect! Thank you!
Thanks very much for these Instructions.
Quick Question though:
In a Secure (disconnected) Environment at what part of the process would I need to execute the stored procedure?
I image there’s three scenarios but not sure which one is correct:
i) Before running the ServiceConnectionTool.exe to create the cab file
ii) After running the ServiceConnectionTool.exe to create the cab file but before performing the import.
iii) It’s not required at all
Very keen to hear your reply.
It was great…thnx a lot
Finally I could install the update. Thanks Prajwal !!
Thanks worked like charm!!
Thank you for sharing this! Worked like a charm!
Worked like a charm!
Thanks
For many days I was thinking the issue was with my SCCM 1906 setup. Finally I read your post and followed the same steps. It worked. Thanks.