Unable to complete update

Discussion in 'Security Signatures' started by Guest, Mar 2, 2006.

  1. Guest

    Guest Guest

    I am trying to update signatures of WD beta 2. I receive following message
    "Windows defender was unable to compete the update. 0x8024002b"

    Can some one explain what is going on.
     
    Guest, Mar 2, 2006
    #1
    1. Advertisements

  2. Guest

    Guest Guest

    I have same problem with slightly different error number.
    0x8024400b

    Rich Hull

    "Gary" wrote:

    > I am trying to update signatures of WD beta 2. I receive following message
    > "Windows defender was unable to compete the update. 0x8024002b"
    >
    > Can some one explain what is going on.
     
    Guest, Mar 3, 2006
    #2
    1. Advertisements

  3. Guest

    Guest Guest

    Hello Gary

    No one can help if you don't provide at least a modicum of informatiºn.
    What version of Windows are you using? SP?? Anti=-virus. Are you on a large,
    managed network, where access to AutoUpdate is restricted? Is there a WSUS
    server on the network?

    WD personal are patroling the NG. With more info, they can have a solution
    sooner.
    Rember this is a Beta with-out support.

    Eиgel
    --


    "Gary" wrote:

    > I am trying to update signatures of WD beta 2. I receive following message
    > "Windows defender was unable to compete the update. 0x8024002b"
    >
    > Can some one explain what is going on.
     
    Guest, Mar 4, 2006
    #3
  4. Guest

    Guest Guest

    Valid point. Operating system is XP sp2. Anti virus is VirusScan Enteprise
    edition 8.0. I am on a network, but there is no restrictio to autoupdate
    access.


    "Engel" wrote:

    > Hello Gary
    >
    > No one can help if you don't provide at least a modicum of informatiºn.
    > What version of Windows are you using? SP?? Anti=-virus. Are you on a large,
    > managed network, where access to AutoUpdate is restricted? Is there a WSUS
    > server on the network?
    >
    > WD personal are patroling the NG. With more info, they can have a solution
    > sooner.
    > Rember this is a Beta with-out support.
    >
    > Eиgel
    > --
    >
    >
    > "Gary" wrote:
    >
    > > I am trying to update signatures of WD beta 2. I receive following message
    > > "Windows defender was unable to compete the update. 0x8024002b"
    > >
    > > Can some one explain what is going on.
     
    Guest, Mar 4, 2006
    #4
  5. Can you try an update, via Help, About, check for updates, and post back the
    corresponding (by time) section of \windows\windowsupdate.log?

    Here's an example from my own system--where no update is available:

    ---
    2006-03-06 23:51:29 1936 fd4 COMAPI -------------
    2006-03-06 23:51:29 1936 fd4 COMAPI -- START -- COMAPI: Search [ClientId =
    Windows Defender]
    2006-03-06 23:51:29 1936 fd4 COMAPI ---------
    2006-03-06 23:51:29 1936 fd4 COMAPI - Online = Yes; Ignore download
    priority = No
    2006-03-06 23:51:29 1936 fd4 COMAPI - Criteria = "(IsInstalled = 0 and
    IsHidden = 0 and CategoryIDs contains
    '0a487050-8b0f-4f81-b401-be4ceacd61cd') or (IsInstalled = 0 and IsHidden = 0
    and CategoryIDs contains '8c3fcc84-7410-4a95-8b89-a166a0190486')"
    2006-03-06 23:51:29 1936 fd4 COMAPI - ServiceID =
    {00000000-0000-0000-0000-000000000000}
    2006-03-06 23:51:31 1936 fd4 COMAPI <<-- SUBMITTED -- COMAPI: Search
    [ClientId = Windows Defender]
    2006-03-06 23:51:31 920 808 Agent *************
    2006-03-06 23:51:31 920 808 Agent ** START ** Agent: Finding updates
    [CallerId = Windows Defender]
    2006-03-06 23:51:31 920 808 Agent *********
    2006-03-06 23:51:50 920 808 PT +++++++++++ PT: Synchronizing server
    updates +++++++++++
    2006-03-06 23:51:50 920 808 PT + ServiceId =
    {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL =
    https://update.microsoft.com/v6/ClientWebService/client.asmx
    2006-03-06 23:52:19 920 808 PT +++++++++++ PT: Synchronizing extended
    update info +++++++++++
    2006-03-06 23:52:19 920 808 PT + ServiceId =
    {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL =
    https://update.microsoft.com/v6/ClientWebService/client.asmx
    2006-03-06 23:52:23 920 808 Agent * Found 0 updates and 16 categories in
    search
    2006-03-06 23:52:23 920 808 Agent *********
    2006-03-06 23:52:23 920 808 Agent ** END ** Agent: Finding updates
    [CallerId = Windows Defender]
    2006-03-06 23:52:23 920 808 Agent *************
    2006-03-06 23:52:23 1936 57c COMAPI >>-- RESUMED -- COMAPI: Search
    [ClientId = Windows Defender]
    2006-03-06 23:52:23 1936 57c COMAPI - Updates found = 0
    2006-03-06 23:52:23 1936 57c COMAPI ---------
    2006-03-06 23:52:23 1936 57c COMAPI -- END -- COMAPI: Search [ClientId =
    Windows Defender]
    2006-03-06 23:52:23 1936 57c COMAPI -------------
    2006-03-06 23:52:28 920 40c Report REPORT EVENT:
    {478E0FE5-1477-47A6-B56A-2489A5E3FECB} 2006-03-06 23:52:23-0500 1 147 101
    {00000000-0000-0000-0000-000000000000} 0 0 Windows Defender Success Software
    Synchronization Agent has finished detecting items.

    --
     
    Bill Sanderson, Mar 7, 2006
    #5
  6. Guest

    Guest Guest

    "Bill Sanderson" wrote:

    > Can you try an update, via Help, About, check for updates, and post back the
    > corresponding (by time) section of \windows\windowsupdate.log?
    >
    > Here's an example from my own system--where no update is available:
    >


    I am getting the same error as Gary. My system is XP SP2 with McAfee
    VirusScan Enterprise 8. I am on a large corporate network and regularly use
    Windows Update with no problems. Here is the appropriate section from
    windowsupdate.log

    2006-03-08 14:47:10 1448 96c COMAPI -------------
    2006-03-08 14:47:10 1448 96c COMAPI -- START -- COMAPI: Search [ClientId =
    Windows Defender]
    2006-03-08 14:47:10 1448 96c COMAPI ---------
    2006-03-08 14:47:10 1448 96c COMAPI - Online = Yes; Ignore download
    priority = No
    2006-03-08 14:47:10 1448 96c COMAPI - Criteria = "(IsInstalled = 0 and
    IsHidden = 0 and CategoryIDs contains '0a487050-8b0f-4f81-b401-be4ceacd61cd')
    or (IsInstalled = 0 and IsHidden = 0 and CategoryIDs contains
    '8c3fcc84-7410-4a95-8b89-a166a0190486')"
    2006-03-08 14:47:10 1448 96c COMAPI - ServiceID =
    {00000000-0000-0000-0000-000000000000}
    2006-03-08 14:47:10 1448 96c COMAPI <<-- SUBMITTED -- COMAPI: Search
    [ClientId = Windows Defender]
    2006-03-08 14:47:10 1124 adc Agent *************
    2006-03-08 14:47:10 1124 adc Agent ** START ** Agent: Finding updates
    [CallerId = Windows Defender]
    2006-03-08 14:47:10 1124 adc Agent *********
    2006-03-08 14:47:10 1124 adc PT +++++++++++ PT: Synchronizing server
    updates +++++++++++
    2006-03-08 14:47:10 1124 adc PT + ServiceId =
    {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://stlwolpat01/ClientWebService/client.asmx
    2006-03-08 14:47:11 1124 adc Misc WARNING: WinHttp:
    SendRequestToServerForFileInformation failed with 0x80190194
    2006-03-08 14:47:11 1124 adc Misc WARNING: WinHttp: ShouldFileBeDownloaded
    failed with 0x80190194
    2006-03-08 14:47:11 1124 adc PT SUS 1.0 server is detected
    2006-03-08 14:47:11 1124 adc PT WARNING: Sync of Updates: 0x8024002b
    2006-03-08 14:47:11 1124 adc Agent * WARNING: Failed to synchronize, error
    = 0x8024002B
    2006-03-08 14:47:11 1124 adc Agent * WARNING: Exit code = 0x8024002B
    2006-03-08 14:47:11 1124 adc Agent *********
    2006-03-08 14:47:11 1124 adc Agent ** END ** Agent: Finding updates
    [CallerId = Windows Defender]
    2006-03-08 14:47:11 1124 adc Agent *************
    2006-03-08 14:47:11 1124 adc Agent WARNING: WU client failed Searching for
    update with error 0x8024002b
    2006-03-08 14:47:11 1448 6c8 COMAPI >>-- RESUMED -- COMAPI: Search
    [ClientId = Windows Defender]
    2006-03-08 14:47:11 1448 6c8 COMAPI - Updates found = 0
    2006-03-08 14:47:11 1448 6c8 COMAPI - WARNING: Exit code = 0x00000000,
    Result code = 0x8024002B
    2006-03-08 14:47:11 1448 6c8 COMAPI ---------
    2006-03-08 14:47:11 1448 6c8 COMAPI -- END -- COMAPI: Search [ClientId =
    Windows Defender]
    2006-03-08 14:47:11 1448 6c8 COMAPI -------------
    2006-03-08 14:47:11 1448 910 COMAPI WARNING: Operation failed due to earlier
    error, hr=8024002B
    2006-03-08 14:47:11 1448 910 COMAPI FATAL: Unable to complete asynchronous
    search. (hr=8024002B)
     
    Guest, Mar 8, 2006
    #6
  7. Guest

    Guest Guest

    "Chris Stratton" wrote:

    > "Bill Sanderson" wrote:
    >
    > > Can you try an update, via Help, About, check for updates, and post back the
    > > corresponding (by time) section of \windows\windowsupdate.log?
    > >
    > > Here's an example from my own system--where no update is available:
    > >

    >
    > I am getting the same error as Gary. My system is XP SP2 with McAfee
    > VirusScan Enterprise 8. I am on a large corporate network and regularly use
    > Windows Update with no problems. Here is the appropriate section from
    > windowsupdate.log
    >
    >
    > {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    > http://stlwolpat01/ClientWebService/client.asmx


    I noticed the server path in my log points to one of our local servers. I
    searched the registry for that server name and found it in
    HKLM\Software\Policies\Microsoft\Windows\Windows Update

    I changed it to https://update.microsoft.com as in Bill's logfile but it
    still doesn't work
     
    Guest, Mar 8, 2006
    #7
  8. Windows Defender is designed to get signature updates via WSUS on a
    corporate network. If your company is running WSUS, the WSUS administrators
    will need to enable the new class of signature updates for Windows Defender.

    If you can reach Microsofts Windows Update servers--via Start, Windows
    Update--Defender Signature updates should be offered that way, but that will
    be a manual process.

    --

    "Chris Stratton" <Chris > wrote in message
    news:...
    > "Bill Sanderson" wrote:
    >
    >> Can you try an update, via Help, About, check for updates, and post back
    >> the
    >> corresponding (by time) section of \windows\windowsupdate.log?
    >>
    >> Here's an example from my own system--where no update is available:
    >>

    >
    > I am getting the same error as Gary. My system is XP SP2 with McAfee
    > VirusScan Enterprise 8. I am on a large corporate network and regularly
    > use
    > Windows Update with no problems. Here is the appropriate section from
    > windowsupdate.log
    >
    > 2006-03-08 14:47:10 1448 96c COMAPI -------------
    > 2006-03-08 14:47:10 1448 96c COMAPI -- START -- COMAPI: Search [ClientId
    > =
    > Windows Defender]
    > 2006-03-08 14:47:10 1448 96c COMAPI ---------
    > 2006-03-08 14:47:10 1448 96c COMAPI - Online = Yes; Ignore download
    > priority = No
    > 2006-03-08 14:47:10 1448 96c COMAPI - Criteria = "(IsInstalled = 0 and
    > IsHidden = 0 and CategoryIDs contains
    > '0a487050-8b0f-4f81-b401-be4ceacd61cd')
    > or (IsInstalled = 0 and IsHidden = 0 and CategoryIDs contains
    > '8c3fcc84-7410-4a95-8b89-a166a0190486')"
    > 2006-03-08 14:47:10 1448 96c COMAPI - ServiceID =
    > {00000000-0000-0000-0000-000000000000}
    > 2006-03-08 14:47:10 1448 96c COMAPI <<-- SUBMITTED -- COMAPI: Search
    > [ClientId = Windows Defender]
    > 2006-03-08 14:47:10 1124 adc Agent *************
    > 2006-03-08 14:47:10 1124 adc Agent ** START ** Agent: Finding updates
    > [CallerId = Windows Defender]
    > 2006-03-08 14:47:10 1124 adc Agent *********
    > 2006-03-08 14:47:10 1124 adc PT +++++++++++ PT: Synchronizing server
    > updates +++++++++++
    > 2006-03-08 14:47:10 1124 adc PT + ServiceId =
    > {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    > http://stlwolpat01/ClientWebService/client.asmx
    > 2006-03-08 14:47:11 1124 adc Misc WARNING: WinHttp:
    > SendRequestToServerForFileInformation failed with 0x80190194
    > 2006-03-08 14:47:11 1124 adc Misc WARNING: WinHttp: ShouldFileBeDownloaded
    > failed with 0x80190194
    > 2006-03-08 14:47:11 1124 adc PT SUS 1.0 server is detected
    > 2006-03-08 14:47:11 1124 adc PT WARNING: Sync of Updates: 0x8024002b
    > 2006-03-08 14:47:11 1124 adc Agent * WARNING: Failed to synchronize,
    > error
    > = 0x8024002B
    > 2006-03-08 14:47:11 1124 adc Agent * WARNING: Exit code = 0x8024002B
    > 2006-03-08 14:47:11 1124 adc Agent *********
    > 2006-03-08 14:47:11 1124 adc Agent ** END ** Agent: Finding updates
    > [CallerId = Windows Defender]
    > 2006-03-08 14:47:11 1124 adc Agent *************
    > 2006-03-08 14:47:11 1124 adc Agent WARNING: WU client failed Searching for
    > update with error 0x8024002b
    > 2006-03-08 14:47:11 1448 6c8 COMAPI >>-- RESUMED -- COMAPI: Search
    > [ClientId = Windows Defender]
    > 2006-03-08 14:47:11 1448 6c8 COMAPI - Updates found = 0
    > 2006-03-08 14:47:11 1448 6c8 COMAPI - WARNING: Exit code = 0x00000000,
    > Result code = 0x8024002B
    > 2006-03-08 14:47:11 1448 6c8 COMAPI ---------
    > 2006-03-08 14:47:11 1448 6c8 COMAPI -- END -- COMAPI: Search [ClientId
    > =
    > Windows Defender]
    > 2006-03-08 14:47:11 1448 6c8 COMAPI -------------
    > 2006-03-08 14:47:11 1448 910 COMAPI WARNING: Operation failed due to
    > earlier
    > error, hr=8024002B
    > 2006-03-08 14:47:11 1448 910 COMAPI FATAL: Unable to complete asynchronous
    > search. (hr=8024002B)
    >
     
    Bill Sanderson, Mar 8, 2006
    #8
    1. Advertisements

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

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Guest
    Replies:
    1
    Views:
    623
    Bill Sanderson
    Feb 15, 2006
  2. Guest
    Replies:
    1
    Views:
    667
    Bill Sanderson
    Feb 15, 2006
  3. Guest
    Replies:
    1
    Views:
    657
    Guest
    Feb 15, 2006
  4. Guest
    Replies:
    10
    Views:
    6,180
    Bill Sanderson
    Mar 13, 2006
  5. Guest
    Replies:
    5
    Views:
    2,945
    Guest
    Mar 9, 2006
Loading...

Share This Page