K
Keith
I identified and located a hijacking BHO using the BHO
System Explorer. I would then highlight the BHO and would
click on "permanently remove this BHO". But when I would
run another report the BHO would still be there. This
happened even if I re-booted before running the next
report. I had to go to another site to get assistance in
removing this BHO. Seems that MS needs to build into Anti-
Spyware a process suspender/killer to stop these hijacking
BHO's so they can be fixed. Just my opinion.
Here were the offending entries.
O2 - BHO: MSEvents Object - {827DC836-DD9F-4A68-A602-
5812EB50A834} - C:\WINDOWS\system32\awvtq.dll
O20 - Winlogon Notify: awvtq - C:\WINDOWS\system32
\awvtq.dll
System Explorer. I would then highlight the BHO and would
click on "permanently remove this BHO". But when I would
run another report the BHO would still be there. This
happened even if I re-booted before running the next
report. I had to go to another site to get assistance in
removing this BHO. Seems that MS needs to build into Anti-
Spyware a process suspender/killer to stop these hijacking
BHO's so they can be fixed. Just my opinion.
Here were the offending entries.
O2 - BHO: MSEvents Object - {827DC836-DD9F-4A68-A602-
5812EB50A834} - C:\WINDOWS\system32\awvtq.dll
O20 - Winlogon Notify: awvtq - C:\WINDOWS\system32
\awvtq.dll