Signature update failure 0x80244021

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi all,

I'm unable to download sig updates, with 0x80244021 reported as the failure.
MSDN reports this as:

WU_E_PT_HTTP_STATUS_BAD_GATEWAY

0x80244021
Same as HTTP status 502 – the server, while acting as a gateway or proxy,
received an invalid response from the upstream server it accessed in
attempting to fulfill the request.

I'm not sure what the actual path is here, but I've got a WSUS server on the
same subnet with a non-caching ISA internet gateway between my workstation
and the internet. The WSUS server has the definitions category checked and
the defender def's approved for install.

Any ideas?

Thanks!
 
Clearly, your administrator has done the right thing, so Engel's reference
doesn't help.

Any idea whether any other machine on the subnet has been able to pick up
signatures via WSUS?
 
Thanks Bill. Good idea - I've installed Defender on another workstation and
it was able to update successfully.

On the machine with the error, I did upgrade to Defender (beta 2) from
Anti-Spyware (beta 1), and in the process of troubleshooting this uninstall
Defender and reinstall it. I've also run the manual MSI uninstall of the
signatures (which didn't fix it either).

Thanks!
 
Windows Defender does pick up information from the Microsoft Antispyware
install. For example, the scheduled scan time is migrated. Since the
signature update functionality is so much changed, I wouldn't think that
much in the way of proxy settings or network-related stuff would be
migrated, but I don't know.

So--you've got a working WSUS server, and another machine picks up
signatures correctly from it, but this one gets this strange error.

I'm hoping the 'softies will be back on Tuesday and get a look at the
messages here again.

If you, for example, uninstall some carefully chosen security update from
the "bad" machine, is it able to pick it up again from the WSUS server?
--
 
WSUS works fine otherwise for the machine, it's my primary workstation. My
guess is it's something with the anti-spyware -> defender state giving us
grief. Thanks for the time thinking about it though.
 
You might mess with the proxy settings in IE. I've seen, on the same
network behind a transparent ISA-2000 proxy, machines where setting
"automatically detect" seemed to trigger updating, and others where removing
that setting did the same. Those machines got numeric errors on the attempt
to update, but I didn't keep track of what they were.

--
 
Back
Top