can't "always ignore" solved (thanks bill sanderson)

[danm]

Thanks bill sanderson. I see what you mean. Uninstalling
the antispyware program, doesn't. It leaves many files
behind. Hope they can fix that before it gets out of beta.
I realize that some people might want to save settings in
case of a reinstall. That means that they should be given
that option during an uninstall. But once I uninstall a
program, my computer should be the same as before the
program was installed.
Anyhow, doing a complete uninstall (including manually
removing the previous install folders and subfolders)
before reinstalling, solved my problem.
Digging around a little, I wonder if the problem might
involve the errors.log file although I haven't proven that
to myself. The erroneous installtion (the one in which I
couldn't get always ignore to work), had an errors.log that
was over 6MB large. Don't know what that means. Perhaps in
the future, it might pay to look at that. Does a huge
errors.log mean it's corrupt? Can that cause some
problems? Or does it indicate that there are problems
(hence the huge file)? Or am I totally off base here?
Anyhow, just thought I'd add my two cents and my thanks.

 

[Bill Sanderson]

Thanks for keeping up on this, and the feedback.

Indeed, I believe that the stuff left behind is intended as a safety
mechanism--to allow for uninstall/reinstall with retained settings, and
access to quarantine, for example. I agree with your sentiments about
that--give the user a choice. A number of other programs do offer that
choice--about quarantined items, for example--on uninstall.

The errors.log file has been a problem in earlier builds--it could grow
unconstrained to 4 gigabytes on an NTFS partition, and sometimes did. In
the newest builds, there is a limit on the file--can't remember precise
details.

There have been a handful of issues over the course of the beta which have
had some light shed on them by looking at the content of the errors.log
file. But most of the time, and for most users, this file is better
ignored.

As to whether your large file means that something useful was actually being
recorded there that might have helped with the "always ignore" issue, I
don't know--I tend to doubt it--but maybe some engineer in Redmond could
have looked at it and said--yeah--blow thus and such away and that'll fix
it.