Windows Update now recommends the installation of Update for Windows Server Update Services 3.0 SP2 [for x64-based Systems] (KB2720211).It’s a 28 MB download from Microsoft servers if you’re curious.If the issue is with your computer or a laptop/notebook you should try using the Reimage Plus Software which can scan the repositories and replace corrupt and missing files.
Verify that the update still exists and is applicable to this computer from your WSUS server or Windows Update.
To give your server a chance at receiving updates—including Windows Server Update Services 3.0 SP2 Dynamic Installer for Server Manager [x64 Edition] (KB972493)—through Microsoft’s website, temporarily disable intranet Microsoft update service location: Edit the Default Domain Policy in Group Policy Management, open , pick a single product with fewest updates possible (e.g., Silverlight).
But deep inside the WSUS server, things are a mess: The WSUS server is the only computer that can get updates from itself, it cannot communicate with clients, and after a few days, all computers—except for the WSUS server itself—are listed as .
Visiting Event Viewer Custom Views for Server Roles, or hitting the Roles’ list collapse sign (plus sign inside the square) on Server Manager and looking into each role’s events, you’d be surprised to see there’s no recent events or perhaps no events at all listed for Web Server (IIS).
This shows that IIS and its pipings are broken and client computers cannot communicate with the server.