As folks have noted, these post-install steps caused unnecessary pain and confusion.
WSUS 3.2 cannot sync or distribute ESDs, and WS12/R2 can only do so if both KB3095113 and KB3159706 are installed on the machine, and all necessary post-install steps from KB3159706 have been followed. WSUS 3.0 SP2 on WS08R2 SP1 (or unpatched WS12/R2) cannot download ESDs Note that Configuration Manager will exhibit the same symptoms as each of the scenarios below.ġ. This thread calls out several different symptoms, for each of which I'll provide guidance. Hi everyone, and apologies for the frustration you're experiencing. Just for once, I wish that one of these 6mth updates could go off without some sort of major hitch! Windows 1511 updates no problem and you can even start the 1607 update from WSUS if I approve it for a computer. WSUS server has both of the Windows 10 related updates (including the one that required additional steps after installation).esd and now. Get-WindowsUpdateLog is of no help since I guess it needs some symbols to make the data readable.
Also adding KB3176929 made no difference (both of these are referenced by multiple threads)
I've tried setting the GPO option here to bypass with the intent of making sure the box gets updates straight from WSUS and not from other clients.Īdding KB3176495 as a preinstall package for one of my deployments via MDT seemed to help but it isn't working now. It likes to get stuck downloading updates and never go anywhere. If you google the issue, it appears that Windows 1607 doesn't play nice with WSUS.
0 kommentar(er)
