J
JOE
Hi,
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
J
John
What other programs like Norton or McAfee are you running that might
interfere?
interfere?
B
Bill Sanderson
Do you get an error message?
Here's what I would recommend, in general:
1) try the uninstall via control panel. If that fails, please try the
change, update options in that same place. If that operation succeeds, then
try the uninstall.
If uninstall still doesn't work, download the Windows installer cleanup app:
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301
Use it to remove Installer-related traces of Microsoft Antispyware.
If that succeeds, I'd then recommend installing Microsoft Antispyware, and
then removing it.
I make that recommendation with the thought that this will leave things in a
known state--i.e. as they would be if all had gone routinely. You could
stop at the installer cleanup, or combine that with blowing away the install
directory, but I'd prefer to go through the whole process and try to leave
things in a known state.
Want to say more about why, and what you think the problem may be?
Here's what I would recommend, in general:
1) try the uninstall via control panel. If that fails, please try the
change, update options in that same place. If that operation succeeds, then
try the uninstall.
If uninstall still doesn't work, download the Windows installer cleanup app:
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301
Use it to remove Installer-related traces of Microsoft Antispyware.
If that succeeds, I'd then recommend installing Microsoft Antispyware, and
then removing it.
I make that recommendation with the thought that this will leave things in a
known state--i.e. as they would be if all had gone routinely. You could
stop at the installer cleanup, or combine that with blowing away the install
directory, but I'd prefer to go through the whole process and try to leave
things in a known state.
Want to say more about why, and what you think the problem may be?
J
JOE
Thanks Bill,
Just saw your response here - Actually you can remove
this thread, or merge it to the slightly later one, since
it got created accidentally, with my "keyboard fat-
fingering problems". I re-initiated this discussion in
the thread immediately above this one. Thanks.
However, as you are reading this here - I had already
done all you suggest: to repeat -
(a) ADD/REMOVE of MSAS did no work in Control Panel, so
(b) next, tried the UNINSTALL MSAS in it's START-Programs
section, but didn't really expect it to work, (just
another entry point), so I
(c) ran the MSAS CHANGE option in ADD/REMOVE, and looking
at some of the module dates, it looked like it did change
some of them to an updated 509 Beta. In fact, the CPU
was no no longer consuming 100%, but was down to about
80% with the updated version (from FEB 8 to the FEB 16
Beta), and Virtual Memory was now flat-lined low
(finally). But still no joy, so I
(d) went to the MSAS download site using IE6, and did
a "formal downlaod", and install - could not tell what it
was doing during install of this file, since it was
running in "stealth mode", no screens, just a lot of
(disk & CP process) activity - which concerned me, so I
killed it's "process" (again) after a few minutes, before
mybe(?) something damaged the system. It might have been
doing an inial disk scan - but it wasn't in responnse to
my acceptance, as it would have normally.
As to your concerns about AVG and Zone Alarm - I was
running "bare-assed" all that time, since "something
(either NIS or a virus) had already uninstalled AVG (I
had to re-install it later, from it's original download
file), and had diasbled Zone Alarm. I suspect that
happened during the install from the Norton Internet
Security 2005 CD, which also got really messed up by
something (but, the next day, Feb 9) - logs indictate NIS
2005 ran to a "clean completion" , as did also MSAS
on "installation that previous day.
I repeated the above described attempts, as you
suggest here, once again, after re-activating both AVG-
7.0 and Zone Alarm, with the same results.
At least I now have "basic protection" with these
freebies, until I get MSAS and NORTON uninstalled - and
then properly re-installed after cleanup.
To answer your question about "messages" - there were
NONE from either MSAS or NORTON - neither one produced a
run-screen, task bar icon, or any message - that it is
running, or even a splash screen, or error screen. They
just ran silently doing whatever they (or it), liked.
With that, can you help out by providing a "manual de-
installation procedure, or script" so I can get MSAS &
NIS both off the system, before re-installing them?
At least, if I could de-install MSAS, and re-install it,
and maybe run properly for a few days, before adding NIS
2005 to the mix, it might explain which one might be
causing the mutual conflict - although, I still suspect
the KILLAV virus, which was only "reported" to SYMANTEC,
2 days after my installs. Perhaps this PC was one of the
few "early buyers" of this virus - timing seems
coincidental.
Thanks
Joe
Just saw your response here - Actually you can remove
this thread, or merge it to the slightly later one, since
it got created accidentally, with my "keyboard fat-
fingering problems". I re-initiated this discussion in
the thread immediately above this one. Thanks.
However, as you are reading this here - I had already
done all you suggest: to repeat -
(a) ADD/REMOVE of MSAS did no work in Control Panel, so
(b) next, tried the UNINSTALL MSAS in it's START-Programs
section, but didn't really expect it to work, (just
another entry point), so I
(c) ran the MSAS CHANGE option in ADD/REMOVE, and looking
at some of the module dates, it looked like it did change
some of them to an updated 509 Beta. In fact, the CPU
was no no longer consuming 100%, but was down to about
80% with the updated version (from FEB 8 to the FEB 16
Beta), and Virtual Memory was now flat-lined low
(finally). But still no joy, so I
(d) went to the MSAS download site using IE6, and did
a "formal downlaod", and install - could not tell what it
was doing during install of this file, since it was
running in "stealth mode", no screens, just a lot of
(disk & CP process) activity - which concerned me, so I
killed it's "process" (again) after a few minutes, before
mybe(?) something damaged the system. It might have been
doing an inial disk scan - but it wasn't in responnse to
my acceptance, as it would have normally.
As to your concerns about AVG and Zone Alarm - I was
running "bare-assed" all that time, since "something
(either NIS or a virus) had already uninstalled AVG (I
had to re-install it later, from it's original download
file), and had diasbled Zone Alarm. I suspect that
happened during the install from the Norton Internet
Security 2005 CD, which also got really messed up by
something (but, the next day, Feb 9) - logs indictate NIS
2005 ran to a "clean completion" , as did also MSAS
on "installation that previous day.
I repeated the above described attempts, as you
suggest here, once again, after re-activating both AVG-
7.0 and Zone Alarm, with the same results.
At least I now have "basic protection" with these
freebies, until I get MSAS and NORTON uninstalled - and
then properly re-installed after cleanup.
To answer your question about "messages" - there were
NONE from either MSAS or NORTON - neither one produced a
run-screen, task bar icon, or any message - that it is
running, or even a splash screen, or error screen. They
just ran silently doing whatever they (or it), liked.
With that, can you help out by providing a "manual de-
installation procedure, or script" so I can get MSAS &
NIS both off the system, before re-installing them?
At least, if I could de-install MSAS, and re-install it,
and maybe run properly for a few days, before adding NIS
2005 to the mix, it might explain which one might be
causing the mutual conflict - although, I still suspect
the KILLAV virus, which was only "reported" to SYMANTEC,
2 days after my installs. Perhaps this PC was one of the
few "early buyers" of this virus - timing seems
coincidental.
Thanks
Joe