[SOLVED] Windows 10 Pro 1809 will not check for updates from WSUS server Error Code 80244022

Bigdog0016

New member
Joined
Jan 18, 2019
Posts
2
I have a workstation that is running Windows 10 Pro 1809. This will no longer take updates from my wsus server. I always get error code 80244022. I have tried some standard fixes, sfc scan, show all icons on taskbar trick, /detectnow and /reportnow with wauclt at command line. Windows update troubleshooting tool errors out when trying to troubleshoot. SFCFix tool says it detected no corruptions. I've stopped update services and bits, and renamed windows/softwaredistribution folder. I updated from 1709 to 1809 manually by downloading update assistant from windows. I've used powershell command get-windowsupdatelog and in the log I see the following:

2019/01/18 15:50:16.6217742 128 8552 WebServices WS error: There was an error communicating with the endpoint at 'http://wsus2.diageo.control:8530/ClientWebService/client.asmx'.
2019/01/18 15:50:16.6217852 128 8552 WebServices WS error: The server returned HTTP status code '503 (0x1F7)' with text 'Service Unavailable'.
2019/01/18 15:50:16.6217911 128 8552 WebServices WS error: The service is temporarily overloaded.

However all my other servers/pc's on the network are taking updates normally. I can ping the wsus server fine, it has taken some updates in the past.

I've went into iis on WSUS in increase the private memory limit for the wsuspool and verified wsuspool was running.

Many reboots later and I am still stuck with this error code.

See attached for windowsupdatelog.txt and CBS.zip

HELP PLEASE!!
 

Attachments

I've run through WSUS Maintenance. What I found that seemed to fix the issue was our proxy setup. If I enable the proxy, even if I have the checkbox selected for 'bypass proxy for local addresses', it causes that error. When I turned the proxy off, it seemed to take updates. I don't necessarily need the proxy on, just using it to check for windows updates online. It's accessing the wsus via http://servername.domain, but I had to add this to the local list in proxy setup for some reason. Other PCs on my network running Win 7 or Server 2008r2 work fine with proxy enabled bypassing proxy for local addresses.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top