K
Ken Cook
Working on a client's WinXP Pro system (with an illegal key
so MSAS couldn't validate), MSAS would run its scan until
it hit
HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\WinTools
and then (watching the Performance graph in Task Manager)
it would slowly grind to a halt. The system did one add of
memory, which got eaten instantly. Got a nice screen snap
of the parabolic arch of the chart.
No way of stopping the scan and cleaning up what had been
identified (as one can do with Spybot or Ad-Aware). With it
being scheduled automatically at 2am, it means that every
morning the client needs to reboot the system.
I've tried Ad-Aware (the new 1.06 version) and Spybot. I've
cleaned up the HJT log and tried going into the Registry in
both normal and safe modes to clear this registry entry
without success. [70 elements in Ad-Aware, 35 in Spybot
(eliminating cookies) and the Hosts file had been
"adjusted".] CWShredder took out one element & fixed Hosts.
System has 5 profiles.
so MSAS couldn't validate), MSAS would run its scan until
it hit
HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\WinTools
and then (watching the Performance graph in Task Manager)
it would slowly grind to a halt. The system did one add of
memory, which got eaten instantly. Got a nice screen snap
of the parabolic arch of the chart.
No way of stopping the scan and cleaning up what had been
identified (as one can do with Spybot or Ad-Aware). With it
being scheduled automatically at 2am, it means that every
morning the client needs to reboot the system.
I've tried Ad-Aware (the new 1.06 version) and Spybot. I've
cleaned up the HJT log and tried going into the Registry in
both normal and safe modes to clear this registry entry
without success. [70 elements in Ad-Aware, 35 in Spybot
(eliminating cookies) and the Hosts file had been
"adjusted".] CWShredder took out one element & fixed Hosts.
System has 5 profiles.