Well, looks like this problem is very common, right?
Never had any problems with Avast before. But now, when I tried to install the new client… I can’t start Windows (XP SP2 64-bit) anymore: just got a black screen with a (functional) mouse cursor on it.
Using Avast Free here. My NVIDIA drivers already updated.
When I uninstall Avast (in Windows’ Safe Mode), Windows works properly. Doesn’t look like a disk or Windows problem: it’s Avast.
Also, when I try to install Avast through the online setup, the installer freezes on “Finishing Setup” and never really finishes it. So I had to download the offline installer.
I read somewhere it could be because Avast is blocking explorer (the Windows’ file manager). Is that correct?
Well, I attached FRST.txt - as I can see, people always ask for it.
Fix result of Farbar Recovery Tool (FRST written by Farbar) (x64) Version: 17-08-2014 01
Ran by Administrator at 2014-08-20 10:51:18 Run:2
Running from C:\PHOINX\PROGRAMAS\Limpeza\Avast\Farbar Recovery Scan Tool
Boot Mode: Normal
==============================================
Content of fixlist:
*****************
HKLM-x32\...\Winlogon: [Userinit] userinit [X]
HKLM\...\Command Processor: <======= ATTENTION
HKLM-x32\...\Command Processor: <======= ATTENTION
CHR HKLM-x32\...\Chrome\Extension: [ihflimipbcaljfnojhhknppphnnciiif] - C:\Program Files (x86)\facemoods.com\facemoods\1.4.17.11\facemoods.crx [2011-09-05]
EmptyTemp:
CMD: bitsadmin /reset /allusers
*****************
HKLM\Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Winlogon\\Userinit => Value was restored successfully.
HKLM\Software\Microsoft\Command Processor\\AutoRun => value deleted successfully.
HKLM\Software\Wow6432Node\Microsoft\Command Processor\\AutoRun => value deleted successfully.
"HKLM\SOFTWARE\Wow6432Node\Google\Chrome\Extensions\ihflimipbcaljfnojhhknppphnnciiif" => Key deleted successfully.
C:\Program Files (x86)\facemoods.com\facemoods\1.4.17.11\facemoods.crx => Moved successfully.
========= bitsadmin /reset /allusers =========
'bitsadmin' is not recognized as an internal or external command,
operable program or batch file.
========= End of CMD: =========
EmptyTemp: => Removed 632.8 MB temporary data.
The system needed a reboot.
==== End of Fixlog ====
But… Should I do this with Avast installed? If that’s the case, could only do that while in Safe Mode.
What I did was uninstall Avast, then FRST Fix and after that installed Avast again - and the problem continues.
It appears that there are some unidentified problems with some XP64 bit, but as it is not all then it is proving difficult to track down the problem. As of yet I have been unable to find a solution
But I will keep looking
Could it be related to a previous installation of another anti-virus I did before?
I installed Kaspersky to give some orientation to a friend using it. But after that I uninstalled it - and used the specific removal tool and CCleaner to clear it all.