G
Guest
Well I stuck with beta 2 for quite a while, but now we're into December it
seemed I'd better take the plunge. (Fresh installations of important programs
are anxious times for people like me who don't really know what's going on.)
The short story is that I closed down all the bits of my AVG security suite,
switched Defender's RTP off, used Dave M's trick (Run 'net stop windefend')
and installed 1593.0 over the top of Beta 2. As far as I can tell so far, the
installation seems to have been successful. A manual update after
reconnecting to the internet seemed to go smoothly, and it scans OK. So far
so good. Even so, I can't help but observe the following:
1. It still doesn't recognise ATWPKT2.sys (the aol driver) as acceptable.
Worse than this, I noticed that already, in the History log, it had recorded
its 'suspicious' behaviour and ALLOWED it without asking me - this before I
had chance to change any settings. Despite having allowed it without asking
me, and despite my putting its file path into its 'don't scan' list, Defender
now goes on and on filling up my Event log with alerts to the behaviour of
ATWPKT2 just like it always did. What was the point of all the feedback I put
in this news group about these false alerts, if no one takes any notice?
2. The install procedure is a small nightmare for the uninitiated. The first
thing that met my gaze was a page of stuff about Genuine Windows. I was
baffled - I'd already gone through all this when I downloaded the program.
Did I have to do it again? Should I connect to the Internet? But if I did
that - I'd have to start up all my security software again, and I'd closed
that all down just for this installation .... In the end I just clicked on to
the next stage and it seemed to be ok. But what the heck was the point of all
that stuff, when all it does is confuse the user at a crucial moment?
3. I was presented with 3 choices, and warned (I forget the details) that if
I made the wrong choices I might mess the security up (or words to that
effect). I could not for the life of me see which of the three to choose, no
matter how many times I read them, nor could I see on what basis I was
supposed to know how to choose, nor how the alternatives were related to each
other. I decided in the end that since I didn't at this stage want to get
entangled in this thing called spynet which was included in option 1, and
option 3 looked positievely dangerous, I'd choose 2. But I didn't then, and
don't now, properly understand the consequences of my choice.
4. While it was updating its definitions I read the 'help', and I looked at
the 'options'. I still don't understand half of what's there (I never did),
and just left the settings on default, because when it really matters and you
have to decide on a setting, the 'help' is often no help at all..
My conclusion is that if this final version is supposed to be suitable for
the general user, then it isn't. It's way, way off target. It's only suitable
for people who have a pretty good idea about what they're doing, and I
suspect that it's very, very easy to set it up wrongly - and I mean
dangerously wrongly, so that things the user should be alerted about may be
missed, while perfectly innocuous things like aol drivers will go on
generating alerts in the event log even when you try to tell the program to
cool it. I'm not myself confident that I have this set up correctly, despite
having been using Defender and reading this newsgroup for months.
It's still basically a program for the technophile. 9 out of 10 users won't
have a clue what's going on when they try to set it up, look in the history
log, or get an alert.
seemed I'd better take the plunge. (Fresh installations of important programs
are anxious times for people like me who don't really know what's going on.)
The short story is that I closed down all the bits of my AVG security suite,
switched Defender's RTP off, used Dave M's trick (Run 'net stop windefend')
and installed 1593.0 over the top of Beta 2. As far as I can tell so far, the
installation seems to have been successful. A manual update after
reconnecting to the internet seemed to go smoothly, and it scans OK. So far
so good. Even so, I can't help but observe the following:
1. It still doesn't recognise ATWPKT2.sys (the aol driver) as acceptable.
Worse than this, I noticed that already, in the History log, it had recorded
its 'suspicious' behaviour and ALLOWED it without asking me - this before I
had chance to change any settings. Despite having allowed it without asking
me, and despite my putting its file path into its 'don't scan' list, Defender
now goes on and on filling up my Event log with alerts to the behaviour of
ATWPKT2 just like it always did. What was the point of all the feedback I put
in this news group about these false alerts, if no one takes any notice?
2. The install procedure is a small nightmare for the uninitiated. The first
thing that met my gaze was a page of stuff about Genuine Windows. I was
baffled - I'd already gone through all this when I downloaded the program.
Did I have to do it again? Should I connect to the Internet? But if I did
that - I'd have to start up all my security software again, and I'd closed
that all down just for this installation .... In the end I just clicked on to
the next stage and it seemed to be ok. But what the heck was the point of all
that stuff, when all it does is confuse the user at a crucial moment?
3. I was presented with 3 choices, and warned (I forget the details) that if
I made the wrong choices I might mess the security up (or words to that
effect). I could not for the life of me see which of the three to choose, no
matter how many times I read them, nor could I see on what basis I was
supposed to know how to choose, nor how the alternatives were related to each
other. I decided in the end that since I didn't at this stage want to get
entangled in this thing called spynet which was included in option 1, and
option 3 looked positievely dangerous, I'd choose 2. But I didn't then, and
don't now, properly understand the consequences of my choice.
4. While it was updating its definitions I read the 'help', and I looked at
the 'options'. I still don't understand half of what's there (I never did),
and just left the settings on default, because when it really matters and you
have to decide on a setting, the 'help' is often no help at all..
My conclusion is that if this final version is supposed to be suitable for
the general user, then it isn't. It's way, way off target. It's only suitable
for people who have a pretty good idea about what they're doing, and I
suspect that it's very, very easy to set it up wrongly - and I mean
dangerously wrongly, so that things the user should be alerted about may be
missed, while perfectly innocuous things like aol drivers will go on
generating alerts in the event log even when you try to tell the program to
cool it. I'm not myself confident that I have this set up correctly, despite
having been using Defender and reading this newsgroup for months.
It's still basically a program for the technophile. 9 out of 10 users won't
have a clue what's going on when they try to set it up, look in the history
log, or get an alert.