Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING SCCM 1606 Hotfix KB3186654 Downloading stuck

ChrisJ

Member
Messages
9
Reaction score
0
Points
1
I see the CM 1606 Hotfix KB3186654 listed in my Updates and Services. It's been stuck at Downloading since it showed up a week ago. I have tried restarting the SMSExecutive service as well as have restarted the server as a whole. The DMPDownloader log looks as if the file is downloaded successfully it just never updated in the console. See Attached.
 

Attachments

I don't see any errors in the log file. I don't even thing it's stuck anywhere. The update should appear in the updates and servicing node. wait for some more time else we have to really troubleshoot this issue.
 
Appreciate you taking a look and any advice you or anyone else may have. It does appear in the Updates and Servicing node but with a state of Downloading even tho it appears to have downloaded without error. I again restarted the SMS_Executive service in hopes this would unlock it but no joy.
 
Hi Chris, can you attach configmgrsetup.log from the connector role ?. It would be helpful if you can attach hman.log and cmupdate.log as well.
 
Sure. I've included the rollover of the hman.log file as well since it appears to rollover frequently still may be too new of information but it's what was available.
 

Attachments

Delete the update from the table dbo.CM_UpdatesPackage and restart SMS_Executive service. The GUID of the package can be obtained from Easy payload setup folder.
 
Delete the update from the table dbo.CM_UpdatesPackage and restart SMS_Executive service. The GUID of the package can be obtained from Easy payload setup folder.
Have you tried this before ?. I would not recommend deleting the table from SQL DB.
 
It's not deleting a table , just deleting the update record with the help of its GUID. I tried many times during upgrade to 1606 from 1602. While running Pre-req check and while installing the update, it stuck many times and i had to delete the update from that table. It worked for me.
 
I have not done this.. and have heard from other people that manually updating the DB is not recommended, leaving that as a last resort. Any other recommendations Prajwal?
 
Hi Chris,

Here is the workaround for the issue that you mentioned. let me if it worked / not worked.

Workaround:

1. Manually update the registry value to point to the right path

2. manually move 2.ESC to hman.box\CFD folder.

GetFileAttachment
 
If you are referencing this thread (https://social.technet.microsoft.co...-updates-after-1602?forum=ConfigMgrCompliance) I checked the registry entry and it matches what they are showing already. I do not have a 2.ESC file in hman.box to move nor could I find a 2.ESC file anywhere else.

If that's not what you were meaning could you be more explicit regarding the registry value and where I may find the 2.ESC file?
 
The 2.ESC file is found in SCCMInstallationFolder\Inboxes\hman.box. The resolution mentioned in that technet forum thread seems to be working for many users. I got the confirmation from the people who contacted me over support address for this issue. In your case it seems something is really wrong, let's try the other method. Backup your SCCM DB and delete the update from the table dbo.CM_UpdatesPackage and restart SMS_Executive service. You could find out GUID of the package from Easy payload setup folder. Let me know if it works.
 
Ok so I deleted the row for GUID 79fb5420-bb10-44ff-81ba-7bb53d4ee22f from DBO_CM_UpdatesPackage and restarted the SMS_Executive service. Console still shows the same update in the downloading state. Watching the dmpdownloader log I see no mention of the afore mentioned GUID. It does go through a process with GUID 3bf7e908-e7b2-4081-bcdb-465ca397e53e which appears to be kb3184153. Upon checking the database table the entry that I deleted is back.
 
Don't know if this will help but looking in "Updates and Servicing Status" it shows in the overview as "Applicable". If I view the status the top window shows Download as "In progress". The detail window below that for the Download step shows Completed on all steps, Process update package, Download update package cab file, extract update package payload, Download redist, and report package as downloaded. It seems while it thinks it reported it as downloaded that is where it's really stuck. Is there some way to force it to force the reporting package of downloaded? In Cloud Services it still shows as Downloading.
 
Is there some way to force it to force the reporting package of downloaded? - I am not really sure about this. I would suggest you open a support ticket with Microsoft support team.
 
Just thought I'd give you an update. I had received approval to contact microsoft regarding this issue but being the holiday season I had not had the time to do so. A week ago after 1610 had been out for a week or so and also being stuck on downloading during that time frame, both updates finally became marked available. I went ahead and did my tests on the 1610 and applied that update and now the server is happily going along. No idea what finally made them click over after 3 months but it's all good now.
 

Forum statistics

Threads
7,026
Messages
27,491
Members
17,677
Latest member
Nairolf

Trending content

Back
Top