Error 0x80242002b

  • Thread starter Thread starter Guest
  • Start date Start date
It's nice to see I am not the only one who felt out in left field in thinking
that something that was there should still be there. Our company also uses
WSUS but allows for remote updates directly from the MS Site. Antispyware
beta 1 works fine with proxy authentication.

Having supported the PC for over 23 years I can tell you that I have seen my
share of good and bad software. Something compatible with multiple
environments, and easily configurable to changing environments is the
software most company IT professionals look for. Thousands of people work
for company A but need to be onsite at company B for a day, a week, month or
year. Having software that lets you adapt to the alternative network
environment is essential for good business functionality for your employee at
a remote site. Every day more and more people are working in environments
the infrastructure team of the company they work for say is unsecure or
hostile. Yet these people still need to do their jobs. Making it harder to
comply by less functionality only makes the product less marketable and
useable for some companies.
 
Exactly. My whole issue with the "it's engineered to update through
automatic updates" thing is this: sure it does make keeping the software up
to date much easier, but the first thing the app does after install is prompt
you with an "update now" button and tells you to click it to update your
definitions.

Why keep the prompt and button? Why not just change the prompt to tell
users to visit the microsoft update site instead? Simple.
 
For the vast majority of users this process works. Additionally, if you do
a new install with the current code, there's a link on that initial page to
the troubleshooting KB, for folks who get stuck from the beginning.

When I say vast majority--I mean folks for whom AutoUpdate is working
routinely, and who have kept patched to date with critical update. Or,
corporate managed desktops who have mandated Windows Defender and are thus
already providing definitions via WSUS over their networks.

The generic messages aren't helpful--but they are mostly seen in situations
where Windows Defender isn't designed to fit--corporate desktops without the
infrastructure support, for example.

--
 
Back
Top