none
Repeated update failure for KB4338818 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based RRS feed

  • Question

  • Apologies in advance if this is not the correct Forum (with all due respect, MS Forum Category is ridiculously unhelpful and limited in scope).

    I have been unable to apply the update KB4338818 (2018-07 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based) repeatedly.  I found a thread reporting the same/similar issue under the Windows 7 IT Pro forum that dates back to November 2017.  It seems this issue has fallen off the radar for Microsoft, since no Support rep has chimed in. FWIW - here is the link to the original forum post:
    https://social.technet.microsoft.com/Forums/windows/en-US/221a12a3-6cbb-4205-bcf3-150efa0ba437/repeatedly-failed-to-install-security-monthly-quality-rollup-for-windows-7-for-x64based-systems

    Under my Server2008r2 system, attempts to install this update result in a failure, and displays the following error:
    "Code 8000FFF Windows Update encountered an unknown error."

    The following details are from the Update History:
    Systems (KB4338818)
    Installation date: ‎8/‎8/‎2018 5:23 PM
    Installation status: Failed
    Error details: Code 8000FFFF
    Update type: Important

    Apparently, this issue has been encountered by many users.  Is there some way to attract the attention of a Microsoft Support agent to provide some guidance?

    Any assistance would be much appreciated!
    Thursday, August 9, 2018 6:26 PM

All replies

  • i have the same issue, hope it will solved right now.
    Tuesday, August 14, 2018 7:50 AM
  • I too have had the same issue now for nearly a year! It's becoming a great source of frustration.
    Thursday, August 16, 2018 5:34 PM
  • Hi,

    Have you tried to check the event log and Windows Update.log?

    They may provide some information about the process how to install the update.

    Regards,


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

    Friday, August 31, 2018 6:33 AM
    Moderator
  • I'm getting this as well. Will try again after server reboot.

    Here is what the WindowsUpdate.log shows...

    2018-10-01    10:39:02:094     468    b60    AU    Install complete for all calls, reboot NOT needed
    2018-10-01    10:39:02:972     468    f1c    AU    UpdateDownloadProperties: 0 download(s) are still in progress.
    2018-10-01    10:39:02:972     468    f1c    AU    Can not perform non-interactive scan if AU is interactive-only
    2018-10-01    10:39:02:973     468    f1c    AU    AU setting pending client directive to 'Install Complete Ux'
    2018-10-01    10:39:02:973     468    f1c    AU    Changing existing AU client directive from 'Progress Ux' to 'Install Complete Ux', session id = 0x6
    2018-10-01    10:39:02:973     468    f1c    AU    Successfully wrote event for AU health state:0
    2018-10-01    10:39:02:976     468    f1c    AU    Successfully wrote event for AU health state:0
    2018-10-01    10:39:02:979     468    d60    AU    AU received handle event
    2018-10-01    10:39:06:912     468    42c    Report    REPORT EVENT: {37094BB9-DAA4-466D-A6A1-7FBA372822F6}    2018-10-01 10:39:01:913-0400    1    182    101    {2986185E-CD31-4F1D-99A5-BEA6BD1EF53C}    200    8000ffff    AutomaticUpdates    Failure    Content Install    Installation Failure: Windows failed to install the following update with error 0x8000ffff: 2018-09 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4457144).
    2018-10-01    10:39:06:918     468    42c    Report    CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2018-10-01    10:39:06:918     468    42c    Report    WER Report sent: 7.6.7601.24085 0x8000ffff(0x8000ffff) 986185E-CD31-4F1D-99A5-BEA6BD1EF53C Install 200 0 AutomaticUpdates {9482F4B4-E343-43B6-B170-9A65BC822C77} 0

    Monday, October 1, 2018 2:44 PM
  • Reboot didn't fix. I did some "BINGing" and found that a missing patch, KB3177467, was the culprit.

    Manual download and install of KB3177467 did the trick.

    I think this is from 2016, but it never showed up on my server during Updates. It may be one of those that pops up when you run Update a 2nd time immediately after a successful update...

    Monday, October 1, 2018 4:27 PM