Re: Windows Update Error 0x800C0008 after updating the WU client

From: J. Merrill (jvm_cop_at_SPAMCOP.NET)
Date: 01/26/04

  • Next message: Sergey V. Gordeychik: "Error in Security Configuration Manager"
    Date:         Mon, 26 Jan 2004 14:37:28 -0500
    To: NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM
    
    

    Interesting that MS's DLL Help Database
         http://support.microsoft.com/servicedesks/fileversion/dllinfo.asp
    doesn't know about the 5.4.3790.17 versions, but does know about 5.4.3790.0 versions of all of those files -- I wonder why your wuauserv.dll and wupdmgr.exe didn't get updated to at least 5.4.3790.0.

    What are the dates on the files you have? If they're quite recent, perhaps the DLL Help Database just doesn't have the info about those versions yet.

    Have you tried turning on the Active Setup "debugging" mechanism as indicated by
         http://support.microsoft.com/default.aspx?scid=kb;en-us;248439

    It would be rather scary if these files didn't actually come from MS, and are a very advanced worm of some kind. Can you confirm that the files you have were signed by MS? (wuaueng.dll seems to be an ActiveX control so it should be signed, even if the others aren't.) I have a feeling that MS would not cause Windows Update to prompt you about whether you want to download a new Windows Update component.)

    Good luck.

    At 02:13 PM 1/24/2004, Joe Dance wrote (in part)
    >[snip]
    >In both cases, this behavior started right AFTER the Windows Update client
    >was updated by the Windows Update website. I checked the file versions
    >before and after:
    >
    >wuauclt.exe went from version "5.4.3630.1106 (xpsp1.020828-1920)"
    >to "5.4.3790.17 built by: lab04_n"
    >wuaueng.dll also went from version "5.4.3630.1106 (xpsp1.020828-1920)"
    >to "5.4.3790.17 built by: lab04_n"
    >wuauserv.dll remained at version "5.4.3630.1106 (xpsp1.020828-1920)"
    >wupdmgr.exe remained at version "5.4.2600.0 (XPClient.010817-1148)"
    >
    >Both systems also display only two Automatic Updates policies in the policy
    >editor, as though they were running an earlier client, before Windows 2000
    >SP3 and Windows XP SP1.
    >
    >I found no relevant information on the Windows Update troubleshooting page,
    >or in the knowledgebase.
    >
    >Joe Dance
    >University of South Carolina

    J. Merrill / Analytical Software Corp

    -----
    NTBugtraq Editor's Note:

    I'm looking for an event at which I can speak in Australia, specifically near Brisbase, as close to Christmas as possible. Anyone interested in flying me down under at that time, please contact me at Russ.Cooper@rc.on.ca
    -----


  • Next message: Sergey V. Gordeychik: "Error in Security Configuration Manager"

    Relevant Pages

    • Re: ITTAPI->Initialize() throws exception
      ... See DLL Help Database: ... You may want to apply the latest SP and run Windows Update if haven't already ... Microsoft MVP for TAPI / Windows SDK ... * Please post all messages and replies to the newsgroup so all may ...
      (microsoft.public.win32.programmer.tapi)
    • Re: error message 0x80072EE4
      ... System-wide proxy settings corrupt. ... How the Windows Update client determines which proxy server to use to connect to ... [CallerId = MicrosoftUpdate] ...
      (microsoft.public.windowsupdate)
    • RE: Error number: 0x80072F78
      ... Do you know where to change the windows update client to use the proxy ... >>I have been searching this message thread with no luck ...
      (microsoft.public.windowsupdate)
    • Re: Failed updates
      ... I have the same problem, d/l 46 new updates and about 10 are marked *failed*, repeated 3 times to no avail, I have d/l the new update tool, I'm on the auto updates, but still get failure notices, now what?? ... if you chose not to update Windows Update client ... ... I don't have the new windows update client installed nor am I going to do so. ... I did run the genuine advantage standalone tool without incident (everything ...
      (microsoft.public.windowsupdate)
    • Re: Windows Update Failing - Error 0x800A0046
      ... the propositions for xp didn't work and I know of ... another guy with this symptoms since July 21. ... not only does the windows update client ...
      (microsoft.public.win2000.windows_update)