Windows 10 - 1607 - Unable to download updates from WSUS

Forums › Microsoft Windows › Windows 10 - 1607 - Unable to download updates from WSUS

nzkiwiman

2154 posts

Uber Geek
+1 received by user: 182

Topic # 207262 16-Dec-2016 10:21

Anyone else having issues installing Cumulative Updates on Windows 10 1607? I am doing some test installs in a VM environment, following the same process I configured and setup for Windows 10 1507 and 1511 and just can't get the 1607 to obtain CU updates from our WSUS server.

Process is - using MDT 2013 to push out a basic installation of W10 1607 to a new VM, configure a few settings and then via WSUS move the computer to our testing group. Approve CU upgrade for installation and wait. Eventually the W10 machine picks up the update and downloads .. and stays at 0% for days. Removing the CU update from WSUS approval list, but allowing other 1607 updates works (ie, they install as expected on the WSUS server)

Note - the W10 1607 machine is not joined to our domain, and does not have internet access. WSUS access is configured via local group policy using the FQDN of our WSUS server.

jhsol

91 posts

Master Geek
+1 received by user: 22

Reply # 1692343 19-Dec-2016 18:43

Check to see whether you are suffering from this issue.

https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/

- Do a google search for KB3148812 and ensure your WSUS server has had the manual fix applied.

- Check to ensure your WSUS server has approved and downloaded the CU updates for 1607

- Check c:\windows\windowsupdate.log on the client and look for any errors (maybe post it up here if you can, you may need to run the get-windowsupdatelog PS command).

Jay

nzkiwiman

2154 posts

Uber Geek
+1 received by user: 182

Reply # 1692715 20-Dec-2016 11:18

I am not trying to install Anniversary Edition on a system from WSUS, which is what that article talks about.

However, I have since found out that the issue I am facing is a known issue that has not yet been fixed by Microsoft. The only way to resolve is to either manually install a CU (after downloading from the Update Catalog) or allowing the system direct access to the internet and download from Microsoft. I tested a manual install and confirmed it installed the CU successfully, and all other updates came through WSUS after the CU was removed from the approval list.

Any other future CU's will have to be installed manually until the issue is resolved by Microsoft

jhsol

91 posts

Master Geek
+1 received by user: 22

Reply # 1693061 21-Dec-2016 08:04

All good you got it sorted.

The article I linked (and KB3148812) was a patch that was released earlier on this year and broke WSUS updates. MS Patches for W10 from May onwards use a new encryption that WSUS was unable to decrypt, but W10 can decrypt natively. Hence W10 machines would update fine over the internet directly from MS Update but not via WSUS servers. You had to make a manual change to your WSUS servers in order to resolve it.

AHitman

79 posts

Master Geek
+1 received by user: 20

Reply # 1693991 22-Dec-2016 19:15

I also had the same issue with clients not downloading updates after 1607 (several months ago now), I even tried building a new WSUS server on Server 2016 however this had no impact.

I ended up pointing them direct to the internet for updates which "resolved" the issue, I was hoping to shift them back over the xmas break however it appears this may not be worth attempting yet.

Another Windows 10 bug to add to the growing pile I guess...