on-access scanner (resident protection) not enabled

I’ve just installed avast av and zone alarm firewall (having uninstalled my previous programs) and the blue ball icon has the little red ‘no entry’ sign on it and says ‘avast! On-Access Scanner: 6 provider(s) total, 0 running’. When I right click on ‘Start on-access protection’ nothing happens. When I right click on ‘start avast antivirus’ it says resident protection disabled - but when I try to change it nothing happens.

If anyone can help or suggest what I can do I’d be v grateful.
Many thanks
Heather


Welcome to the forums, Scoobs. :slight_smile:

Please tell us what OS and what the previous av was … as well as how you uninstalled it.


Thanks Charley.
Previous AV/firewall was Symantec (Norton Security/Antivirus) and I uninstalled it using the uninstall prog on control panel.
My PC is Win98 (yeah I know it’s archaic!)
I’ve also tried going into the ‘on-access protection control’ and clicking ‘start’ and it says ‘you’re trying to change the settings - are you sure’ blah blah…when I click ‘yes’ it won’t accept.
Any help gratefully received!
Thanks

After that you must use the Symantec tool for full removal of any file and registry key left behind after the uninstallation…
If you search the Symantec site you’ll find it.

A link worth looking at, which is a program removal tool that can remove the remnants of a number of different Norton Programs:
Removing your Norton program using SymNRT

Thanks.

I’ve now used the Norton unistall tool recommended above and have rebooted but the problem still seems to be the same.

When I go into ‘on-access protection control’ and press ‘start’ to try to activate the resident protection modules, it says ‘the requested resident task could not be found - the operation could not be completed’.

Any other ideas?
TIA
Scoobs

Now that you have rid yourself of the remnants it may be necessary to uninstall avast, reboot, install and reboot. This should rectify any issues caused by the presence of the remnants, avast if it detects the presence of another AV won’t fully install to avoid any potential conflict.

I have exactly the same problem… Running on Win 98SE with Zone Alarm v.6

Never used Norton Antivirus, but had KAV. Uninstalled Kaspersky, cleaned up the registry and files.

Uninstalled avast, rebooted, installed again, rebooted. But resident protection still wouldn’t enable!

But, is ashserv.exe running in background?
Are the avast services running?
I had a similar problem some weeks ago… I had two or three on-demmand scanners and only starting a clean Windows installation, I could not manage to make the residents on.
There is a standalone uninstaller for Kaspersky if I`m remembering right… Did you find it into its webpage?

I see Ashmaisv and Aswebsv, but not ashserv

I run this uninstaller: downloads1.kaspersky-labs.com/utils/klremover/KAV_Registry_Clean.zip
and also did some manual cleaning. Don’t think there is anything left from KAV now…

Could it be Zone Alarm or something missing in Win98?

Some updates:

I uninstalled Avast once again, with the “avast! uninstall utility”. Then rebooted, installed Avast and rebooted again.

It worked for a while after this install, but then stopped after the second reboot. All I did was some customizations to the “providers”.

Either avast doesn’t like my machine or there’s something really wrong… ???

ashserv.exe is the standard shield resident provider… it is ‘the’ antivirus heart… it should be running.
Besides KAV, did you use any other antivirus in the past? Are you using other security programs and specially WinPatrol, PrevX, ProcessGuard, etc.?

I guess it is running, since I see it in the tray…

Besides KAV, did you use any other antivirus in the past? Are you using other security programs and specially WinPatrol, PrevX, ProcessGuard, etc.?
Nope, I didn't use any antivirus except KAV since my last windows install. But I'm also using Spybot's Search & Destroy, a spyware remover.

The tray icon is ashDisp.exe and not ashServ.exe, check task manager to see if it is running.

Do (or did) you use Kaspersky’s anti-hacker tool (or any other Kaspersky products) as this uses the same process names as KAV and could be seen by avast as KAV and not the anti-hacker tool and disable some of the avast processes ?

Same here after removing etrust antivirus. Resident scanner won’t start until I try a manual update. Otherwise after reboot no protection. ECAR virus fails.

Check out the etrust site and see if there is a manual removal tool or instructions to ensure all remnants including registry entries are gone. Once you have done that reboot and see if that resolves the problem, if not uninstall, reboot, install, reboot.

It would probably be best to download the latest version of avast and save it to your HDD, somewhere you can find it again. Use that when you reinstall.

  1. Uninstall avast from Control Panel first.
  2. Boot
  3. Use Avast Uninstall for complete uninstallation (read http://www.avast.com/eng/avast_uninstall_util.html)
  4. Boot
  5. Install again and see if this way you get a clean installation.

Right, ashServ.exe isn’t running

Do (or did) you use Kaspersky's anti-hacker tool (or any other Kaspersky products) as this uses the same process names as KAV and could be seen by avast as KAV and not the anti-hacker tool and disable some of the avast processes ?

I didn’t use any security products that I remember after last windows install (to a clean HDD), except Kaspersky antivirus, Spybot S&D, Avira’s Antivir and PandaSoftware’s online ActiveScan. AntiVir uninstalled quite nicely, nothing in the registry.

Except?
Maybe any Kaspersky or Antivir or Panda antivirus left files/registry key behind… ::slight_smile:

I can’t see anything that might cause avast not to start, as you say you have used the KAV removal tool and antivir has gone from the registry. Spybot S&D has TeaTimer resident protection (Tools) but this if active would normally only effect the avast icon.

Also useful as a diagnostic tool - Download HiJackThis.zip - HJT Information HiJackThis Tutorial 1 or HiJackThis Tutorial 2

Post the contents of the log file here and perhaps it will show something running or in registry that could be the problem.