Header Script

Solution for Windows Update Error 0x800705b4 (2018-06 Cumulative Update)

You may also like...

12 Responses

  1. Omar Abi Nader says:

    It works!! I only tried the method of “sconfig” and it successfully installed (and it downloaded the update from WSUS)

    I am using WSUS and all cumulative updates never installed automatically it keeps failing with this error (0x800705b4) even for 2016 – 07 Cumulative update..

    But how to fix this error with an environment of more than 100 servers? It is disturbing to do it manually on each server!

  2. Zubair Alexander says:

    Omar, before I install the Cumulative Update 2018-07, I have been disabling the option listed under Advanced Settings on the Windows Update page called “Give me updates for other Microsoft products when I update Windows.” After the update is successfully installed, I re-enable this option. So far on every server Cumulative Update 2018-07 has installed without any issues. It’s either because I have been temporarily turning off the update option for other Microsoft products, or perhaps Microsoft has fixed the issues that have been problematic with previous cumulative updates.

  3. Mike Konopka says:

    Thanks for posting this article. Your advice is greatly appreciated! I had the same situation and results as Omar Abi Nader above, but the issue is only present on 3 servers (for now).

  4. Zubair Alexander says:

    Mike, I haven’t found any consistency in the behavior. Some servers get stuck on the Cumulative Updates, while others have no issues at all. In the past month or so, SConfig has worked for me every single time on every single computer. SConfig also works for Omar. Have you guys tried to run the SConfig remotely on the servers that are having issues? You can also write a script and use a Group Policy to run SConfig on a large number of servers.

  5. Roy says:

    Again, thanks for the update Zubair for the time and effort put in here.
    I am just in the process of waiting for sconfig to download all updates.
    Bit of a pain this as one 2016r2 server updated from scratch same iso no problem.
    This latest one is proving to be a very slow laborious task. I downloaded the KB4103720 cu. Got bored with it sat there doing nothing after 2 hours. Rebooted and I am not using sconfig option 6, and waiting to see what we get this way. Bring back 2003 r2 server 🙂

  6. Pravin Dave says:

    Alexander, your solution worked for me!
    None of the other solutions on the net worked.
    Thank you so much!!!

  7. Zubair Alexander says:

    Pravin, thank you for your feedback. Glad to hear my solution worked for you.

  8. Mark says:

    Zubair, I’ve been fighting this on our Server 2016 instances since April ’19. SConfig and excluding %windir%\systemdistribution has resolved it. Thank you.

  9. Zubair Alexander says:

    Thanks, Mark. Appreciate your feedback and glad the solution worked for you.

  10. Barney Gumble says:

    Newly upgraded to Server 2016 from 2012R2 and saw this error when trying to install updates. Ran SConfig, chose option 6. A window appeared to open and close too quickly to see what it was. In short, this solution did not work for me.

  11. John says:

    Finally a solution that works. Thanks for your help!

Leave a Reply

Your email address will not be published. Required fields are marked *