none
Windows 10: Windows Update error 0x8024401c and 0x800705b4 RRS feed

  • Question

  • Hi All,
    I'm having problems with Windows Update on many Windows 10 clients (build 1511 and 1607).
    All clients are connected on an internal WSUS server on Windows Server 2012 R2.

    Many clients works fine and regularly gets updates from WSUS, but on an half of them, I get this error if I check for updates:
    "There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x8024401c)"
    or
    "There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x800705b4)"

    I have followed all suggested steps available at this URL:
    https://support.microsoft.com/en-us/help/10164/fix-windows-update-errors

    1) I have executed the "Windows Update troubleshooter"
    2) I have manually installed the most recent update KB
    3) I have executed "DISM.exe /Online /Cleanup-image /Restorehealth" and "sfc /scannow"
    4) I have manually upgraded the build from 1511 to 1607

    Nothing changed.

    So, I have tried changing my GPO to point to Microsoft servers instead of my WSUS, and if I do this, the Windows Update client getting errors, starts to work.

    On some clients, If I run the PowerShell command "Get-WindowsUpdateLog", I can see this log:

    2017/05/16 13:53:23.6876262 928   376   WebServices     Current service auth scheme=0.
    2017/05/16 13:53:23.6876277 928   376   WebServices     Current Proxy auth scheme=0.
    2017/05/16 13:53:25.7027586 928   376   WebServices     Auto proxy settings for this web service call.
    2017/05/16 13:54:27.6879485 928   376   WebServices     WS error: There was an error communicating with the endpoint at 'https://servername.domain.ext:443/ClientWebService/client.asmx'.
    2017/05/16 13:54:27.6879507 928   376   WebServices     WS error: There was an error receiving the HTTP reply.
    2017/05/16 13:54:27.6879522 928   376   WebServices     WS error: The operation did not complete within the time allotted.
    2017/05/16 13:54:27.6879544 928   376   WebServices     WS error: There was an error communicating with the endpoint at 'https://servername.domain.ext:443/ClientWebService/client.asmx'.
    2017/05/16 13:54:27.6879562 928   376   WebServices     WS error: There was an error receiving the HTTP reply.
    2017/05/16 13:54:27.6879577 928   376   WebServices     WS error: The operation did not complete within the time allotted.
    2017/05/16 13:54:27.6879599 928   376   WebServices     WS error: There was an error communicating with the endpoint at 'https://servername.domain.ext:443/ClientWebService/client.asmx'.
    2017/05/16 13:54:27.6879613 928   376   WebServices     WS error: There was an error receiving the HTTP reply.
    2017/05/16 13:54:27.6879632 928   376   WebServices     WS error: The operation did not complete within the time allotted.
    2017/05/16 13:54:27.6879646 928   376   WebServices     WS error: The operation timed out
    2017/05/16 13:54:27.6879672 928   376   WebServices     Web service call failed with hr = 8024401c.
    2017/05/16 13:54:27.6879687 928   376   WebServices     Current service auth scheme=0.
    2017/05/16 13:54:27.6879698 928   376   WebServices     Current Proxy auth scheme=0.
    2017/05/16 13:54:27.6879786 928   376   ProtocolTalker  PTError: 0x8024401c
    2017/05/16 13:54:27.6879797 928   376   ProtocolTalker  SyncUpdates_WithRecovery failed. 0x8024401c
    2017/05/16 13:54:27.6880057 928   376   ProtocolTalker  SyncUpdates round trips: 3
    2017/05/16 13:54:27.6880174 928   376   ProtocolTalker  Sync of Updates 0x8024401c
    2017/05/16 13:54:27.6880636 928   376   ProtocolTalker  SyncServerUpdatesInternal failed 0x8024401c
    1601/01/01 01:00:00.0000000 928   376                   Unknown( 230): GUID=8ce98bfa-21f0-385f-839a-1073774029ac (No Format Information found).
    1601/01/01 01:00:00.0000000 928   376                   Unknown( 240): GUID=8ce98bfa-21f0-385f-839a-1073774029ac (No Format Information found).
    1601/01/01 01:00:00.0000000 928   376                   Unknown( 241): GUID=8ce98bfa-21f0-385f-839a-1073774029ac (No Format Information found).
    2017/05/16 13:54:27.7654360 928   3608  ComApi          *RESUMED* Search ClientId = UpdateOrchestrator
    2017/05/16 13:54:27.7660270 928   3608  ComApi          Updates found = 0
    2017/05/16 13:54:27.7660284 928   3608  ComApi          Exit code = 0x00000000, Result code = 0x8024401C
    2017/05/16 13:54:27.7660299 928   3608  ComApi          * END *   Search ClientId = UpdateOrchestrator
    2017/05/16 13:54:27.7666645 928   4120  ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C

    I have also tried to stop the AntiVirus, but nothing changed.

    Do you have any suggestion?

    Thanks!
    Tuesday, May 16, 2017 3:59 PM

Answers

  • I found a way to fix this error.
    I have upgraded the affected machines to Windows 10 build 1703, then I ran the "Windows Update troubleshooting tool" and all was fixed.
    • Marked as answer by thenewmessiah Tuesday, May 30, 2017 3:49 PM
    Tuesday, May 30, 2017 3:49 PM

All replies

  • Same here. At first I thought it was a local problem. In my stupidity I put back an image from a couple,of days ago on my work system. Didn't bring any solution. In fact it got worse, because it desperately tried to get updates for,as well Windows 10 as well as apps. Which failed with a boatload of errors as a result. MS is obviously not capable in generating normal errors like 'sorry the update server is down, try again later'. If I would have seen such a message I would not be in the shit I am now. :-(
    Tuesday, May 16, 2017 6:29 PM
  • To me this seems like a problem reaching your WSUS server (or the proxy?)
    Is this really the name of your WSUS server? "https://servername.domain.ext"

    Tuesday, May 16, 2017 8:51 PM
  • To me this seems like a problem reaching your WSUS server (or the proxy?)
    Is this really the name of your WSUS server? "https://servername.domain.ext"

    "servername.domain.ext" is a placeholder, not the real address

    Also, there is no proxy configured and no firewall between the client and the server.
    I can open the address "https://servername.domain.ext:443/ClientWebService/client.asmx" from the affected machines.

    Wednesday, May 17, 2017 7:48 AM
  • Hi,

    As I know, Windows server 2012 R2 using port 8531 by default, but I noticed you are using port 443.

    Have you changed the port manually?

    “So, I have tried changing my GPO to point to Microsoft servers instead of my WSUS, and if I do this, the Windows Update client getting errors, starts to work.”

    Do you mean updating from Microsoft server will work well?

    Please enter the alternative server address follow the article below:

    It is recommend to ask for help from WUSU support as they have more resources to help you.

    WSUS:

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverwsus

    Best regards,

    Joy.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Friday, May 19, 2017 1:19 AM
    Moderator

  • Have you changed the port manually?

    “So, I have tried changing my GPO to point to Microsoft servers instead of my WSUS, and if I do this, the Windows Update client getting errors, starts to work.”

    Do you mean updating from Microsoft server will work well?

    Yes, I have changed the port to 443.

    Updating from Microsoft server work well.

    Monday, May 22, 2017 12:39 PM
  • I found a way to fix this error.
    I have upgraded the affected machines to Windows 10 build 1703, then I ran the "Windows Update troubleshooting tool" and all was fixed.
    • Marked as answer by thenewmessiah Tuesday, May 30, 2017 3:49 PM
    Tuesday, May 30, 2017 3:49 PM
  • Hi there. :)

    I know this is an old thread now but I had the same problem too. Sometimes Windows update worked and others not.

    One day I realised that the updates were always failing when I was using my wired connection. I switched to wireless and Windows update worked. I kept on changing from wifi to wired and testing the updates to check if it was always like that and it was. It only seems to work properly when I used my WiFi. I have no idea why it only works with a WiFi connection. It's weird. :) (Typical Windows).

    Maybe it may be the same for you..

    Hope this helps. 

    Best regards. :)

    Friday, July 28, 2017 11:54 PM
  • Mine's the opposite. WiFi doesn't work.

    A different problem suggested a network reset to fix discovery. I wonder if this is somehow related as the network components used are the same.

    ....The update troubleshooter found a few errors the install has started again.

    Why doesn't Microsoft bake this into the updater? Especially for us insiders running preview builds.


    • Proposed as answer by George_F Wednesday, August 30, 2017 5:06 AM
    Saturday, August 19, 2017 3:08 PM
  • I was running into the same problem - have switched from wireless to wired and the problem was instantly solved. Now I have the latest updates downloaded and installed.

    
    Monday, August 28, 2017 4:02 AM
  • It's working for me :D thank you!
    Wednesday, February 14, 2018 3:29 PM
  • Engineer thenewmessiah , 

    Your posts two links  :

    9:47 AM 7/19/2019

    https://servername.domain.ext:443/ClientWebService/client.asmx"

    https://servername.domain.ext"

    unfound today ? What they are having inside for about ? 

    Sincerely 

    Friday, July 19, 2019 1:52 AM