none
Windows Server 2016 - WSUS Clients - WindowsUpdateFailure3, 1001, 0x8024500c

    Domanda

  • I've looked at everything I know to look at.

    The WSUS Server itself is running Windows Server 2016 DataCenter.

    The clients on our network are Windows 7 Enterprise, Windows 7 Professional, Windows 10 Professional, Windows 10 Enterprise, Windows Server 2016 Standard, Windows Server 2016 DataCenter and Windows Server 2008 R2 DataCenter.

    Only my Windows Server 2016 clients are having this issue.

    I've tried clearing the SoftwareDistrib folder, reregistering DLLs, re-indexing the SQL database, rebooting several times, etc.

    Our AD Group Policies are as such that INTERnet-based WSUS are prohibited as we want all updates to come from the local server.

    The WSUS server itself shows no signs of sync issues or issues downloading the actual updates.  I am at an absolute loss here.

    ****

    Fault bucket 127883099475, type 5
    Event Name: WindowsUpdateFailure3
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: 10.0.14393.1198
    P2: 8024500c
    P3: 00000000-0000-0000-0000-000000000000
    P4: Scan
    P5: 0
    P6: 0
    P7: 8024500b
    P8: UpdateOrchestrator
    P9: {9482F4B4-E343-43B6-B170-9A65BC822C77}
    P10: 0

    Attached files:

    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_10.0.14393.1198_802d6847332aebf619279c14e8638fd2125bcdcc_00000000_1bf75f67

    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 2aeac304-5ab2-11e7-90f5-70106fbf9c86
    Report Status: 0
    Hashed bucket: d1dff83bf57fb9291a38c9f8b68fde52


    ****

    WER File Output

    Version=1
    EventType=WindowsUpdateFailure3
    EventTime=131416677960233426
    Consent=1
    UploadTime=131429845363147214
    ReportIdentifier=f50bdb53-4eb8-11e7-90ef-70106fbf9c86
    AppSessionGuid=00000594-0000-0010-960c-34eea1cdd201
    TargetAppId=W:0000f519feec486de87ed73cb92d3cac802400000000!00000dac68816ae7c09efc24d11c27c3274dfd147dee!svchost.exe
    TargetAppVer=2016//07//16:02:25:32!d1ac!svchost.exe
    BootId=4294967295
    Response.type=4
    Sig[0].Name=ClientVersion
    Sig[0].Value=10.0.14393.1066
    Sig[1].Name=Win32HResult
    Sig[1].Value=8024402f
    Sig[2].Name=UpdateID
    Sig[2].Value=00000000-0000-0000-0000-000000000000
    Sig[3].Name=Scenario
    Sig[3].Value=Scan
    Sig[4].Name=RevisionID
    Sig[4].Value=0
    Sig[5].Name=IsManaged
    Sig[5].Value=0
    Sig[6].Name=LastError
    Sig[6].Value=801901f6
    Sig[7].Name=CallerAppID
    Sig[7].Value=UpdateOrchestrator
    Sig[8].Name=ServiceUsed
    Sig[8].Value={7971F918-A847-4430-9279-4A52D1EFE18D}
    Sig[9].Name=MiscField2
    Sig[9].Value=0
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=10.0.14393.2.0.0.272.7
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    State[0].Key=Transport.DoneStage1
    State[0].Value=1
    FriendlyEventName=Windows Update installation problem
    ConsentKey=WindowsUpdateFailure3
    AppName=Host Process for Windows Services
    AppPath=C:\Windows\System32\svchost.exe
    ReportDescription=A Windows update did not install properly. Sending the following information to Microsoft can help improve the software.
    ApplicationIdentity=00000000000000000000000000000000
    MetadataHash=410089339


    lunedì 26 giugno 2017 21:16

Risposte

  • We ended up spending the money on a Microsoft Support ticket.

    For us, it was a group policy.  If you enable the group policy Do not include drivers with Windows Updates, your local only WSUS config will break.  The fix is to either Disable that policy or set it back to Not Configured.

    Of course, the rep REFUSED to admit this is a bug and the conversation instantly tasted of bureaucrat.

    Even after making this GPO change, you will still need to delete the SoftwareDistribution folder.

    • Contrassegnato come risposta M.Reyes martedì 22 agosto 2017 17:01
    martedì 22 agosto 2017 15:17

Tutte le risposte

  • Hi MReyes-StancoDCSS,

    1. Have you ever installed any updates on the Server 2016, if not, please install one of the monthly rollup on the Server 2016 manually:

    https://support.microsoft.com/en-us/help/4000825

    2. If the Server 2016 could access the Internet, please test if they could download updates from Microsoft Update;

    3. If it still not work, please provide the related windows update log.

    Best Regards,

    Anne


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

    martedì 27 giugno 2017 06:06
    Moderatore
  • One of my servers - 10.0.14393.1198 - could not install KB4022723.  It says the update does not apply.

    I tried to install KB4023680 and it seems to be taking.  I will try KB4022723 after that.  My understanding is these updates are rollups and do not need to be installed in succession.  Is that true??

    martedì 27 giugno 2017 17:59
  • I've updated one of the test servers I'm running this on...The server is now patched to 10.0.14393.1230.

    All of the later patches throw an error stating the update does not apply.

    On a second server I'm following your instructions on did accept the patch and it's now running 10.0.14393.1378.

    Upon trying to run a Windows Update against the local WSUS, I'm seeing the exact same errors as before.

    If I remove the GPO setting and allow the servers access to the Internet-based WSUS repositories, the error will clear.  I need to get this to work without an Internet-based source.  If it can't, there may be a bug in Win2016 and/or WSUS.

    martedì 27 giugno 2017 18:25
  • Hi MReyes-StancoDCSS,

    Do you also patched the WSUS server 2016 as well?

    By the way, also run Server Cleanup Wizard on the WSUS server.

    Best Regards,

    Anne


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

    mercoledì 28 giugno 2017 07:00
    Moderatore
  • By Server Cleanup Wizard, I assume you mean the one inside WSUS...Cleanup wizard seems to hang at Deleting unused updates...

    No change.

    Yes, the 2016 WSUS server itself was patched yesterday.

    mercoledì 28 giugno 2017 15:07
  • The cleanup completed.  It just took a lot longer than I thought it would.


    No change.

    mercoledì 28 giugno 2017 16:46
  • My script usually fixes issues like this. Try running it. It does WAY MORE than the SCW, and fixes TONS of issues.

    Have a peek at my Adamj Clean-WSUS script. It is the last WSUS Script you will ever need.

    http://community.spiceworks.com/scripts/show/2998-adamj-clean-wsus

    What it does:

    1. Remove all Drivers from the WSUS Database.
    2. Shrink your WSUSContent folder's size by declining superseded updates.
    3. Remove declined updates from the WSUS Database.
    4. Clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs).
    5. Compress Update Revisions.
    6. Remove Obsolete Updates.
    7. Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days).
    8. Application Pool Memory Configuration to display the current private memory limit and easily increase it by any configurable amount.
    9. Run the Recommended SQL database Maintenance script on the actual SQL database.
    10. Run the Server Cleanup Wizard.

    It will email the report out to you or save it to a file, or both.

    Although the script is lengthy, it has been made to be super easy to setup and use. There are some prerequisites and instructions at the top of the script. After installing the prerequisites and configuring the variables for your environment, simply run:

    .\Clean-WSUS.ps1 -FirstRun

    and then

    .\Clean-WSUS.ps1 -InstallTask

    If you wish to view or increase the Application Pool Memory Configuration, you must run it with the required switch. See Get-Help .\Clean-WSUS.ps1 -Examples

    If you're having trouble, there's also a -HelpMe option that will create a log so you can send it to me for support.


    Adam Marshall, MCSE: Security
    http://www.adamj.org

    giovedì 29 giugno 2017 03:06
  • I've run most all of those tasks already.

    No change.

    giovedì 29 giugno 2017 16:59
  • Did you run my script or just comment on it?

    Adam Marshall, MCSE: Security
    http://www.adamj.org

    giovedì 29 giugno 2017 17:05
  • Any other thoughts Anne?
    giovedì 29 giugno 2017 17:07
  • Can't help the unwilling. There is a reason why my script is the number one downloaded script on Spiceworks.

    Adam Marshall, MCSE: Security
    http://www.adamj.org

    giovedì 29 giugno 2017 17:10
  • Not going to download a script into my production environment just because it's the #1 download from any site because someone says I should.  Not going to listen to the unprofessional and haughty.

    giovedì 29 giugno 2017 17:13
  • That's ok. We're each entitled to our own opinions. Just because I don't have Microsoft in my signature of where I work, doesn't mean that I don't know what I'm talking about.

    By all means, download the script and run each piece separately (it's all compartmentalized) with source URLs to the scripts (many are from technet). My script is very well documented, and the issue you're having stems most likely from lack of declining superseded updates, obsolete updates that need to be declined, and SQL Maintenance of the database.

    Something to try from the GUI, is to mass decline all superseded updates. They are superseded, which means that they are replaced with something that is already encompassing the superseded update.


    Adam Marshall, MCSE: Security
    http://www.adamj.org

    giovedì 29 giugno 2017 17:57
  • Hi MReyes-StancoDCSS,

    1. Please enable to IIS log on the WSUS server; (On server 2016, we need to enable IIS log additionally)

    2. Check updates on the WSUS client (Server 2016), then provide the windows update log and the IIS log for the trip, let's check if we could find the detailed cause of the issue.

    Best Regards,

    Anne


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


    martedì 4 luglio 2017 02:43
    Moderatore
  • 2017-07-05 14:41:32 W3SVC1535779138 vDCSS-WSUS02 fe80::7508:21c9:1aee:f3b8%5 POST /SimpleAuthWebService/SimpleAuth.asmx - 8530 - fe80::7508:21c9:1aee:f3b8%5 Windows-Update-Agent/10.0.10011.16384+Client-Protocol/1.40 - vdcss-wsus02:8530 200 0 0 187
    mercoledì 5 luglio 2017 14:56
  • 2017-07-05 14:28:33 fe80::7508:21c9:1aee:f3b8%5 GET /selfupdate/iuident.cab - 8530 - fe80::7508:21c9:1aee:f3b8%5 - - 200 0 0 0
    2017-07-05 14:28:33 fe80::7508:21c9:1aee:f3b8%5 POST /reportingwebservice/reportingwebservice.asmx - 8530 - fe80::7508:21c9:1aee:f3b8%5 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 15
    2017-07-05 14:28:33 fe80::7508:21c9:1aee:f3b8%5 POST /ApiRemoting30/WebService.asmx - 8530 DCSS\VDCSS-WSUS02$ fe80::7508:21c9:1aee:f3b8%5 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-07-05 14:28:33 fe80::7508:21c9:1aee:f3b8%5 POST /ServerSyncWebService/serversyncwebservice.asmx - 8530 - fe80::7508:21c9:1aee:f3b8%5 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-07-05 14:28:33 fe80::7508:21c9:1aee:f3b8%5 POST /ClientWebService/Client.asmx - 8530 - fe80::7508:21c9:1aee:f3b8%5 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-07-05 14:28:33 fe80::7508:21c9:1aee:f3b8%5 POST /SimpleAuthWebService/SimpleAuth.asmx - 8530 - fe80::7508:21c9:1aee:f3b8%5 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-07-05 14:28:33 fe80::7508:21c9:1aee:f3b8%5 POST /DssAuthWebService/DssAuthWebService.asmx - 8530 - fe80::7508:21c9:1aee:f3b8%5 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.42000) - 200 0 0 0
    2017-07-05 14:28:33 fe80::7508:21c9:1aee:f3b8%5 GET /Content/anonymousCheckFile.txt - 8530 - fe80::7508:21c9:1aee:f3b8%5 - - 200 0 0 0
    mercoledì 5 luglio 2017 15:06
  • I am having same issue as you, i tried many things like you did and have response.

    I just not tried to re-install WSUS, that I am trying not to do.

    I will try to run that script to see if I have any success.

    martedì 22 agosto 2017 15:04
  • We ended up spending the money on a Microsoft Support ticket.

    For us, it was a group policy.  If you enable the group policy Do not include drivers with Windows Updates, your local only WSUS config will break.  The fix is to either Disable that policy or set it back to Not Configured.

    Of course, the rep REFUSED to admit this is a bug and the conversation instantly tasted of bureaucrat.

    Even after making this GPO change, you will still need to delete the SoftwareDistribution folder.

    • Contrassegnato come risposta M.Reyes martedì 22 agosto 2017 17:01
    martedì 22 agosto 2017 15:17
  • Thank for the fix. Worked instantaneously after laboring  on it for a few days.
    mercoledì 28 marzo 2018 15:03
  • Doesn't that GPO only apply to windows 10? 
    venerdì 18 maggio 2018 00:57
  • I had this also, although I did not have drivers delivered via WSUS. I did an online update of the WSUS server (not using itself as an update source) and that resolved this for me. 

    lunedì 6 agosto 2018 08:43