Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, January 21, 2016 1:28 AM
Pushing via WSUS on Win Server 2012 R2. When I do an win update check it sees the update and attempts to install but it fails. I get this in the event log:
Installation Failure: Windows failed to install the following update with error 0x8007007E: Upgrade to Windows 10 Pro, version 1511, 10586 - en-us, Volume.
Any help is greatly appreciated. Thanks.
J. Swann – Information Security Engineer
All replies (4)
Friday, January 22, 2016 8:26 PM ✅Answered
I got it working by bypassing my WSUS and downloading the upgrade directly from Microsoft via my win updates. I tried publishing the Retail and Volume versions in WSUS, both together and separately and got install failures as soon as the installs started. However, when I chose to update from MS it worked perfectly.
Apparently there's a different version of the same KB and I'm publishing the one(s) not meant for my flavor of win 10. I'm really unhappy with how convoluted MS is making this.
J. Swann – Information Security Engineer
Friday, January 22, 2016 6:04 AM
Hi J. Swann,
Did the issue occur with all the machines or the specific one? Did the issue occur when we download the update or when we install the update?
First of all, please ensure the following hotfix is installed on the machine to support Windows 10 feature upgrades.
Update to enable WSUS support for Windows 10 feature upgrades
https://support.microsoft.com/en-us/kb/3095113
If the issue occur when we download the update. We should configure the IIS. Windows 10 Pro, version 1511, 10586( KB3012973 ) is an upgrade not a normal update. It includes the .esd format ISO. To use wsus, we should add the .esd MIME type to IIS for the WSUS server as application/octet-stream allows the IIS server to serve the new update file type. For more information about this, we could ask for help fron our Server forum.
WSUS
https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverwsus
If the issue occurred during the upgrade process, we could check the setupact.log (C:\Windows.~WS\Sources\Panther)for more information to troubleshoot this issue.
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Monday, January 25, 2016 5:47 AM
Hi J. Swann,
So the issue is resolved by upgrade from Windows Update directly. I am glad the issue has been resolved.
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Tuesday, May 31, 2016 4:53 PM
This needs to be added to the documentation for WSUS. We don't need a hundred machines going out and downloading gigs of upgrade files individually. Bad enough on a high speed connection, totally painful on a slow connection. Thanks to J. Swann on enlightening us on the file type for the upgrade. Too bad MS didn't put a patch out for WSUS that prepped IIS for the .esd extension so it would work like it should. That was all that was needed to keep everything in-house and save wasting additional bandwidth. WSUS upgrade from Win 10 to Win 10/1511 has taken about 30 minutes total. Will test it on a Win 7 machine now.
Regards,