locked
KB4041691 Update Fails with Error 0x800705b4 RRS feed

  • Question

  • When attempting to install Windows Server Datacenter 2016 Cumulative Update KB4041691, I am encountering error 0x800705b4. I haven't found any relevant solutions. Suggestions?
    Monday, October 30, 2017 12:57 PM

Answers

  • I'd try the windows update trouble shooter. Also try running;

    sfc /scannow

    dism /online /cleanup-image /restorehealth

    try manual download of the latest cumulative update.

    https://www.catalog.update.microsoft.com/Search.aspx?q=KB4041688

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    • Marked as answer by AlaskanRogue Monday, October 30, 2017 6:22 PM
    Monday, October 30, 2017 1:21 PM
  • Looking here you can see that KB4041688 is a higher build version. The sequence of the KB numbers irrelevant.

    https://support.microsoft.com/en-us/help/4000825/windows-10-windows-server-2016-update-history

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    • Marked as answer by AlaskanRogue Tuesday, October 31, 2017 5:27 PM
    Tuesday, October 31, 2017 12:51 PM

All replies

  • I'd try the windows update trouble shooter. Also try running;

    sfc /scannow

    dism /online /cleanup-image /restorehealth

    try manual download of the latest cumulative update.

    https://www.catalog.update.microsoft.com/Search.aspx?q=KB4041688

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    • Marked as answer by AlaskanRogue Monday, October 30, 2017 6:22 PM
    Monday, October 30, 2017 1:21 PM
  • The manual install of the alternative update appears to have worked on the first VM server I applied it to.

    Interesting, but when I was at the update site I notice that the KB4041688 update was listed as an replacement for the KB4041691 update which doesn't make much sense for an update sequencing order. Why?

    Also, I noticed that it says it is for AMD hardware, not Intel. Why?

    Monday, October 30, 2017 6:21 PM
  • Good to hear it helps.
    KB4041688 update was listed as an replacement for the KB4041691 update which doesn't make much sense for an update sequencing order. Why?

    Windows updates are now cumulative so KB4041688 contains new fixes / updates plus everything within KB4041691 Here you can see the update KBs and resulting build numbers.

    https://support.microsoft.com/en-us/help/4000825/windows-10-windows-server-2016-update-history

    Also, I noticed that it says it is for AMD hardware, not Intel. Why?

    I think microsoft refers to all x64 as "amd64 architecture".

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Monday, October 30, 2017 6:44 PM
  • I can see KB4041688 being in KB4041691 but not the other was around; the reason for my question.
    Tuesday, October 31, 2017 11:07 AM
  • Looking here you can see that KB4041688 is a higher build version. The sequence of the KB numbers irrelevant.

    https://support.microsoft.com/en-us/help/4000825/windows-10-windows-server-2016-update-history

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    • Marked as answer by AlaskanRogue Tuesday, October 31, 2017 5:27 PM
    Tuesday, October 31, 2017 12:51 PM
  • Thanks for the link. It does present the build numbers which explain the sequencing.
    Tuesday, October 31, 2017 5:27 PM