It's needed for Windows Server 2012 and Windows Server 2012 R2 users that want to keep Windows 10 clients up to date.This WSUS update can't be skipped by those users, Microsoft's announcement explained: Skipping this KB [KB3159706] means not being able to distribute the Windows 10 Anniversary Update, or any subsequent feature update, via these platforms.The environment is as below: WSUS Server : Win Server 2003 R2 SP2 (with internet connection) (IP: 192.168.207.188)(Version: 3.2.7600.226)WSUS Client : Win Server 2008 R2 Standard (without internet connection, but connected through local network to the server) (192.168.207.130)The Client can be found in Admin Console of the server, and all updates have been approved (Critical and Security updates only).However, I could not get the updates to be downloaded and installed in the Client, despite there is no error message in the Windows file.Until now, we have been manually decrypting these packages prior to releasing to the WSUS channel, the process of which is both time consuming and error prone.KB3159706 introduces this functionality to WSUS for /R2, such that it can now natively decrypt this content.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.https://blogs.technet.microsoft.com/mni ... If ($Result.reboot Required) I don't know about this issue, just trying to assist.s-10-1607/Adding KB3176495 as a preinstall package for one of my deployments via MDT seemed to help but it isn't working now. Have you considered using Fiddler2 to validate the machine is reaching out to the correct WSUS and not any peers?
It likes to get stuck downloading updates and never go anywhere.Hello, I have a WSUS serer where it has been updating Windows 10 clients for about a year.Now I have noticed about 30 of the Windows 10's clients are loosing there connection to the WSUS server.However, the patch had some flaws, causing WSUS to not be able to connect with Windows clients, among other problems.Some organizations that applied the flawed KB3148812 update have had dysfunctional WSUS systems for almost two weeks. The fix is a new Knowledge Base item called "KB3159706," as described in this announcement today.