Since installing updates yesterday, some of our Windows 7 and 2008 R2
servers refuse to connect to
our WSUS again and, instead, reports the unknown error 0x80244019 .The problem happens only withour local WSUS. The Windows support website on the error suggests: If you receive one of these errors while downloading updates, the most common cause is a I'm gonna vote No on that one. My WindowsUpdate.log shows the following:
And, actually, another support article caught my eye:
You cannot download updates when you access the Windows Update Web site from a Windows XP-based computer that is behind a firewall or a proxy server That article refers to XP, but I had to recently tweak the WinHTTP settings on our servers and clients in order to resolve a CAC (Common Access Card) Authentication issue with our Virtual VMs to resolve yet another issue. I fixed that access problem by running:
So, I'm assuming Windows Update uses WinHTTP as well, and my changes prevent it from working properly. But even after adjusting my bypass-list to "*.domain.example.com;<local>" , Windows Update refuses to function. |
||
Answer
|
Seems like a reboot was all that was needed after adjusting the
bypass-list , which must contain <local> so the WinHTTP proxy is bypassed for your local WSUS installation:
Alternatively, if you're already setting the correct proxy in IE (through group policy, for example), you can simply import those settings into WinHTTP:
To inspect your own current WinHTTP proxy settings, run netsh winhttp show proxy . |
No comments:
Post a Comment