I recently helped out a senior friend (mid 70’s) who’s avast had become corrupted and wouldn’t open - no response at all
I attempted the repair option, Restarted PC, but it still failed to open.
I uninstalled it and removed any avast folders on C: drive
Restarted PC
Installed version 7.0.1474, registered it and ran a boot scan - no problem.
A few days later she called to say that it hadn’t updated (“the lady isnt green, she is maroon”)
My friend is able to browse websites and has never used any other security software on this machine.
Up until recently she had reported no issues with avast whatsoever.
Machine Specs:
Dell Laptop
Core 2 Duo 2Ghz, 2GB RAM, 250GB HDD
Avast Free v 7.0.1474
Win7 x86 SP1 updated
I suspected a firewall issue - but checked my PC and there is no exception here for avast so I assumed it didn’t need one?
Did I correctly remove the last version - Is there an Avast removal tool?
it is important that any previous used or preinstalled AV is removed before installing avast
Dell computers used to come with a preinstalled Norton…and the laste yearsit as been McAfee
if so it must be uninstalled, and then run the removal tool to clear any leftover files that may conflict
tools found here. http://singularlabs.com/uninstallers/security-software/
I know there was no other AV software because I personally did a clean install of Windows 7 for her.
As suggested, I used the Avast uninstall utility and re-installed/re-registered a freshly downloaded AVAST free version.
Still no luck … I was considering switching her to AVG (Can I even say that word here?) - but was out of time on the day and had to leave.
My friend called the next day to say that Java had requested she update, so we went through with the Java update then and there.
She called again later to say that the “Green Lady” was back and was very pleased. ( I too was pleased about the “Green Lady” - lol)
Some info that may/may not be useful:
From memory, when I installed Win7 her initial Java was ~v6.5 and I’m pretty sure she wouldn’t attempt an update herself.
So it would appear that updating Java fixed the issue.