none
error 8024401F in windows update, in windows 7

    Question

  • I'm using windows 7, and WSUS to get my updates. windows update detects the updates from WSUS but when i try downloading them, i'm facing this error code 8024401F.

    Note other windows 7 machines have no problem with the same configuration.
    Sunday, March 07, 2010 12:21 PM

All replies

  • but when i try downloading them, i'm facing this error code 8024401F.
    This is an HTTP 500 error, and generally indicates that the serer has some intenal issue impacting the response to the request. Since this is only client experiencing this issue, it suggests that the problem may be a bad request submitted that the server cannot properly respond to.

    It would be useful to see the full detection event, with the error in context.



    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2010)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Monday, March 08, 2010 3:41 PM
    Moderator
  • hi lawrence,

    This issue is getting frustrating to me, i would appreciate your help. Please let me know what information you need in details and from where should i get them.

    Thanks,
    Wednesday, March 10, 2010 8:16 AM
  • hi lawrence,

    This issue is getting frustrating to me, i would appreciate your help. Please let me know what information you need in details and from where should i get them.

    Thanks,

    Uhhh.... I thought I asked that already . . .


    >> It would be useful to see the full detection event, with the error in context.

    Presumably you're already familiar with the WindowsUpdate.log -- I'm assuming that's where your reference to the error code (0x8024401F) is coming from.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2010)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Wednesday, March 10, 2010 5:26 PM
    Moderator
  • I am getting the same error on Windows SBS 2008 server which in turn will not update and allow the clients to get the update - The actual error is "WindowsUpdate_8024401F" "WindowsUpdate_dt000" and I can not find reference to it anywhere.

    I don't quite  understand what you mean by "full detection event, with the error in context" but I have found these errors in the event log.

    The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

    Context: Application 'Search', Catalog 'index file on the search server Search'

     

    The start address <sts3s://XXX.mywebsite.com:987/contentdbid={b0bf23e2-2ef2-4eef-8e0b-e29beeea0ae2}> cannot be crawled.

    Context: Application 'Search index file on the search server', Catalog 'Search'

    Details:

    Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled. (0x80041205)

    Wednesday, October 27, 2010 11:43 PM
  • I am also getting the same error in Windows Server 2008 standard.

    But the strange thing is that, after showing this error for months, windows got updated on last Dec 2010. Again after that single day, it is showing the same error. As far as I remember  I haven't made any changes.

    Friday, February 18, 2011 4:29 AM
  • I am also getting the same error in Windows Server 2008 standard.

    But the strange thing is that, after showing this error for months, windows got updated on last Dec 2010. Again after that single day, it is showing the same error. As far as I remember  I haven't made any changes.

    The same request applies.. Post The Log Entries showing the client's detection event. Without logs, I haven't got a clue what's happening.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Friday, February 18, 2011 4:31 PM
    Moderator
  • Hi Everyone,

    I was facing similar issue but couldnt find solution anywhere.

    As i found that this is dns error i did one step and solved the issue for me.

    Please try ipconfig /flushdns and then try updates staraightaway.

    Tell me if that helped.

     

    Please mark as answer if that helps. that will help others as well


    Tx n Re, NSB Please click the Check Mark As Answered On This Page If this post helps to resolve your issue as it helps others.
    Wednesday, May 18, 2011 10:40 AM
  • Dear all

    i'm also facing seam issue with Windows Server 2008 standard and couldn't find any solution

    and i'm also try ipconfig /flushdns but nothing happened

    i'm totally tired don't know what to do :( any one can help

    Mr v-2nbatt did you find any solution ?

    kind regerds

    Tuesday, May 24, 2011 12:08 PM
  • Hi Ahmed,

    As stated above by Lawrence, we need to take a look at the logs in order to help you.  Try this:

     

    1) From a command prompt on the server with issues, type "wuauclt /detectnow", without the quotes.  This kicks off a checkin with your WSUS server.

    2) On this same server, navigate to your Windows directory (usually c:\windows).  There is a file there called 'windowsupdate.log'.  Open this file in your text editor, then look for the lines with a timestamp that matches the time when you performed step 1.  Copy all the lines with this timestamp and put them into a reply here so we can hopefully see where the error is.

    Once we see that, we might be able to help you out.

    Hope that helps,

    John

    Tuesday, May 24, 2011 1:30 PM
  • Hi Ahmed,

    As stated above by Lawrence, we need to take a look at the logs in order to help you.  Try this:

     

    1) From a command prompt on the server with issues, type "wuauclt /detectnow", without the quotes.  This kicks off a checkin with your WSUS server.

    2) On this same server, navigate to your Windows directory (usually c:\windows).  There is a file there called 'windowsupdate.log'.  Open this file in your text editor, then look for the lines with a timestamp that matches the time when you performed step 1.  Copy all the lines with this timestamp and put them into a reply here so we can hopefully see where the error is.

    Once we see that, we might be able to help you out.

    Hope that helps,

    John


    Hi John

    I am having the same issue, I run a small network (1 x SBS 2008, 1 x Server 2003 and 3 PCs - 2 x XP Pro and 1 x Windows 7 Pro).  I appear to be having the same issues as mentioned above.  Although updates seem to be work find for the XP machines and the Server 2003.  To confirm I only get the error on the SBS 2008 and the Windows 7 Machine.

    I have followed your instruction above and the following are from the windowsupdate.log..... I hope you can help!!

    2011-07-15 15:56:12:422  264 914 AU Triggering AU detection through DetectNow API
    2011-07-15 15:56:12:422  264 914 AU Triggering Online detection (non-interactive)
    2011-07-15 15:56:12:422  264 2614 AU #############
    2011-07-15 15:56:12:422  264 2614 AU ## START ##  AU: Search for updates
    2011-07-15 15:56:12:422  264 2614 AU #########
    2011-07-15 15:56:12:422  264 2614 AU <<## SUBMITTED ## AU: Search for updates [CallId = {3D74536C-D5C0-46AE-A2E4-732392302407}]
    2011-07-15 15:56:12:422  264 dd0 Agent *************
    2011-07-15 15:56:12:422  264 dd0 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2011-07-15 15:56:12:422  264 dd0 Agent *********
    2011-07-15 15:56:12:422  264 dd0 Agent   * Online = Yes; Ignore download priority = No
    2011-07-15 15:56:12:422  264 dd0 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2011-07-15 15:56:12:422  264 dd0 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2011-07-15 15:56:12:422  264 dd0 Agent   * Search Scope = {Machine}
    2011-07-15 15:56:12:422  264 dd0 Setup Checking for agent SelfUpdate
    2011-07-15 15:56:12:422  264 dd0 Setup Client version: Core: 7.4.7600.226  Aux: 7.4.7600.226
    2011-07-15 15:56:12:422  264 dd0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2011-07-15 15:56:12:438  264 dd0 Misc  Microsoft signed: Yes
    2011-07-15 15:56:12:438  264 dd0 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x801901f4
    2011-07-15 15:56:12:438  264 dd0 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x801901f4
    2011-07-15 15:56:12:438  264 dd0 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x801901f4
    2011-07-15 15:56:12:454  264 dd0 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x801901f4
    2011-07-15 15:56:12:454  264 dd0 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x801901f4
    2011-07-15 15:56:12:454  264 dd0 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x801901f4
    2011-07-15 15:56:12:454  264 dd0 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x801901f4
    2011-07-15 15:56:12:454  264 dd0 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x801901f4
    2011-07-15 15:56:12:454  264 dd0 Misc WARNING: DownloadFileInternal failed for http://SBS01:8530/selfupdate/wuident.cab: error 0x801901f4
    2011-07-15 15:56:12:454  264 dd0 Setup WARNING: SelfUpdate check failed to download package information, error = 0x8024401F
    2011-07-15 15:56:12:454  264 dd0 Setup FATAL: SelfUpdate check failed, err = 0x8024401F
    2011-07-15 15:56:12:454  264 dd0 Agent   * WARNING: Skipping scan, self-update check returned 0x8024401F
    2011-07-15 15:56:12:938  264 dd0 Agent   * WARNING: Exit code = 0x8024401F
    2011-07-15 15:56:12:938  264 dd0 Agent *********
    2011-07-15 15:56:12:938  264 dd0 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2011-07-15 15:56:12:938  264 dd0 Agent *************
    2011-07-15 15:56:12:938  264 dd0 Agent WARNING: WU client failed Searching for update with error 0x8024401f
    2011-07-15 15:56:12:938  264 2138 AU >>##  RESUMED  ## AU: Search for updates [CallId = {3D74536C-D5C0-46AE-A2E4-732392302407}]
    2011-07-15 15:56:12:938  264 2138 AU   # WARNING: Search callback failed, result = 0x8024401F
    2011-07-15 15:56:12:938  264 2138 AU   # WARNING: Failed to find updates with error code 8024401F
    2011-07-15 15:56:12:938  264 2138 AU #########
    2011-07-15 15:56:12:938  264 2138 AU ##  END  ##  AU: Search for updates [CallId = {3D74536C-D5C0-46AE-A2E4-732392302407}]
    2011-07-15 15:56:12:938  264 2138 AU #############
    2011-07-15 15:56:12:938  264 2138 AU Need to show Unable to Detect notification
    2011-07-15 15:56:12:938  264 2138 AU AU setting next detection timeout to 2011-07-15 15:49:03

     

    Best regards

     

    Luke

    Friday, July 15, 2011 3:01 PM
  • 2011-07-15 15:56:12:454  264 dd0 Misc WARNING: DownloadFileInternal failed for http://SBS01:8530/selfupdate/wuident.cab: error 0x801901f4

    This is an HTTP 404 error trying to find the selfupdate services on the WSUS server.

    Either WSUS is not installed on the SBS server, or the 'selfupdate' virtual directory has "Gone Missing".

    Please open IIS on your SBS2008 server and determine if there is a v-root named "WSUS Administrator".

    If so, open that node and determine if there is a v-dir named "selfupdate".


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Friday, July 15, 2011 4:57 PM
    Moderator
  • 2011-07-15 15:56:12:454  264 dd0 Misc WARNING: DownloadFileInternal failed for http://SBS01:8530/selfupdate/wuident.cab: error 0x801901f4

    This is an HTTP 404 error trying to find the selfupdate services on the WSUS server.

    Either WSUS is not installed on the SBS server, or the 'selfupdate' virtual directory has "Gone Missing".

    Please open IIS on your SBS2008 server and determine if there is a v-root named "WSUS Administrator".

    If so, open that node and determine if there is a v-dir named "selfupdate".


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com


    Hi Lawrence

    Thanks for your quick response!

    I have checked on the server and there appears to be both a v-root named WSUS Administrator and also a v-dir named selfupdate. I have uploaded a JPEG screenshot here: http://intellivault.co.uk/images/screen-shot.jpg if this helps.

    I have also check this folder (C:\Program Files\Update Services\Selfupdate) and found the wuident.cab file (that was indicated in the log) there.

    Not sure if it is relevant but when I opened IIS on the server I noticed that I had 2 managers available, IIS 6 and IIS 7. When I opened IIS 6 the only option available where for FTP Sites and that appears to be in a stopped state.

    Also, this may or may not be related but I also have a problem with the internal website the server sets as the default home page for new domain PCs (I think this is its built in SharePoint site), this page doesn't load (HTTP 500 Internal Server Error), the internal address is http://companyweb/ - this is not a major issue as we dont use it anyway, I only mention it in case it is relevant the windows update problem.

    Any further advice you have would be greatly appreciated.

    Best regards

    Luke

    • Proposed as answer by Luke Shepherd Monday, July 18, 2011 4:23 PM
    • Unproposed as answer by Luke Shepherd Monday, July 18, 2011 4:23 PM
    Monday, July 18, 2011 10:21 AM
  • 2011-07-15 15:56:12:454  264 dd0 Misc WARNING: DownloadFileInternal failed for http://SBS01:8530/selfupdate/wuident.cab: error 0x801901f4

    This is an HTTP 404 error trying to find the selfupdate services on the WSUS server.

    Either WSUS is not installed on the SBS server, or the 'selfupdate' virtual directory has "Gone Missing".

    Please open IIS on your SBS2008 server and determine if there is a v-root named "WSUS Administrator".

    If so, open that node and determine if there is a v-dir named "selfupdate".


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com


    Hi Lawrence

    Thanks for your quick response!

    I have checked on the server and there appears to be both a v-root named WSUS Administrator and also a v-dir named selfupdate. I have uploaded a JPEG screenshot here: http://intellivault.co.uk/images/screen-shot.jpg if this helps.

    I have also check this folder (C:\Program Files\Update Services\Selfupdate) and found the wuident.cab file (that was indicated in the log) there.

    Not sure if it is relevant but when I opened IIS on the server I noticed that I had 2 managers available, IIS 6 and IIS 7. When I opened IIS 6 the only option available where for FTP Sites and that appears to be in a stopped state.

    Also, this may or may not be related but I also have a problem with the internal website the server sets as the default home page for new domain PCs (I think this is its built in SharePoint site), this page doesn't load (HTTP 500 Internal Server Error), the internal address is http://companyweb/ - this is not a major issue as we dont use it anyway, I only mention it in case it is relevant the windows update problem.

    Any further advice you have would be greatly appreciated.

    Best regards

    Luke


    I have found a fix!!

    I found this page: http://support.microsoft.com/kb/942062  and followed method 1:

    Method 1

    <script type="text/javascript">// <![CDATA[ loadTOCNode(2, 'resolution'); ]]></script> To resolve this problem, follow these steps:

    1. Start IIS Manager. To do this, click Start, click Run, type inetmgr.exe, and then click OK.
    2. In IIS Manager, expand <var>server name</var>, expand Web sites, and then click the Web site that you want to modify.
    3. In Features view, double-click Directory Browsing.
    4. In the Actions pane, click Enable.

    With the web site being WSUS Administration

    All appears to be working.

    Monday, July 18, 2011 4:26 PM
  • I have found a fix!!

    Unfortunately, it is not an appropriate fix. Enabling "Directory Browing" on a website is never an appropriate configuration option unless you have explicity created a web site for that specific purpose and on a very specific folder tree. Although it is certainly capable of masking the original cause of an HTTP 404 error trying to find the wuident.cab file in that folder.

    Back to the original error -- HTTP 404 -- File Not Found. Since the v-root is present, the v-dir is present, the %ProgramFiles%\Update Services\selfupdate folder is present, and the foray into enabling Directory Browsing has confirmed that the v-root is properly mapped to the filesystem, I'd venture a guess that the ACLs on the %ProgramFiles%\Update Services\selfupdate folder (or higher in the tree) have been modified, essentially making the wuident.cab file invisible to the anonymous user in IIS.

    You should review the settings defined in Appendix C and Appendix D of the WSUS Operations Guide and ensure that your server is properly configured to support WSUS. My educated guess would be that somebody has "locked down" the SBS server, and broken the WSUS functionality in the process.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Monday, July 18, 2011 4:54 PM
    Moderator
  • I have found a fix!!

    Unfortunately, it is not an appropriate fix. Enabling "Directory Browing" on a website is never an appropriate configuration option unless you have explicity created a web site for that specific purpose and on a very specific folder tree. Although it is certainly capable of masking the original cause of an HTTP 404 error trying to find the wuident.cab file in that folder.

    Back to the original error -- HTTP 404 -- File Not Found. Since the v-root is present, the v-dir is present, the %ProgramFiles%\Update Services\selfupdate folder is present, and the foray into enabling Directory Browsing has confirmed that the v-root is properly mapped to the filesystem, I'd venture a guess that the ACLs on the %ProgramFiles%\Update Services\selfupdate folder (or higher in the tree) have been modified, essentially making the wuident.cab file invisible to the anonymous user in IIS.

    You should review the settings defined in Appendix C and Appendix D of the WSUS Operations Guide and ensure that your server is properly configured to support WSUS. My educated guess would be that somebody has "locked down" the SBS server, and broken the WSUS functionality in the process.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com


    Hi Lawrence

    Thanks again for your support.  The only thing I can think that would have changed the server and stopped WSUS working would be a peice of software we had installed called Desktop Authority by ScriptLogic (now owned by Quest), if you are not familier with it, it is a script writing tool for managing desktop PCs and servers on your network.  To be honest with you I did think of this first as the timing of the install coincided (roughly) with the time I noticed the problems start.  I have spoken with ScriptLogic/Quest on a couple of occasions and they have said on each that the product doesnt affect WSUS or IIS.

    I cannot think and any other changes (other than a windows update) that would have an effect.

    I will have a look at the setting from the links you sent to me to see if I can spot anything out of place.

    Regards

    Luke

    Monday, July 18, 2011 6:37 PM
  • This was the correct solution for me!

    Thank you very much!
    Thursday, March 29, 2012 11:57 AM
  • This was the correct solution for me!
    Enabling Directory Browsing is **NOT** an appropriate fix for ANY problem, and certainly not for the one described in this thread.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Friday, March 30, 2012 5:29 PM
    Moderator
  • I had the same problem. For me it was caused by a failing data drive. The process of repairing the drive involved moving the WSUS database to a temporary drive (and all my other data), removing the old drive, setting up a new drive with the original drive letter, then moving it back to the original drive letter (though now on a new mirror). The process somehow failed to update the v-dir location in the last step. SelfUpdate was correctly pointing to the C:\Program Files\Update Services\Selfupdate. However, the contact v-dir was point to drive F: which was my temp drive while preparing the new mirror. Somehow the SBS Console, Server Storage, Move Windows Update Repository Data wizard failed to move it back. Anyway, I updated the content v-dir target dir (in advanced properties of the v-dir in IIS) to point to D:\WSUS\WsusContent\ and clients were again able to get the updates.

    Tuesday, April 10, 2012 9:38 PM
  • Hi,

    I had the same problem and found the solution here. My clients system was SBS 2011 with all Client PC's Win 7.

    None would update. Spent 1 week on & off on this prob & now i'm a free man lol ...

    http://www.sbsfaq.com/?p=3331

    Hope this will help someone. I applied the above fix and rebooted the server. Then rebooted all the Client PC's.

    Wayne.

    Wednesday, July 25, 2012 11:06 AM
  • ...Started after some windows updates installed.

    The problem was ISAPI filter wrong value for ASP.NET_4.0.30319.0
    it had additional slash in the pathway:
    C:\Windows\Microsoft.NET\Framework\v4.0.30319\\aspnet_filter.dll
    fixed:
    C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_filter.dll
    Sunday, August 05, 2012 5:17 PM