When a system doesn’t show up in WSUS, do these steps on the system not showing up:<\/p>\n
1) Verify this registry setting (usually set via a GPO):<\/p>\n
reg query HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows\\WindowsUpdate<\/strong><\/pre>\n2) Verify the System can resolve the hostname of the WSUS server, if specified. If IP, move on.<\/p>\n
3) Use telnet against the specified port (if different from 8530), this verifies layer 4 and that not firewall ports are in the way.<\/p>\n
4) Ensure the Windows Service is actually running via services.msc<\/p>\n
5) All else fails try this:<\/p>\n
net stop wuauserv\r\nreg delete HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\WindowsUpdate \/v SusClientId \/f\r\nreg delete HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\WindowsUpdate \/v SusClientIdValidation \/f\r\nnet start wuauserv\r\nwuauclt \/resetauthorization \/detectnow\r\nwuauclt \/reportnow<\/pre>\nWait a couple mins and hard refresh the WSUS MMC Snap-in. I noticed this trick also works for systems that are in WSUS but won’t report an install percentage of 100%.<\/p>\n
I noticed one system was not showing up with 100% install rate, and a yellow icon indicating needed updates still required, however checking for updates on the system kept reporting all updates, even after step 5 a couple times.<\/p>\n
So… to get updates WSUS doesn’t have on Desktop based version of Windows there’s usually a nice link that states “Check for updates from Windows Update Online”, but this was a core hyper-v server, and no GUI, so…<\/p>\n
*Note ByPassing WSUS on Core, without GPO changes.<\/p>\n
reg add HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows\\WindowsUpdate\\AU \/v UseWUServer \/t REG_DWORD \/d 0\r\nnet stop wuauserv\r\nnet start wuauserv\r\nsconfig<\/pre>\nrun option 6 and check for all updates (this assumes the server\/system has access to internet servers).<\/p>\n
Don’t forget to set the setting off again:<\/p>\n
reg add HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows\\WindowsUpdate\\AU \/v UseWUServer \/t REG_DWORD \/d 1<\/pre>\nThen run Step 5 again.<\/p>\n
Update* Feb 2020<\/p>\n
I discovered there’s a new “Expert” in WSUS named Adam<\/a><\/div>\nFollowing his suggestion on this technet post<\/a>, managed to resolve the issue and have his machine install the CU for 1909 and report it’s status to WSUS!<\/div>\n<\/div>\nnet stop bits<\/pre>\nnet stop wuauserv<\/pre>\nreg delete \"HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\WindowsUpdate\" \/v AccountDomainSid \/f<\/pre>\nreg delete \"HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\WindowsUpdate\" \/v PingID \/f<\/pre>\nreg delete \"HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\WindowsUpdate\" \/v SusClientId \/f<\/pre>\nreg delete \"HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\WindowsUpdate\" \/v SusClientIDValidation \/f<\/pre>\nrd \/s \/q \"C:\\WINDOWS\\SoftwareDistribution\"<\/pre>\nnet start bits<\/pre>\nnet start wuauserv<\/pre>\nwuauclt \/resetauthorization \/detectnow<\/pre>\n<\/div>\nOnly a couple systems that may need to be manually intervened before all systems report successfully and are 100% updated.<\/div>\n