locked
1607 Anniversary Update never installs RRS feed

  • Question

  • Hello,

    It seems everyone has had this issue where there WSUS server couldn't install the 1607 Anniversary Update on their Windows 10 PCs.

    I'm still getting the issue and I must of read every post to try and fix it, but have failed.  We are on Windows 2012R2.

    If I manually install the update then the PCs will then be fine and start to download and install further updates.

    Should I rebuild the server from scratch?  If so does someone have the perfect guide I could follow?

    Here is a link to the get-windowsupdate log file of a PC with the issue, maybe you can see something I can't?

    Get-WindowsUpdate log file

    On this PC there seems to be quite a few Event ID 1001 information events like this too:

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

    Problem signature:
    P1: 10.0.10586.672
    P2: 80244007
    P3: 00000000-0000-0000-0000-000000000000
    P4: Scan
    P5: 0
    P6: 1
    P7: 0
    P8: TrustedInstaller FOD
    P9: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    P10: 0

    Attached files:
    C:\Windows\Temp\WER9CD4.tmp.WERInternalMetadata.xml

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

    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 6d840ff1-2410-11e7-831b-4851b720ac9b
    Report Status: 0
    Hashed bucket: 395405586e6c3b63ed9d62a54b6f611d


    Thanks in advance



    • Edited by TB303 Tuesday, April 18, 2017 8:34 AM
    Tuesday, April 18, 2017 8:19 AM

Answers

All replies

  • Hi TB303,

    >Should I rebuild the server from scratch?  If so does someone have the perfect guide I could follow?

    I would recommend re-build the WSUS server from scratch, and check the result:

    1. Remove WSUS role and WID role in Server Manager;

    2. Delete WSUS content folder and WSUS site in IIS;

    3. Install SQL server management studio 2012:

    https://www.microsoft.com/en-sg/download/details.aspx?id=29062

    Use \\.\pipe\MICROSOFT##WID\tsql\query to connect to WID, then detach and delete SUSDB:

    4. Delete SUSDB.mdf and SUSDB_log.ldf in C:Windows\WID\Data;

    5. Then restart WSUS server;

    6. Install WSUS role, when configure "Products and Classifications", do not check "Upgrades".

    7. Install KB3095113 and KB3159706(with manual steps), restart the server to finish installation;

    8. After installation the above KBs, check "Windows 10" in "Products" and check "Upgrades" in "Classifications", then sync from MU;

    9. Wait clients to show up and report to the WSUS server, then approve the 1607 upgrade file for the test clients.

    10. Before clients downloading the upgrade file, please add .esd MIME type into WSUS site in IIS:

    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.


    Wednesday, April 19, 2017 7:15 AM
  • Hello,

    I've done this and will see what happens.

    No computers have checked in yet and it's been a hour or so, should some be in there by now?

    Thanks

    Wednesday, April 19, 2017 11:07 AM
  • I've been trying to sync and I get this error:

    IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
    at System.Net.ConnectStream.Read(Byte[] buffer, Int32 offset, Int32 size)
       at Microsoft.UpdateServices.ServerSync.ServerSyncCompressionProxy.GetWebResponse(WebRequest webRequest)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
       at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetUpdateData(Cookie cookie, UpdateIdentity[] updateIds)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.WebserviceGetUpdateData(UpdateIdentity[] updateIds, List`1 allMetadata, List`1 allFileUrls, List`1& updatesWithSecureFileData, Boolean isForConfig)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.GetUpdateDataInChunksAndImport(List`1 neededUpdates, List`1 allMetadata, List`1 allFileUrls, Boolean isConfigData)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)

    Wednesday, April 19, 2017 2:29 PM
  • Hi Anne,

    I've rebuilt the server and I can see that there PC's showing in WSUS again, but all of them say 0 for needed updates, why would this be?

    Friday, April 21, 2017 8:28 AM
  • Hi TB303,

    What is the situation now, are they still report as "0" needed updates?

    When you re-install, do you use the above steps to remove the original SUSDB correctly?

    Could you provide the screenshot of WSUS overview?

    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.

    Monday, April 24, 2017 8:04 AM
  • Hi,

    I've got the computers checking in now.  So I have 1 windows computer that WSUS says it needs 32 updates which I have approved, if I manually run the windows updates it says it's already up-to-date.

    The windows log file says it found 0 updates.

    Not sure where to go with this now.


    Monday, April 24, 2017 9:52 AM
  • Here you go Anne:

    and I guess this looks ok in IIS?

    • Edited by TB303 Tuesday, April 25, 2017 2:32 PM
    Tuesday, April 25, 2017 6:34 AM
  • Hi TB303,

    >So I have 1 windows computer that WSUS says it needs 32 updates which I have approved, if I manually run the windows updates it says it's already up-to-date. The windows log file says it found 0 updates.

    Try resetting windows update components on the client that report as "up to date";

    https://support.microsoft.com/en-us/kb/971058

    Also "check online for update" on that computer, check if it could detect updates from Microsoft Update.

    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.

    Wednesday, April 26, 2017 7:59 AM
  • Built a Windows 2016 WSUS server and everything works now.
    Thursday, April 27, 2017 11:20 AM
  • Hi TB303,

    Glad to hear everything working now, then, you may mark useful reply in this post as answer, so that this thread can be ended.

    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.

    Tuesday, May 2, 2017 1:44 AM