locked
Windows 10 Build 1607 Update RRS feed

  • Question

  • I am running WSUS on Windows Server 2012 and it shows the update "Feature update to Windows 10 Pro, version, en-us, Retail" as available. I approved the update but it fails to download showing the error "Content file download failed. Reason: File cert verification failure. Source File: /c/upgr/2016/08/14393.0.160715-1616.rs1_release_clientpro_ret_x86fre_en-us_8e519f5103a405e4f3b45845f48ddfd967749e68.esd Destination File: d:\wsus\WsusContent\68\8E519F5103A405E4F3B45845F48DDFD967749E68.esd."  I keep retrying the download but I get the same failure.  This is the only update on the server that fails to download.  Has anyone else seen this. Does anyone have a solution?
    Wednesday, August 17, 2016 1:57 PM

Answers

All replies

  • I am also running WSUS on Server 2012, and I don't even see the update as being available.  Did you have to enable any other product classifications to get it to show up?
    Wednesday, August 17, 2016 6:23 PM
  • Hi IAGoldWing,

    Have you installed KB3159706 on the WSUS server?

    If not, please install the KB and do manual steps.

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

    Best Regards,

    Anne


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

    Thursday, August 18, 2016 6:07 AM
  • I just checked and KB3159706 is installed on the server. I did the "Manual steps required..." this morning but this has not resolved the issue.  I did not do SSL portion as I am not running my WSUS as an SSL connection.
    Thursday, August 18, 2016 1:52 PM
  • I found out today this patch kb3095113 needs to be applied which I did. I then followed instructions here How to delete upgrades in WSUS so my downloads are successful to my WSUS server.  I am now faced with issue outlined here 1511 to 1607 Enterprise feature upgrade failing .
    Friday, August 19, 2016 1:39 PM
  • Hi IAGoldWing,

    1. Since your original issue has been solved, then you'd better mark your last reply as answer and close this case, since it may be clear for others to read if one post owns one question.

    2. As for WSUS server can download 1607 upgrade file successfully, while clients unable to install; then please check if you add .esd MIME type in WSUS IIS;

    3. If you still have issues with upgrading clients to 1607, then it's better to create a new post, then you'll get better help;

    Best Regards,

    Anne


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


    Monday, August 22, 2016 8:20 AM
  • I'm seeing a lot of references to 1607 - which I never got though the Updates and Servicing - I got 1606 which failed but would never allow me to find out why (logs or otherwise). I used the resultant download installation (manually) 1602 (which everyone here is referencing at 1603(?)) and got everything to work fine now. The Updates and Servicing portal doesn't seem to work right for me.
    Sunday, September 4, 2016 8:40 PM
  • Hi hankiepoo,

    It's better to create a new post for yourself, descript the detailed issue that you meet, then, you'll get better help.

    Best Regards,

    Anne


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

    Wednesday, September 7, 2016 1:44 AM