New
#31
Windows Defender hasn't changed - but Avast has changed significantly at least twice this year.
One of the changes may have caused the problem.
Windows Defender hasn't changed - but Avast has changed significantly at least twice this year.
One of the changes may have caused the problem.
not to beat a dead horse... if thats even a phrase?! :) but it could be either way, I actually tend to lean toward defender being the source of the problem. Only because, you (@NoelDP) had the OP install MSE to disable defender, instead of allowing me to talk through the disable I was in the process of doing, for just such troubleshooting purposes. And defender is basically a subset of the MSE suite, so defender is essentially still installed, albeit in a new package, but no changes were made to Avira, and problem solved.
Mike
It's quite possible that an uninstall/reinstall of Avira/Avast would have cured the problem without manually touching anything. :)
It was NOT my idea for anyone to install MSE - I suggest that you read what I wrote.
I was mistaken, it was not you who suggested it. Although I didn't intend to insinuate you acted out of line, I do appologise for the way my remark sounded NoelDB.:)
We can still disagree on the details, but as we'll not ever know for sure, it is trivial at this point, as I said It could be either way.
Thanks for pointing out my mistake,
Mike
My last update for Avast before the provlems appeared was when I installed it 4 months ago.
When the problems appeared, I thought it might be Avast, so I updated it, and no change happened.
I am positive it was the Defender update, as it was the only change made to my computer between the time frame.
Updating an installation is a very different process than uninstalling and reinstalling it :)
What AV did you have on there prior to Avast? Did you use the manufacturer's removal tool after uninstalling it, and beofre installing Avast?
Norton and McAfee are both renowned for messing up later installs if not completely removed - and both tend to leave a mass of stuff behind unless you run the removal tool.
I had the default Windows one, can't recall whether it was Norton or not.
And the problem persists.
For the first day it worked, and now its back.
I have to run everything as admin to make it work.
So, the plot thickens.
Download and run (with reboots in between!)
1) the Norton Removal Tool https://www-secure.symantec.com/nort...=1&pvid=f-home
2) McAfee MCPR How to uninstall or reinstall supported McAfee consumer products using the McAfee Consumer Products Removal tool (MCPR.exe)
3) teh Avast removal tool avast! Uninstall Utility
reboot again, then open an Elevated Command Prompt window, and run the following command:-
NETSH WINSOCK RESET
- you will be asked to reboot to complete the reset.
once completed, you may need to uninstall and reinstall MSE, and/or repair IE.
How can I find out which Norton I had? As it was the one that came with Windows 7, so likely a trial period of some kind. The only trace I can find of it is Norton Online Backup, but I do remember uninstalling Norton when I got Avast.
Also, I don't think I've ever had this McAfee tool on my computer. Atleast as far as I know.
And as I removed Avast before with the normal tools, I do not have the file available anymore, so I can't actually use the Avast removal tool.
Last edited by Hujoppi; 28 Nov 2011 at 16:52.