Wsus 3 0 clients not updating

Important Windows Server 2008 R2 requires WSUS 3.0 SP2.If you install Windows Server 2008 R2, you should install WSUS 3.0 SP2.

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?

For further details on cookies, please see our cookies policy.

I am not going to rebuild any of the others, but am floored that even the server that WSUS resides on can't report status.

I havesuccessfully downloaded updates and have the console configured. All client gpo's in Active Directory point to the new server (

NET App Pool, Default App Pool, and Wsus Pool) are all set to Classic for Managed Pipeline)which allows the WSUS console to work properly, else it errors out.This shows that IIS and its pipings are broken and client computers cannot communicate with the server.ABC-Update is a freeware tool available from and it is designed to do just what you are asking.This update fixes the following issue: when you try to install 80 or more updates at the same time the Web page of the Windows Update or Microsoft Update Web page, you may receive the error code 0x80070057. enhancements and issues that are fixed by version 7.2.6001.784 of the Windows Update Agent.This update fixes the following issue: improves Windows Update check time, improves the speed at which signature updates are delivered, enables support for Windows Installer reinstallation functionality and enhances the error messages. the WSUS 3.0 SP2 and Windows 7 include a new version of Windows Update Agent (to Windows XP, Vista, Windows Server 2000, Windows Server 2003 and Windows Server 2008).