Hi, this is my first post because I have never really had any problems with avast! until recently.
I was experiencing a conflict between avast! and Outpost Firewall Pro which I finally tracked down to avast!'s Network Shield, which I disabled in Device Manager.
Today I decided to try a free 6-month trial of Kaspersky Internet Security (just the anti-virus part), which I got from a computer magazine, to see if that would run without any conflicts. What a NIGHTMARE! I had the following problems with it:
It almost brought my PC to a complete standstill
It exhibited the exact same conflict with Outpost that avast! did
Norton Protection Center didn’t recognise it
I had about 7 or 8 blue screens of death in around 3 hours!
So I have realised the error of my ways and I’m going back to avast! - well trying to anyway…
I uninstalled Kaspersky (after much cursing and swearing) and tried to reinstall avast! (version 4.7.942). However it kept telling me there was a problem installing it and the error log mentioned errors with DLLs (such as 0x0000020 or similar). I downloaded 4.7.986 but that had the same problem.
I downloaded clean uninstall utilities from both avast! and Kaspersky but still couldn’t get avast! to install. I did eventually get it to install in Safe Mode, but I still can’t get on-access protection to start up
The avast! Antivirus service in Services is set to Automatic but when I try to start it up manually, ashServ.exe crashes as below:
This will conflict with both avast and Kaspersky… I think…
Conflicts…
There are some tools to get rid from Kaspersky (you can search their website or even avast forum and you’ll find them). Use to uninstall Kaspersky completely and then install avast… If you need to be at Safe Mode to install avast it won’t work when you boot in normal way…
If you have avast working at that time, I’m sure that David - which use avast and Outpost Pro - will help you to manage NetShield (that is compatible with other firewalls).
I was involved in a long Topic in the outpostfirewall.com forum about this very thing and I couldn’t understand whyit was happening when I have the network shield enabled and none of the problems Steven experienced.
Just to let you all know that I formatted my C: drive in the end to remove all traces of Kaspersky(!) and restored from a mid-week backup so I’m back up and running now ;D
I’m just wondering whether I should update to 4.7.986 (as I’m back on 4.7.942 now) - a few people seem to be experiencing slowdowns in Windows load time after installing it by the sounds of things?
There will be a new option to troubleshoot this eventual problem, if it occurs.
By the way, Igor, when it will be available?
Note that, in a lot of cases, the slowdown is made by Windows services (majority, Windows Update scanning & detecting missing updates) and not an avast issue itself.
Well you almost answer your own question when you say “a few people seem to be experiencing slowdowns in Windows load time” against the huge numbers that aren’t experiencing any slowdown. I would say it is strongly weighted in favour of updating.
As Tech said in the Program Settings, Trouble shooting, option should this be a problem.
I remember that being there on 4.7.981 I believe (I can’t recall if it was that way on 4.7.942 as oldman mentions), unless the terminology has changed not wanting to scare the natives talking about kernel-mode scanning.
But, if you have 4,7,986 as I have it should be their, perhaps a repair and manual update check ?
I’ve updated (I think) but after rebooting I get an error from ashDisp.exe - Entry Point Not Found. Can someone tell me how to attach it to the forum so I can post it please?
Hmm, how strange. I did a Repair from the Setup program and after rebooting it seems to be working OK now!
I did notice when I updated that there was a message - something about not being able to update some files as they were in use. If it’s any help I did the update from the Update (Basic) settings page. When I updated my laptop earlier I used the ‘Updating’ option from the system tray icon and that didn’t cause the problem…