May 23, 2011

Advanced WSUS Troubleshooting for error 0x8024401f

Error 0x8024401f  may prevent you from installing updates from WSUS.
This error means the IIS had an internal server error while processing download request.

I didn't know that.

You may get something like this in your C:\Windows\WindowsUpdate.log :

________________________________________________________________

   *   UpdateId = {5BA0608C-87FC-4CF1-9374-033C4B79E5D7}.100
2011-05-23 14:32:32:985  924 91c Agent   *     Bundles 1 updates:
2011-05-23 14:32:32:985  924 91c Agent   *       {231511E5-E672-4A13-91BD-8E166A1557D1}.100
2011-05-23 14:32:33:078  924 988 DnldMgr Error 0x8024401f occurred while downloading update; notifying dependent calls.
2011-05-23 14:32:33:078  924  c8 DnldMgr Error 0x8024401f occurred while downloading update; notifying dependent calls.
2011-05-23 14:32:33:093  924 91c Agent *********
2011-05-23 14:32:33:093  924 91c Agent **  END  **  Agent: Downloading updates [CallerId = Microsoft Forefront Client Security]
2011-05-23 14:32:33:093  924 91c Agent *************
2011-05-23 14:32:33:093  924 91c Report REPORT EVENT: {0FDCDB7B-13DB-4F4E-B130-98CAE2F7B71B} 2011-05-23 14:32:29:657+0530 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 60 updates.
2011-05-23 14:32:33:093  924 91c Report REPORT EVENT: {1CF1F7FF-391B-47A5-8038-67BB8B147097} 2011-05-23 14:32:29:657+0530 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2011-05-23 14:32:33:093  924 91c Report CWERReporter finishing event handling. (00000000)
2011-05-23 14:32:33:093  924 91c Report CWERReporter finishing event handling. (00000000)
2011-05-23 14:32:33:093  924 91c Report CWERReporter finishing event handling. (00000000)
2011-05-23 14:32:33:093  924 91c Report CWERReporter finishing event handling. (00000000)
2011-05-23 14:32:33:093  924 91c Report CWERReporter finishing event handling. (00000000)
2011-05-23 14:32:33:093  924 91c Report CWERReporter finishing event handling. (00000000)
2011-05-23 14:32:33:093  924 91c Report REPORT EVENT: {EEE61AE6-BAB0-40E5-980E-F5C31552316D} 2011-05-23 14:32:29:719+0530 1 163 101 {E75471D2-0D1A-4101-858F-2803F5DE9453} 100 0 AutomaticUpdates Success Content Download Download canceled.
2011-05-23 14:32:33:093  924 91c Report REPORT EVENT: {1C46C78E-B600-4B21-ABB1-2572EE7D5922} 2011-05-23 14:32:29:750+0530 1 163 101 {A7BF88EE-CFBB-4947-B0BC-52630F561340} 102 0 AutomaticUpdates Success Content Download Download canceled.
2011-05-23 14:32:33:093  924 91c Report REPORT EVENT: {1322E118-A312-448E-ADC1-0E1D273E0901} 2011-05-23 14:32:29:796+0530 1 163 101 {8D807A34-2A08-4F5E-B722-C12BE78C8D15} 104 0 AutomaticUpdates Success Content Download Download canceled.
2011-05-23 14:32:33:093  924 91c Report CWERReporter finishing event handling. (00000000)
2011-05-23 14:32:33:155  924 988 DnldMgr BITS job {E804C303-7E29-4794-8610-EFAEB428027D} hit a transient error, updateId = {231511E5-E672-4A13-91BD-8E166A1557D1}.100, error = 0x801901F4
2011-05-23 14:32:33:155  924 988 DnldMgr   Attempt no. 1 to resume the job
2011-05-23 14:32:33:217  924  c4 DnldMgr Error 0x8024401f occurred while downloading update; notifying dependent calls.
2011-05-23 14:32:33:217  924 988 DnldMgr Error 0x8024401f occurred while downloading update; notifying dependent calls.
2011-05-23 14:32:33:233  924  c8 DnldMgr BITS job {E804C303-7E29-4794-8610-EFAEB428027D} hit a transient error, updateId = {231511E5-E672-4A13-91BD-8E166A1557D1}.100, error = 0x801901F4
2011-05-23 14:32:33:233  924  c8 DnldMgr   Attempt no. 2 to resume the job
2011-05-23 14:32:33:295  924  c8 DnldMgr BITS job {E804C303-7E29-4794-8610-EFAEB428027D} hit a transient error, updateId = {231511E5-E672-4A13-91BD-8E166A1557D1}.100, error = 0x801901F4
2011-05-23 14:32:33:295  924  c8 DnldMgr   Attempt no. 3 to resume the job
2011-05-23 14:32:33:341  924 988 DnldMgr BITS job {E804C303-7E29-4794-8610-EFAEB428027D} hit a transient error, updateId = {231511E5-E672-4A13-91BD-8E166A1557D1}.100, error = 0x801901F4
2011-05-23 14:32:33:341  924 988 DnldMgr   Will not attempt to resume the job as it has reached the maximum number of attempts.
2011-05-23 14:32:33:341  924 988 DnldMgr Error 0x8024401f occurred while downloading update; notifying dependent calls.
2011-05-23 14:32:33:403  924 9bc DnldMgr Error 0x8024401f occurred while downloading update; notifying dependent calls.
2011-05-23 14:32:33:651  924 9bc DnldMgr Error 0x8024401f occurred while downloading update; notifying dependent calls.
2011-05-23 14:32:33:666  924  c4 DnldMgr Error 0x8024401f occurred while downloading update; notifying dependent calls.
2011-05-23 14:32:33:666  924  94 AU AU checked download status and it changed: Downloading is paused


_______________________________________________________________

So, first I checked it at the client's side if there was something in event log and then server's event log and got nothing.
Then I tried to browse my WSUS URL from Internet Explorer,
http://servername:8530/Content
and got error 500 Internal Server Error.
The error claimed that there were some duplicate MIME Type issues with IIS Configuration.
What does that mean?
So I Googled it, and then changed MIME Types that were added twice in IIS Settings.

On the error page, you can find those MIME Types which are repeatedly declared. In my case it was the ".psf application/octet-stream".
so, go to IIS Manager, Click WSUS Website features view, Select MIME Types, and delete the MIME Type from there.
Restart the website and check if you can Download updates now.

Labels:

11 Comments:

At September 26, 2011 at 9:27 AM , Blogger rossinini said...

hey! thanks for the post. Had the same problem and will try the steps you have outlined. Superthanks

 
At September 27, 2011 at 3:04 AM , Blogger northcro said...

Thanks also for the post. We have the exactly the same problem and will try steps you have outlined also.

 
At March 22, 2013 at 10:47 PM , Anonymous Anonymous said...

Where did you find that you had duplicate MIME types? I don't see any reference to that.

 
At November 15, 2016 at 6:08 PM , Blogger Unknown said...

Thanks !! Same problem and solved

 
At July 19, 2017 at 1:14 AM , Blogger antfoo said...

Thank you! This fixed our WSUS issue with error 0x8024401f

 
At August 2, 2017 at 10:05 PM , Blogger Unknown said...

Thank you! Fixed it for me as well. However to find the error with the MIME type in question, I had to actually try to go into the MIME types for the Content directory in IIS under the WSUS website, I couldn't get the type to show in the browser error page.

 
At September 21, 2017 at 10:59 PM , Blogger daniel said...

Thank you, the error was similar and you solution works. The Mime type i added before trying the solve another problem with Wsus( no detect and no report)

 
At February 15, 2018 at 10:04 PM , Blogger Unknown said...

This comment has been removed by the author.

 
At February 15, 2018 at 10:05 PM , Blogger Unknown said...

This comment has been removed by the author.

 
At February 15, 2018 at 10:07 PM , Blogger Unknown said...

Initially i had to add a custom MIME to my IIS ".esd application/octet-stream" so that windows 10 computers could download the updates from the WSUS because they were stuck at 0% for days...

Thank you for the information, removing the custom MIME that I added months ago to server 2012 R2 fixed the problem for me.
There must of been a recent update that removed the need to add that custom MIME.

 
At September 5, 2019 at 1:14 AM , Blogger Unknown said...

This might help: http://blog.errorkart.com/how-to-fix-update-error-0x8024401f-on-windows-10/

 

Post a Comment

Subscribe to Post Comments [Atom]

<< Home