Windows Update Error Code 80004002

Discussion in 'Windows Update' started by Erich, Jun 24, 2007.

  1. Erich

    Erich Guest

    Windows Vista Business - can't run Windows update - gives code 80004002.

    Any ideas on how to fix this problem?

    This problem started after I did a registry fix that resolved another issue
    - Windows
    would not recognize either optical drive. Here is a link to the procedure I
    followed to fix the optical drive problem:

    http://support.microsoft.com/kb/314060

    Thanks
    Erich
     
    Erich, Jun 24, 2007
    #1
    1. Advertisements

  2. Try using System Restore to back up to a date before your Windows Update
    problems began.

    Then maybe you might need to find another way of dealing with optical drive
    problems.
     
    Robin Walker [MVP], Jun 24, 2007
    #2
    1. Advertisements

  3. Erich

    Erich Guest

     
    Erich, Jun 24, 2007
    #3
  4. Before doing the items below, ensure that you have disabled all 3rd-party
    anti-virus, anti-spyware, popup-blocker, download accelerator, or firewall.
    If you disabled a 3rd-party firewall, then re-enable Windows Firewall for
    the duration.

    For 32-bit systems, download and save to hard disk, and then install:
    <http://download.windowsupdate.com/v7/windowsupdate/redist/standalone/WindowsUpdateAgent30-x86.exe>

    If this produces an error message about "Update agent already
    installed", then execute the installer again manually, with parameter
    /wuforce as in (at a Windows cmd.exe prompt window):

    WindowsUpdateAgent30-x86.exe /wuforce

    Then visit Microsoft Update again, and report back whether your problem is
    fixed.
     
    Robin Walker [MVP], Jun 24, 2007
    #4
  5. Erich

    Erich Guest

    Thank you Robin but unfortunately I do not have a system restore dated prior
    to the optical drive problem. Any system restore I do, doesn't solve the
    update problem. I was hoping there would be a solution to the Windows Update
    issue other than reformat and reinstall

     
    Erich, Jun 24, 2007
    #5
  6. Erich

    Erich Guest

    Robin thank you, but this did not work.

    I uninstalled McAfee Security Center, uninstalled Comcast Toolbar in case
    that had a pop up blocker, made sure Spysweeper wasn't turned on, and made
    sure the I.E. 7.0 pop up blocker was not enabled.

    Then I downloaded the patch and saved to desktop. I installed it, but at the
    end it gives me this error:

    INSTALL FAILED WITH THE FOLLOWING ERROR CODE 0x80060100.
     
    Erich, Jun 24, 2007
    #6
  7. 80060100 is new on me, was it in fact 800b0100?

    Could you check that your downloaded patch was not corrupt? Right click it,
    select "Properties", click tab "Digital Signature". Select the one digital
    signature listed, then click "Details". Look for the message "The digital
    signature is OK".

    If the digital signature is not OK, please empty your Temporary Internet
    Files, and download the patch again.
    If the digital signature was OK, but Windows Update is still not working,
    then you might need to rename the Catroot2 folder. If this had been XP, the
    instructions would have been:

    a. Click Start, click Run, type cmd, and then click OK.
    b. At the command prompt, type the following commands, and then press ENTER
    after each command:

    net stop cryptsvc
    ren %systemroot%\System32\Catroot2 oldcatroot2
    net start cryptsvc
    exit

    but given this is Vista, you will need to launch the cmd.exe with
    Administrator privileges
     
    Robin Walker [MVP], Jun 24, 2007
    #7
  8. Erich

    Erich Guest

    Thank you Robin, but did not work.

    The digital signiture was ok. Also you are right it was error 800b0100

    I ran cmd.exe from the C:\ as an Administrator. I wasn't in any specific
    directory - just at the C:\
    I typed the commands you listed, and I got confirmation the service both
    stopped and started. But
    I get the same error when trying to install the patch.

    I guess I really hosed the operating system when doing the registry fix for
    the optical drives - those work great but Windows Update won't work.

    Also, I ran into something on google that said to try the diagnostics on
    Microsoft Genuine Software to be sure it recognizes my OS as legitimate and
    it does.

    Would portions from the Windows Update log files help you? I copied and
    pasted some below:

    2007-06-24 17:17:39:705 2028 f70 WUApp FATAL: Failed to initialize WU app,
    hr=80004002
    2007-06-24 17:17:39:705 2028 f70 WUApp WARNING: Cannot load updates because
    AU service is not available, hr=80010108
    2007-06-24 17:17:39:705 2028 f70 WUApp WARNING: Failed to load the update
    list, error 80010108
    2007-06-24 17:17:39:705 2028 f70 WUApp WARNING: Failed to populate update
    list with error 80010108
    2007-06-24 17:17:39:721 2028 f70 WUApp WARNING: Error displaying Opted In
    Service summary: 80004002
    2007-06-24 17:18:24:907 1152 f80 Agent *********** Agent: Initializing
    Windows Update Agent ***********
    2007-06-24 17:18:24:907 1152 f80 Agent *********** Agent: Initializing
    global settings cache ***********
    2007-06-24 17:18:24:908 1152 f80 Agent * WSUS server: <NULL>
    2007-06-24 17:18:24:908 1152 f80 Agent * WSUS status server: <NULL>
    2007-06-24 17:18:24:908 1152 f80 Agent * Target group: (Unassigned
    Computers)
    2007-06-24 17:18:24:908 1152 f80 Agent * Windows Update access disabled: No
    2007-06-24 17:18:24:923 1152 f80 DnldMgr Download manager restoring 0
    downloads
    2007-06-24 17:18:24:932 1152 f80 DnldMgr Retrieved 1 persisted download jobs
    2007-06-24 17:18:24:932 1152 f80 DnldMgr *********** DnldMgr: Restoring
    download [no. 0] ***********
    2007-06-24 17:18:24:933 1152 f80 DnldMgr * BITS JobId =
    {76C0B5C7-1CE1-46F8-8365-D851A9380D7B}
    2007-06-24 17:18:24:933 1152 f80 DnldMgr * ServiceId =
    {7971F918-A847-4430-9279-4A52D1EFE18D}
    2007-06-24 17:18:24:947 1152 f80 DnldMgr * UpdateId =
    {C432BA5C-BA8E-47C5-B9F2-E51DD481DD05}.100
    2007-06-24 17:18:25:252 1152 f80 DnldMgr * Restored download job.
    2007-06-24 17:18:25:253 1152 f80 AU ########### AU: Initializing Automatic
    Updates ###########
    2007-06-24 17:18:25:255 1152 f80 AU # Approval type: Scheduled (User
    preference)
    2007-06-24 17:18:25:255 1152 f80 AU # Scheduled install day/time: Every
    day at 3:00
    2007-06-24 17:18:25:255 1152 f80 AU # Auto-install minor updates: Yes
    (User preference)
    2007-06-24 17:18:25:283 1152 f80 AU Setting AU scheduled install time to
    2007-06-25 08:00:00
    2007-06-24 17:18:25:284 1152 f80 Report *********** Report: Initializing
    static reporting data ***********
    2007-06-24 17:18:25:284 1152 f80 Report * OS Version = 6.0.6000.0.0.65792
    2007-06-24 17:18:25:284 1152 f80 Report * OS Product Type = 0x00000006
    2007-06-24 17:18:25:665 1152 f80 Report * Computer Brand = MSI
    2007-06-24 17:18:25:665 1152 f80 Report * Computer Model = MS-7260
    2007-06-24 17:18:25:683 1152 f80 Report * Bios Revision = 080014
    2007-06-24 17:18:25:683 1152 f80 Report * Bios Name = Default System BIOS
    2007-06-24 17:18:25:683 1152 f80 Report * Bios Release Date =
    2006-06-02T00:00:00
    2007-06-24 17:18:25:683 1152 f80 Report * Locale ID = 1033
    2007-06-24 17:18:25:976 1152 f80 AU AU finished delayed initialization
    2007-06-24 17:18:25:976 1152 f80 AU #############
    2007-06-24 17:18:25:976 1152 f80 AU ## START ## AU: Search for updates
    2007-06-24 17:18:25:976 1152 f80 AU #########
    2007-06-24 17:18:26:564 1152 f80 AU <<## SUBMITTED ## AU: Search for updates
    [CallId = {888560D5-D631-4D0A-B956-0AD69DEC4F1D}]
    2007-06-24 17:18:26:564 1152 c94 Agent *************
    2007-06-24 17:18:26:564 1152 c94 Agent ** START ** Agent: Finding updates
    [CallerId = AutomaticUpdates]
    2007-06-24 17:18:26:564 1152 c94 Agent *********
    2007-06-24 17:18:57:716 1152 c94 Driver DriverUtil marking
    {FD6916D9-3190-41A6-AF31-25B50640F007}.100 e_detectionStateInstallable
    2007-06-24 17:18:57:716 1152 c94 Driver Matched driver to device
    PCI\VEN_168C&DEV_0013&SUBSYS_3A1B1186&REV_01
    2007-06-24 17:18:57:716 1152 c94 Driver Status: 0x180200a, ProblemNumber:
    00000000
    2007-06-24 17:18:57:716 1152 c94 Driver Calculated driver attributes as
    0x00000000
    2007-06-24 17:18:58:719 1152 c94 Agent Update
    {BEBCED00-3E31-4649-A072-4EC77BDA7A17}.100 is pruned out due to potential
    supersedence
    2007-06-24 17:18:58:719 1152 c94 Agent Update
    {77AE3909-75F9-4C68-BFAB-860573A479DF}.100 is pruned out due to potential
    supersedence
    2007-06-24 17:18:58:719 1152 c94 Agent Update
    {F1CDD19E-F1DD-4DEE-B6B1-32DC63BA2BF0}.100 is pruned out due to potential
    supersedence
    2007-06-24 17:18:58:719 1152 c94 Agent * Added update
    {F68AD52F-5569-4B8E-8256-B391BBB0AADF}.100 to search result
    2007-06-24 17:18:58:719 1152 c94 Agent * Added update
    {FD6916D9-3190-41A6-AF31-25B50640F007}.100 to search result
    2007-06-24 17:18:58:719 1152 c94 Agent * Found 2 updates and 32 categories
    in search
    2007-06-24 17:18:58:726 1152 c94 Agent *********
    2007-06-24 17:18:58:726 1152 c94 Agent ** END ** Agent: Finding updates
    [CallerId = AutomaticUpdates]
    2007-06-24 17:18:58:726 1152 c94 Agent *************
    2007-06-24 17:18:58:728 1152 7fc AU >>## RESUMED ## AU: Search for updates
    [CallId = {888560D5-D631-4D0A-B956-0AD69DEC4F1D}]
    2007-06-24 17:18:58:728 1152 7fc AU # 2 updates detected
    2007-06-24 17:18:58:739 1152 7fc AU WARNING: AU ignoring update during
    offline scan:
    2007-06-24 17:18:58:740 1152 7fc AU #########
    2007-06-24 17:18:58:740 1152 7fc AU ## END ## AU: Search for updates
    [CallId = {888560D5-D631-4D0A-B956-0AD69DEC4F1D}]
    2007-06-24 17:18:58:740 1152 7fc AU #############
    2007-06-24 17:18:58:740 1152 7fc AU Setting AU scheduled install time to
    2007-06-25 08:00:00
    2007-06-24 17:18:58:745 1152 c94 Report REPORT EVENT:
    {71DDB8F0-C629-432E-907C-A367B6775DCD} 2007-06-24
    17:18:25:284-0500 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
     
    Erich, Jun 24, 2007
    #8
  9. Erich

    Sato Guest

    I also have this silly problem. I am experience blue screens with the error
    - bad_pool_header - and the recommended fix is to run an update.

    Unfortunately due to the 80004002 error I can't!!

    Hope someone can help.
     
    Sato, Jun 27, 2007
    #9
  10. Erich

    Chankys Guest

    Exactly the same problem here and no solution yet... :((((((((((((((((((
     
    Chankys, Jul 3, 2007
    #10
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.