none
Installer module and update 7.0.6000.381 errors

    Question

  • I am getting windows installer module has stopped working error

    I have traced the erro back to update 7.0.6000.381 it installed and was successful on the 23rd August, since then it has tried to install a further 17 times, each time either canceled or failed.

     

    Any ideas on how to stop this problem, can i unthe install any how - it does not appear in the list of updates that can be removed.

     

    Is it possible to download the update on its own and run and apply it with out using windows update?

     

     

    Thursday, August 30, 2007 1:03 PM

All replies

  • The 7.0.6000.381 shows as failed in my history also with error 8024D00F but Microsoft has no posted information for that error code.

    Tuesday, September 4, 2007 2:52 PM
  •  

    I get the same, windows fails on every attempt to install this with error ose.exe, but i don't even have office installed? what is going on?
    Monday, September 10, 2007 3:31 PM
  • I have the same problem and it seems to be stopping me updating vista ever since but as you say I also cannot find any helpful threads on here. Someone helppppppppppppp!!!!! lol.

     

    Saturday, September 15, 2007 8:05 PM
  • Me too.... Anyone have anything?
    Saturday, September 15, 2007 11:00 PM
  • I have tried all the suggested fixes in the knowledge base even the last one of removing office 2003 and reinstalling it but to no avail and it appears that it doesn't matter if you have office or not for this to happen think it must be something else causing it come on microsoft give us a clue !!!!!!

     

    Sunday, September 16, 2007 11:11 AM
  • I've attempted most things that I can think of and some that I couldn't.

    1) Install in safe mode - Windows update apparently cannot run in safe mode.  This seems like a strange restriction
    2) Download and install the updater manually. - No change
    3) Reboot reboot reboot - No change

    Below is every piece of information I know to look for on this.  This is a total pain!

    Details on the error
    ==============

    Update History:
    Error Details: 800F081F

    C:\Windows\Update.log:
    2007-09-16    08:36:36:011    1128    17b0    AU    AU deferring detection until wake-up from hibernation
    2007-09-16    08:36:36:011    1128    17b0    AU    Forced install timer expired for scheduled install
    2007-09-16    08:36:36:012    1128    17b0    AU    UpdateDownloadProperties: 0 download(s) are still in progress.
    2007-09-16    08:36:36:012    1128    17b0    AU    Setting AU scheduled install time to 2007-09-17 07:00:00
    2007-09-16    08:36:36:018    1128    1574    Report    WARNING: Reporter failed to upload events with hr = 8024000c.
    2007-09-16    08:36:36:018    1128    1574    Report    WARNING: Reporter failed to upload events with hr = 8024000c.
    2007-09-16    08:36:36:018    1128    1574    Report    WARNING: Reporter failed to upload events with hr = 8024000c.
    2007-09-16    08:36:36:018    1128    1574    Report    WARNING: Reporter failed to upload events with hr = 8024000c.
    2007-09-16    08:36:39:320    1128    1574    Misc    Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
    2007-09-16    08:36:39:327    1128    1574    Misc     Microsoft signed: Yes
    2007-09-16    08:36:39:363    1128    1574    Misc    Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
    2007-09-16    08:36:39:369    1128    1574    Misc     Microsoft signed: Yes
    2007-09-16    08:36:39:376    1128    1574    Report    Uploading 1 events using cached cookie, reporting URL = http://stats.update.microsoft.com/ReportingWebService/ReportingWebService.asmx
    2007-09-16    08:36:48:279    1128    17b0    AU    Triggering Online detection (non-interactive)
    2007-09-16    08:37:18:279    1128    17b0    AU    #############
    2007-09-16    08:37:18:279    1128    17b0    AU    ## START ##  AU: Search for updates
    2007-09-16    08:37:18:279    1128    17b0    AU    #########
    2007-09-16    08:37:18:282    1128    17b0    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {C33BE9D8-28F2-4ABA-B91F-458A6795DB6E}]
    2007-09-16    08:37:46:067    1128    1574    Report    Reporter successfully uploaded 1 events.
    2007-09-16    08:37:46:068    1128    1574    Agent    *************
    2007-09-16    08:37:46:068    1128    1574    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2007-09-16    08:37:46:068    1128    1574    Agent    *********
    2007-09-16    08:37:46:068    1128    1574    Agent      * Online = Yes; Ignore download priority = No
    2007-09-16    08:37:46:068    1128    1574    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"
    2007-09-16    08:37:46:068    1128    1574    Agent      * ServiceID = {7971F918-A847-4430-9279-4A52D1EFE18D}
    2007-09-16    08:37:46:068    1128    1574    Setup    Checking for agent SelfUpdate
    2007-09-16    08:37:46:070    1128    1574    Setup    Client version: Core: 7.0.6000.374  Aux: 7.0.6000.374
    2007-09-16    08:37:46:133    1128    1574    Misc    Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
    2007-09-16    08:37:46:153    1128    1574    Misc     Microsoft signed: Yes
    2007-09-16    08:37:46:257    1128    1574    Misc    Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
    2007-09-16    08:37:46:266    1128    1574    Misc     Microsoft signed: Yes
    2007-09-16    08:37:46:310    1128    1574    Agent    Checking for updated auth cab for service 7971f918-a847-4430-9279-4a52d1efe18d at http://www.update.microsoft.com/v7/microsoftupdate/redir/muauth.cab
    2007-09-16    08:37:46:310    1128    1574    Misc    Validating signature for C:\Windows\SoftwareDistribution\AuthCabs\authcab.cab:
    2007-09-16    08:37:46:318    1128    1574    Misc     Microsoft signed: Yes
    2007-09-16    08:37:46:515    1128    1574    Misc    Validating signature for C:\Windows\SoftwareDistribution\AuthCabs\authcab.cab:
    2007-09-16    08:37:46:523    1128    1574    Misc     Microsoft signed: Yes
    2007-09-16    08:37:46:538    1128    1574    Misc    Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
    2007-09-16    08:37:46:548    1128    1574    Misc     Microsoft signed: Yes
    2007-09-16    08:37:46:577    1128    1574    Misc    Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
    2007-09-16    08:37:46:586    1128    1574    Misc     Microsoft signed: Yes
    2007-09-16    08:37:46:605    1128    1574    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2007-09-16    08:37:46:614    1128    1574    Misc     Microsoft signed: Yes
    2007-09-16    08:37:46:695    1128    1574    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2007-09-16    08:37:46:705    1128    1574    Misc     Microsoft signed: Yes
    2007-09-16    08:37:46:712    1128    1574    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2007-09-16    08:37:46:719    1128    1574    Misc     Microsoft signed: Yes
    2007-09-16    08:37:46:748    1128    1574    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2007-09-16    08:37:46:757    1128    1574    Misc     Microsoft signed: Yes
    2007-09-16    08:37:46:798    1128    1574    Setup    Determining whether a new setup handler needs to be downloaded
    2007-09-16    08:37:46:798    1128    1574    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
    2007-09-16    08:37:46:809    1128    1574    Misc     Microsoft signed: Yes
    2007-09-16    08:37:46:809    1128    1574    Setup    SelfUpdate handler update NOT required: Current version: 7.0.6000.381, required version: 7.0.6000.381
    2007-09-16    08:37:46:809    1128    1574    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.0.6000.381"
    2007-09-16    08:37:47:011    1128    1574    Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.0.6000.381" is applicable but is already staged; it will not be downloaded.
    2007-09-16    08:37:47:012    1128    1574    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.0.6000.381"
    2007-09-16    08:37:47:493    1128    1574    Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.0.6000.381" is applicable but is already staged; it will not be downloaded.
    2007-09-16    08:37:47:495    1128    1574    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.0.6000.381"
    2007-09-16    08:37:47:790    1128    1574    Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.0.6000.381" is applicable but is already staged; it will not be downloaded.
    2007-09-16    08:37:47:792    1128    1574    Setup    SelfUpdate check completed.  SelfUpdate is required.
    2007-09-16    08:37:47:793    1128    1574    Setup    Downloading binaries required for SelfUpdate
    2007-09-16    08:37:47:793    1128    1574    Setup    Download of SelfUpdate binaries succeeded
    2007-09-16    08:37:47:793    1128    1574    Setup    Starting agent SelfUpdate
    2007-09-16    08:37:47:815    1128    1574    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
    2007-09-16    08:37:47:825    1128    1574    Misc     Microsoft signed: Yes
    2007-09-16    08:37:47:827    1128    1574    Report    REPORT EVENT: {0860D1ED-7622-4C0C-86A4-C6E46CB57B3A}    2007-09-16 08:37:47:826-0400    1    201    101    {E2FF4526-97D7-4926-8E75-295DBA39C6BF}    1    0    SelfUpdate    Success    Content Install    Installation pending.
    2007-09-16    08:37:47:861    1128    1574    Misc    Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
    2007-09-16    08:37:47:869    1128    1574    Misc     Microsoft signed: Yes
    2007-09-16    08:37:47:879    1128    1574    Misc    Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
    2007-09-16    08:37:47:886    1128    1574    Misc     Microsoft signed: Yes
    2007-09-16    08:37:47:895    1128    1574    Report    Uploading 1 events using cached cookie, reporting URL = http://stats.update.microsoft.com/ReportingWebService/ReportingWebService.asmx
    2007-09-16    08:37:48:196    1128    1574    Report    Reporter successfully uploaded 1 events.
    2007-09-16    08:37:49:546    1128    1574    Setup    Launching WuSetupV.exe to complete SelfUpdate
    2007-09-16    08:37:49:580    1128    1574    Setup    WuSetupV.exe launched successfully
    2007-09-16    08:37:49:581    1128    1574    Agent      * WARNING: Skipping scan, self-update check returned 0x8024001B
    2007-09-16    08:37:49:624    1128    1574    Agent      * WARNING: Exit code = 0x8024001B
    2007-09-16    08:37:49:624    1128    1574    Agent    *********
    2007-09-16    08:37:49:624    1128    1574    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2007-09-16    08:37:49:624    1128    1574    Agent    *************
    2007-09-16    08:37:49:624    1128    1574    Agent    WARNING: WU client failed Searching for update with error 0x8024001b
    2007-09-16    08:37:49:625    1128    171c    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {C33BE9D8-28F2-4ABA-B91F-458A6795DB6E}]
    2007-09-16    08:37:49:625    1128    171c    AU      # WARNING: Search callback failed, result = 0x8024001B
    2007-09-16    08:37:49:625    1128    171c    AU      # WARNING: Failed to find updates with error code 8024001B
    2007-09-16    08:37:49:625    1128    171c    AU    #########
    2007-09-16    08:37:49:625    1128    171c    AU    ##  END  ##  AU: Search for updates [CallId = {C33BE9D8-28F2-4ABA-B91F-458A6795DB6E}]
    2007-09-16    08:37:49:625    1128    171c    AU    #############
    2007-09-16    08:37:49:626    1128    171c    AU    Setting AU scheduled install time to 2007-09-17 07:00:00
    2007-09-16    08:37:49:988    2192    918    Misc    ===========  Logging initialized (build: 7.0.6000.381, tz: -0400)  ===========
    2007-09-16    08:37:49:988    2192    918    Misc      = Process: C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe
    2007-09-16    08:37:49:984    2192    918    Setup    Performing SelfUpdate installation
    2007-09-16    08:37:50:017    1128    17b0    AU    ###########  AU: Uninitializing Automatic Updates  ###########
    2007-09-16    08:37:50:038    1128    17b0    Setup    Service shutting down while setup is in progress.  Attempting to unload core client binaries
    2007-09-16    08:37:50:038    1128    17b0    Setup    Attempting to close open Windows Update explorer windows
    2007-09-16    08:37:51:314    1128    17b0    Setup    Attempting to unload unused libraries from svchost
    2007-09-16    08:37:55:038    1128    17b0    Setup    Attempting to unload binaries from event log service
    2007-09-16    08:37:55:284    1128    17b0    Service    *********
    2007-09-16    08:37:55:284    1128    17b0    Service    **  END  **  Service: Service exit [Exit code = 0x240001]
    2007-09-16    08:37:55:284    1128    17b0    Service    *************
    2007-09-16    08:37:56:019    2192    918    Setup    Installing setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.0.6000.381"
    2007-09-16    08:37:59:695    2192    918    Setup    WARNING: CBS installation failed, error = 0x800F081F
    2007-09-16    08:37:59:698    2192    918    Setup    WARNING: Install of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.0.6000.381" failed, error = 0x800F081F
    2007-09-16    08:37:59:698    2192    918    Setup    FATAL: Failed to install package, error = 0x800F081F
    2007-09-16    08:37:59:698    2192    918    Setup    WARNING: Installing applicable setup packages failed, error = 0x800F081F
    2007-09-16    08:38:00:083    1128    13c0    Misc    ===========  Logging initialized (build: 7.0.6000.374, tz: -0400)  ===========
    2007-09-16    08:38:00:083    1128    13c0    Misc      = Process: C:\Windows\system32\svchost.exe
    2007-09-16    08:38:00:083    1128    13c0    Misc      = Module: c:\windows\system32\wuaueng.dll
    2007-09-16    08:38:00:083    1128    13c0    Service    *************
    2007-09-16    08:38:00:083    1128    13c0    Service    ** START **  Service: Service startup
    2007-09-16    08:38:00:083    1128    13c0    Service    *********
    2007-09-16    08:38:00:101    1128    13c0    Agent      * WU client version 7.0.6000.374
    2007-09-16    08:38:00:104    1128    13c0    Agent      * Base directory: C:\Windows\SoftwareDistribution
    2007-09-16    08:38:00:104    1128    13c0    Agent      * Access type: No proxy
    2007-09-16    08:38:00:105    1128    13c0    Agent      * Network state: Connected
    2007-09-16    08:38:00:114    1128    13c0    Setup    Service restarting after SelfUpdate
    2007-09-16    08:38:00:114    1128    13c0    Setup    Client version: Core: 7.0.6000.374  Aux: 7.0.6000.374
    2007-09-16    08:38:00:116    1128    13c0    Setup    WARNING: SelfUpdate package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.0.6000.381" install failed, hr = 800F081F
    2007-09-16    08:38:00:490    1128    13c0    Report    ***********  Report: Initializing static reporting data  ***********
    2007-09-16    08:38:00:490    1128    13c0    Report      * OS Version = 6.0.6000.0.0.66304
    2007-09-16    08:38:00:490    1128    13c0    Report      * OS Product Type = 0x00000003
    2007-09-16    08:38:00:580    1128    13c0    Report      * Computer Brand = Hewlett-Packard
    2007-09-16    08:38:00:580    1128    13c0    Report      * Computer Model = HP Pavilion dv6000 (GL913UA#ABC) 
    2007-09-16    08:38:00:588    1128    13c0    Report      * Bios Revision = F.38   
    2007-09-16    08:38:00:588    1128    13c0    Report      * Bios Name = PhoenixBIOS 4.0 Release 6.1    
    2007-09-16    08:38:00:588    1128    13c0    Report      * Bios Release Date = 2007-06-20T00:00:00
    2007-09-16    08:38:00:588    1128    13c0    Report      * Locale ID = 4105
    2007-09-16    08:38:00:591    1128    13c0    Setup    FATAL: SelfUpdate core package installation failed, err = 0x800F081F
    2007-09-16    08:38:00:867    1128    13c0    Service      * Service restarted after self update
    2007-09-16    08:38:00:867    1128    13c0    Service    WARNING: Failed to read back selfupdate handle from environment variable with error 0
    2007-09-16    08:38:02:728    2192    918    Setup    WuSetup has finished.  Exit code is 0x00000000
    2007-09-16    08:38:05:591    1128    10f0    Report    REPORT EVENT: {201DDB33-6D91-4EB1-9C6B-503557EB9FF5}    2007-09-16 08:38:00:591-0400    1    195    101    {E2FF4526-97D7-4926-8E75-295DBA39C6BF}    1    800f081f    SelfUpdate    Failure    Content Install    Installation Failure: Windows failed to install the following update with error 0x800f081f: Windows Update Core.

    Control Panel -> Administrative Tools -> Event Viewer:  (I stopped at about 15 that seem to be related)
    1) Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: The data is invalid.
    .
    2) Installation Failure: Windows failed to install the following update with error 0x800f081f: Windows Update Core.
    3) Windows Servicing failed to complete the process of setting package WUClient-SelfUpdate-Core (Feature Pack) into Default(Default) state
    4) Windows Servicing failed to complete the process of setting package WUClient-SelfUpdate-Core-Package-en-US-MiniLP (Feature Pack) into Default(Default) state
    5) Windows Servicing failed to complete the process of setting package WindowsUpdateClient-SelfUpdate-Core-UIComp-Package_en-US (Language Pack) into Default(Default) state
    6) Windows Servicing failed to complete the process of setting package WindowsUpdateClient-SelfUpdate-Core-CoreComp-Package_en-US (Language Pack) into Default(Default) state
    7) Windows Servicing failed to complete the process of setting package WindowsUpdateClient-SelfUpdate-Core-Package (Language Pack) into Resolved(Resolved) state
    8) Windows Servicing failed to complete the process of changing update Core from package WindowsUpdateClient-SelfUpdate-Core-CoreComp-Package(Update) into Staging(Staging) state
    9) Windows Servicing failed to complete the process of changing update AdmComp from package WindowsUpdateClient-SelfUpdate-Core-Package(Update) into Staging(Staging) state
    10) Windows Servicing failed to complete the process of changing update WUClient-SelfUpdate-Core-zh-HK-LP-Toplevel from package WUClient-SelfUpdate-Core(Feature Pack) into Staging(Staging) state
    11) Windows Servicing failed to complete the process of changing update WUClient-SelfUpdate-Core-uk-UA-LP-Toplevel from package WUClient-SelfUpdate-Core(Feature Pack) into Staging(Staging) state
    12) Windows Servicing failed to complete the process of changing update WUClient-SelfUpdate-Core-th-TH-LP-Toplevel from package WUClient-SelfUpdate-Core(Feature Pack) into Staging(Staging) state
    13)Windows Servicing failed to complete the process of changing update WUClient-SelfUpdate-Core-sl-SI-LP-Toplevel from package WUClient-SelfUpdate-Core(Feature Pack) into Staging(Staging) state
    14) Windows Servicing failed to complete the process of changing update WUClient-SelfUpdate-Core-sk-SK-LP-Toplevel from package WUClient-SelfUpdate-Core(Feature Pack) into Staging(Staging) state
    Sunday, September 16, 2007 1:38 PM
  • Windows Update software 7.0.6000.381

    Installation date: ‎9/‎20/‎2007 9:06 PM

    Installation status: Failed

    Error details: Code 80070002

    Update type: Important

     

    I have been researching this problem for a week now. Need help! Same problem. No answers from Microsoft. Tried to find an .exe file that I could manually install with no luck. Any solutions?

     

    Thanks, Belewarmy

    Thursday, September 20, 2007 6:43 PM
  • I still don't have anything, but i am a bit surprised that not one person from microsoft has responded to my e-mails.  I don't know if you guys got anything?

     

    Thanks

    Friday, September 21, 2007 10:44 AM
  • I've seen nothing, but haven't opened an official complaint ticket.  Has anyone taken on that?
    Friday, September 21, 2007 5:22 PM
  •  

    Hi all!

     

    I've been suffering the same issue since I restored a HDD image. WU Client does not update itself, though it successfully downloads all the necessary patches & updates. I'm trying to update to WU 7.0.6000.381 from .374: the update is downloaded but it can't be installed (giving error code 80070643). Funnily enough, whenever WU cannot install any update for Vista, ALL PATCHES FOR OFFICE 2007 ARE CORRECTLY INSTALLED (before and after the WU client tried to update itself).

     

    I've renamed the Catroot folders for no good, and have deleted the specific certificates for WU 7.0.6000.381 in the Catalog DB  (in one of the Catroot subfolders). The WU manager has asked me to reboot my PC in order to install the necessary files, but once this was done, the same error showed up again.

     

    I guess the DOWNLOADED package for WU .381 might be corrupted at the server itself, as I've deleted all previous updated (using Free Disk Space in System Tools) and, as it should, the update was downloaded again.

     

    Again, this has nothing to do with the Office Source Engine, as the correctly installed updates for Office 2007 prove.

     

    Hope to get some results before Christmas, gosh!

     

    Plxpisa

     

    Saturday, September 22, 2007 9:11 AM
  • Turned in a request and received email on 8/28 saying a pro would contact within 24 hours to assist. That was the last I heard from anyone.

     

    Tuesday, September 25, 2007 3:36 AM
  • Uninstall Comodo Personal Firewall beta helps for me.

    http://forums.comodo.com/32_bit_bug_reports/vista_updates_major_bug-t12182.0.html
    Thursday, September 27, 2007 3:37 PM
  • Good to know that compatibility issue with Comodo Firewall, but that's not my case. Just in case, I'm only using Windows Firewall, and I even created exceptions to allow all traffic from/to Wuauclt.exe and Wuapp.exe to no good end.

     

    I've also checked that deleting the correspondign folder under SofwareDistribution doesn't help either. We're getting closer, but I still haven't found the corrupt file and/or registry entry (there are too meny references to WU 7.0.6000.381 in the registry to dare clean them manually).

     

    Keep testing!

     

    Thursday, September 27, 2007 4:41 PM
  • WOW thank you this helped me as I was running comodo.

     

    Everything updated yesturday and we are good to go. 

     

    Thanks

     

     

    Sunday, September 30, 2007 12:44 PM
  • Unfortunately, that's no good for me.  Running Norton Internet Security.
    Tried updating with the firewall shut down with no change.
    Anyone else with suggestions?
    Sunday, September 30, 2007 1:49 PM
  • I tried the same thing, I shut my down and it still did not want to update, it was not untill i uninstalled it completely from my system that it worked like charm.

    I would try that see if that works,  you got nothing else to loose.

    TJ
    Sunday, September 30, 2007 1:53 PM
  • Uninstall Norton completely?  Seriously?  Wow if this works one more reason for me not to like Norton....  Not that pleased with Microsoft at the moment either though I still can find no official statement on this error code anywhere

     

    Sunday, September 30, 2007 3:07 PM
  • Well it seems I'm helpless here. I've uninstalled my AV (Avast 4.7) and any other security software I had running in my PC. I turned off Windows Firewall and rebooted. Tried to use Windows Update. Didn't work either, so the root of the issue (at least in my case) seems not to be a specific application blocking traffic from WU.

     

    The Windows Defender updates are correctly done when started manually. Manual updates work fine as well. Has anybody else found out something else (apart from uninstalling AV/Firewalls)?

     

    Monday, October 1, 2007 3:54 PM
  • I am in the same position as others after reading this thread at least I know I am not alone. I have Vista Premium and Norton Security and can no longer update. WU is stuck on 7.0.6000.381. I can't uninstall my firewall or antivirus as they came pre-installed on my laptop and although licensed I do not have a separate installer. I have however found something very interesting and probably key to the whole issue. Please read the following link and comment if you think it is relevant

     

    http://blogs.pcworld.com/staffblog/archives/005417.html

    Monday, October 1, 2007 8:45 PM
  • Well that didn't work.  Uninstalled Norton completely and totally rebooted and the exact same error code and failure.  I also left the windows firewall down during this testing so again confirming what has been said before.  This must be a problem with the update.  Why is it that there is no indication anywhere on the microsoft site about this update?  Surely they've had tonnes of people running into this?

    As far as the link just posted I don't see how this helps.  There doesn't appear to be any suggestions on how to correct the problem, but is just an indication that the update was pushed to computers who didn't necessarily have it set to get it automatically.

    *sigh*  Anyone else with ideas?
    Monday, October 1, 2007 8:56 PM
  • I can't find any satisfactory solution for this anywhere. It looks to me like the AV/Firewall software is doing it's job just this is an unconventional update. Althought the link I posted doesn't offer a fix (shame), it might answer the question "Why is it that there is no indication anywhere on the microsoft site about this update?" (or might not).

     

    The ideal for me would be a separate fully packaged and tested release of the new version of Windows Update that can be re-installed on Vista. I have tried following various links and they all give an unrecoverable error when you try to install on Vista. If you try to use Microsoft Update instread of Windows Update the Microsoft Update site launches Windows Update. I feel like I am going around in circles.

    Monday, October 1, 2007 10:33 PM
  • Another fellow sufferer, essentially no matter what I try 381 will not update over 374. There are loads of articles saying use the /wuflush parameter but this makes no difference whatsoever.

    The diagnostic that OSE.exe is corrupt is a complete red herring.

    The only strange thing is that if you use the /uninstall flag you get a report that the update was successful, but that too is false and looks like a bug in the installer.

    Can't understand why Microsoft is so quiet on this one, there are postings all over the Internet about this problem.

    After days of trying I would just like to remove the windows update agent completely, but it seems on Vista you cannot do that either!

    Come on guys, give us a clue

     

    Tuesday, October 2, 2007 8:10 AM
  • I agree completely with the last post. Right now this thread has been viewed nearly 2000 times. If anyone from Microsoft is listening, there must be thousands of frustrated people out there not just hitting this forum, either trashing operating systems to rebuild or creating holes in their security to try to fix the problem. With users like myself and I and sure countless others OS rebuild or AV re-install might not be an option. I don't really care if there are political issues with update 381, I trust Microsoft otherwise I wouldn't be using Vista. Is an uninstall and re-install of Windows Update the answer? I think it is but the problem is that the delivery system of the new version is Windows Update itself. Enough problems Microsoft, please listen to your users and help.

    Tuesday, October 2, 2007 7:40 PM
  • Think I found the problem...for me anyway. I had relocated my user profiles to another drive (for ease of backup etc).

    Apparently certain updates use the user profile area and this causes them to fail.

     

    I originally followed the advice to move user profiles at http://joshmouch.wordpress.com/2007/04/07/change-user-profile-folder-location-in-vista/

    If you have done this, the solution is to delete the old  %systemroot%\users drectory completely, then make a symbolic link with mklink from %systemroot%\users to wherever you have placed user data. Finally go back and restore the registry settings to their original values. It works for me now and update 381 has gone on and stayed on.

     

    During my failed attempts I trolleyed my user account and have lost my browser history and therefore the web address of the guy who solved the problem. I would really like to credit him and have searched for ages to no avail, , he was dutch, if someone finds his page please credit.

     

     

    Wednesday, October 3, 2007 9:47 AM
  • I am really pleased this worked for you and I hope it helps a few others out there. I still believe there is something wrong with the install and/or the delivery method as there are so many people that still can't find a solution for this one. I have done nothing to change user accounts, profiles or permissions from the base install that my machine was supplied. I am running Windows Update as an administrator and have tried creating a new administrator user to ensure a clean profile in case of corruption and this also did not work. Any standard software install should (and does in all other cases) work. I have seen many people on other forums have logged calls with Microsoft to help but no-one is getting a fix from them. Again, I am a user that values, loves and trusts Microsoft (although it might not sound that way sometimes). A clean installation tool for the new version of Windows Update sounds like the best way forward to me. Has anyone found a way of re-installing Windows Update on Vista? Do other users agree that this would be useful for Microsoft to provide this?

    Wednesday, October 3, 2007 9:53 PM
  • I agree completely.  Microsoft's handling of this issue must be called into question.  That being said I have good news for me, and hopefully for others.

    I too have done no manipulation of user accounts or anything out of the ordinary leading into this and then today.....

    GOT IT!  After another day of tinkering and trying to fix it.  It works!  Well for me at least....

    1) from the command line (cmd.exe) type
         net stop wuauserv
    2) from the command line type:
         regsvr32 %windir%\system32\wups2.dll
    3) Download the manual installer from here:
        
    http://download.windowsupdate.com/WindowsUpdate/redist/standalone/7.0.6000.381/WindowsUpdateAgent30-x86.exe
    4) from the command line change to the directory that contains the file you just downloaded and type
         WindowsUpdateAgent30-x86.exe /wuforce
    5) I know I've tried this before, but this time it told me it needed to reboot after installing (which it hadn't done before).  While rebooting it told me it was configuring updates and after rebooting Windows Update completes properly!  FINALLY!

    Hope this helps others.

    Cheers!

    Wednesday, October 3, 2007 11:12 PM
  • I found the same solution yesterday!

    It's works! FINNALLY!

    Thursday, October 4, 2007 4:03 PM
  • I tried your solution. All things work as you describe except that Windows Update doesn't complete properly. The problem is still there. Windows Update keeps saying that it needs to update Windows Update and after closing down and starting again that it can't search for new updates. In the download history it says Update of software from Windows Update 7.0.6000.381 has failed.

    Thursday, October 4, 2007 5:43 PM
  • I have tried re-regestering all the Windows Update DLL's before and tried again just in case but nope, still didn't work. The installer still gives the unrecoverable fault error mentioned earlier. Again there seem to be a number of strange things happening with update 381 and if you either have a few weeks to spare, have lady luck on your smiling down on you, a following wind or just enjoy trashing and re-installing your OS, you might just be able to get Windows Update working again. I am beginning to think that Microsoft will sort this in SP1 for Vista and won't touch it until then. This still leaves all us vulnerable users out there with Windows unable to update in the interim. I suspect a fault caused by the updater that has affected systems in various ways depending on what security was in place. Due to the unconventional method of distribution this has only partially upgraded/re-configured Windows Update. I suspect the existing download available depends somewhat in having various components of Windows Update operational. A full installer for Windows Update prior to SP1 still seems the best solution to me. Has anyone had any positive feedback from Microsoft on this yet? If you are reading this and are connected to Microsoft, take note of the growing community of people suffering from this problem and the number of times these threads are being viewed. Yes there will be occasional postings from people that have found a fix but this is just nibbling away at the edge. It keeps us busy as we all go off and try another suggested fix but we can't all keep doing. We don't want to know what caused it, we just want a nice clean and easy good quality Microsoft Package to fix Windows Update. Help us please Microsoft.

    Friday, October 5, 2007 12:55 AM
  • Burney289, I think you've nailed it. I've tried every solution I run across to fix this and nothing works. Sent in a help request late August and received a lovely email in reply: A Support Professional would contact me within 24 hours to assist and I've heard nothing more. And I read somewhere the SP1 probably won't be out until after the end of the year...long time to go it seems. Well, good luck on your search but I'm about ready to toss the whole thing. IMHO Vista has been the Pitsa.

     

    Saturday, October 6, 2007 2:16 AM
  • Thanks shawnskown!

     

    Have tried to figure this out for some time. Your solution works. I had the error code C015001A but based on the same problem with a loop asking for installation of a new update for windows update ( installer update 7.0.6000.381).

     

    Very dissapointing that MS will release something via the backdoor which has clearly created problems for thousands.

     

    Thanks

     

    Sunday, October 7, 2007 10:14 PM
  • Thank you Shawn, you're a life saver.  It worked wonderfully.  As a side note, the FIRST time i tried it failed, but then I ran cmd.exe as administrator (even though I was logged in as the admin) and it worked that time.  Just a heads up for anyone else who may be trying this and getting .dll error messages (like I did at first).

     

    Thanks again!
    Tuesday, October 30, 2007 1:32 PM
  • Glad that some folks are finding solutions. Mine was to move to Ubuntu since I managed to totally wipe out the Vista operating system while trying to fix this problem. I have the recovery CDs I created when I first bought this thing but haven't figured out how to get Vista restored. Now I'm asking myself why I think I need it anyway. Maybe I'll eventually try to get it up and running but it's had so many problems I don't know that I'll miss it.
    Wednesday, October 31, 2007 1:42 AM
  •  rricci1 wrote:
    Thank you Shawn, you're a life saver.  It worked wonderfully.  As a side note, the FIRST time i tried it failed, but then I ran cmd.exe as administrator (even though I was logged in as the admin) and it worked that time.  Just a heads up for anyone else who may be trying this and getting .dll error messages (like I did at first).

     

    Thanks again!

     

    rricci1 - how did you run cmd.exe as administrator?  I am an administrator user on my pc and it won't even let me complete step 1 in Shawn's solution (net stop wuauserv).

     

    thanks

    Saturday, November 3, 2007 3:55 PM
  • Click the Start -> Windows Button
    In the Start Search text box type cmd (or locate the cmd.exe in any way that you normally would)
    Right Click on the cmd.exe icon and select Run as Administrator.

    That should do it, but if you have additional problems post here and I'll try to help.
    Sunday, November 4, 2007 12:53 PM
  • Hi shawnskeown,

    everything works fine untill I try to run the update, it does not work, with the message: installation failed with errornumber 0x8000ffff

    any help?
    thanks in advance
    Monday, November 5, 2007 2:29 PM
  • Not a very helpful return code, like most of microsofts return codes.  It's an unexpected error.  So not a lot I can suggest except to be as detailed as possible when reporting the problem.  Where exactly did you run into issues?  What do your update logs say?  I did a quick scan for the same return code and didn't find anything obvious, one person said they did a system restore to a previous update and no longer had the problem, but as with most posts they didn't really provide a lot of detail.

    Sorry I couldn't be more help.  If you come up with some additional info I'll see what I can do, but based on what you've posted here there isn't anything else I can suggest.
    Tuesday, November 6, 2007 3:08 AM
  • Thanks Shawn - I managed to get the updates working with your instructions.  It's a damn shame Microsoft has dropped the ball on this - I have a little unix experience, so this wasn't too difficult, but joe public could never work this out through the command prompt.  Thanks to everyone that has contributed.

    Thursday, November 8, 2007 2:35 AM
  • I got the same message as LukasSen. My initial error code is 8024D00F and it occurred while trying to install 7.0.6000.381 a couple months ago and since then i can't check for updates. I also tried to register the following DLLs manually:

     

    regsvr32 wuaueng1.dll **
    regsvr32 wuaueng.dll
    regsvr32 wucltui.dll **
    regsvr32 wups2.dll
    regsvr32 wups.dll
    regsvr32 wuweb.dll **

     

    the ones with stars returned the error:

     

    The module "xxx.dlll" failed to load.
     
    Make sure the binary is stored at the specified path or debug it to check for problemts with the binary or dependent .DLL files.
     
    The specified module could not be found.
    .

     

    I then found that XP and Vista have some differing names for these DLLs so I registered these ones:

     

    regsvr32 wucltui.dll

    regsvr32 wuwebv.dll

     

    which I think correspond to the very similarly named DLLs above. So maybe there is one corresponding to wuaueng1.dll that has a slightly different name? because my update still will not work.

     

    Any help is very much appreciated. I can provide more information if you can think of anything I am leaving out.

     

    Thanks very much in advance.

     

     

    Tony

     

    Saturday, November 10, 2007 12:26 AM
  • In response to my post above, my updates have started partially working. Although it still tells me that it cannot check for updates, it has found and installed about 14, but is having an error with another one.

    The one that is failing to install is called

    Security Update for Microsoft XML Core Services 4.0 Service Pack 2 (KB936181)


    And it gives Error details: Code 643

    And this link I just noticed: http://go.microsoft.com/fwlink/?LinkId=88350

    It has tried to install this twice now and has failed both times. One other difference now is that the little Windows Update icon in my system tray says 'new updates are available' when i hover over it, rather than 'windows can't check for updates'.

    My guess is that the original problem is either partially corrected, or corrected and I have a new problem.

    Any suggestions? I appreciate any help, thanks in advance.


    Tony
    Tuesday, November 13, 2007 5:13 PM
  •  

    I got error 8007002 and i got 800F081F once so i think its related.  Did the posted fix still doesnt work.  This first started when windows update made me download update i already had.  Im going to try a system restore and see if that works.  Thank you MS for making me waste time and be really uncool about helping out.
    Tuesday, November 20, 2007 12:58 AM
  • guess what,  my problems came back after few other updates with vista, so I looked up what the other guy posted about this thing called ubuntu, and its great,

    I got to say, made my system fast, and looks great. 

    thanks for posting because i would have never know about it.
    Friday, November 23, 2007 11:33 PM
  • Quoting shawnskeown:

    "1) from the command line (cmd.exe) type
         net stop wuauserv
    2) from the command line type:
         regsvr32 %windir%\system32\wups2.dll
    3) Download the manual installer from here:
        
    http://download.windowsupdate.com/WindowsUpdate/redist/standalone/7.0.6000.381/WindowsUpdateAgent30-x86.exe
    4) from the command line change to the directory that contains the file you just downloaded and type
         WindowsUpdateAgent30-x86.exe /wuforce
    5) I know I've tried this before, but this time it told me it needed to reboot after installing (which it hadn't done before).  While rebooting it told me it was configuring updates and after rebooting Windows Update completes properly!"

    This worked for me. I also ran cmd.exe as an administrator. I also needed to uninstall Comodo.

    More importantly for me, this fixed the dreaded 8024D00E error on a brand-new PC. I hope this may help others who have searched for the solution in vain
    Friday, December 14, 2007 11:40 AM
  • Hello from Hawaii -

     

    I just bought a new computer for my sister-in-law and am trying to do a simple Windows Update and get that dumb 800F018F error - STRAIGHT out of the box. I realize your post was from 3 months ago - but did you ever resolve the problem? Is there no way to manually patch this box if I can't get Windows Update to work? (I installed Office 2003 - AFTER I tried to update with WU) - and there's no way I want this box sitting out on the internet without being patched...

     

    Please advise if you're still checking this forum - I need help! This is supposed to be a Christmas present....

     

    Mahalo!

     

    Saturday, December 22, 2007 5:12 PM
  •  

    Sorry all -

     

    As the newbie, I neglected to read ALL the threads (like page 2 and page 3 - kinda ditzy - so sorry!). Shawnskeown solution SEEMS to have worked for me - THANK YOU SO much! Of course, I won't get my hopes up until the 17 updates I need has successfully downloaded and installed. However, I wasn't even getting to the fact that I HAD updates that needed to be installed so this is a HUGE step forward. Thank you all for being diligent and posting your work arounds - Obviously Microsoft isn't listening hard enough...

     

    Mahalo!

    Saturday, December 22, 2007 5:38 PM
  • received error message while in step 4 that files were corrupt any suggestions

     

     

    Wednesday, January 2, 2008 3:47 AM
  • I have the solution to this problem, you can find it at http://forums.dlsoftware.net/topic494.html
    Friday, January 4, 2008 8:32 PM
  •  

    hi ,,,

    I have problem in my windows update all time coming this code

     

    Error(s) found:

         Code 8024d00e

    plz halp me in this error, how I fix it?

     

    thanks

    Tuesday, February 12, 2008 9:37 AM
  • Where exactly did you run into issues?  What do your update logs say?  What fixes have you tried already?  Have you attempted to stop the service and download and install manually?

    I did a quick search and found this post about your specific error: http://www.vistaheads.com/forums/microsoft-public-windowsupdate/181778-error-code-8024d00e.html

    Good luck, but please for future posts try to provide as much detail as you possibly can about everything you have done.

    Tuesday, February 12, 2008 12:36 PM
  •  shawnskeown wrote:
    I agree completely.  Microsoft's handling of this issue must be called into question.  That being said I have good news for me, and hopefully for others.

    I too have done no manipulation of user accounts or anything out of the ordinary leading into this and then today.....

    GOT IT!  After another day of tinkering and trying to fix it.  It works!  Well for me at least....

    1) from the command line (cmd.exe) type
         net stop wuauserv
    2) from the command line type:
         regsvr32 %windir%\system32\wups2.dll
    3) Download the manual installer from here:
        
    http://download.windowsupdate.com/WindowsUpdate/redist/standalone/7.0.6000.381/WindowsUpdateAgent30-x86.exe
    4) from the command line change to the directory that contains the file you just downloaded and type
         WindowsUpdateAgent30-x86.exe /wuforce
    5) I know I've tried this before, but this time it told me it needed to reboot after installing (which it hadn't done before).  While rebooting it told me it was configuring updates and after rebooting Windows Update completes properly!  FINALLY!

    Hope this helps others.

    Cheers!



    I tried this method;  I even tried running it in Safe Mode.  Each time it reaches "Copying Files" and after the bar gets 1/3 of the way through it stops saying installation failed.  It says failed with error code:  0xc150004
    Tuesday, March 11, 2008 4:29 PM
  • i've tried shawnskeown's method thrice now, and every time it finishes, but never asks me to restart my laptop, has nyone actually got a proper solution, and also, if i want to rerun wuauserv, do i just type net run wuauserv
    Tuesday, March 18, 2008 12:10 AM
  •  

    I just tried doing this, and thought that it had worked; however now windows update doesn't work at all! I cannot change any settings, and dialogue boxes that pop up have no text on them, just blank buttons. Help!
    Thursday, March 20, 2008 11:45 AM
  • Can anyone help me?

    I also get the 0x800F081F error with 7.0.6000.381 but following the steps above when I attempt to install Windows Update Agent it tells me I'm not logged in as an administrator (even though I am) or that my version of Windows doesn't support this product.

    How do I fix this problem, it's a brand new PC. : (
    Monday, March 31, 2008 11:45 PM
  •  

    I tried running the Update Agent patch, and it came back with the error: "You cannot install Windows Update Agent because you are not logged on as as Administrator..".  I of course was logged on as an Admin. and even right clicked the .exe and selected "Run as Administrator" AFTER I turned off UAC!!!! - One day I'll wise up and start running Slackware or Debian.
    Saturday, July 26, 2008 12:22 AM
  • Hi this error is to do with AV blocking the updates try disabling your AV then run an update and see if you get the error. I was using Kaspersky and part of the software was blocking the update, changed a few settings and it works fine now.
    Sunday, May 24, 2009 9:12 AM