Boot scanner get`s stuck.

Hi

Boot scanner get`s stuck at 41% and shows:

c/System…1-4 EFG6-AF80-AF25F3CO68DD}\RP44\ACO13922.EXE

I have to forcibly reboot to restart. Any help will be appreciated.

Thanks

Problem solved:
The previously mentioned item the scanner got stuck on ,was related to the system restore.
Deactivated Sys.restore and reactivated , scanned again with boot scanner and it came out clean. :wink:

Glad to hear you solved your problem :slight_smile:

Just one thing though, how come you haven’t updated to SP3 yet, it has been available for over a year now and contains several security updates. Not updating it leaves you vulnerable to attack.

-Scott-

Just being lazy about xp3 updating. One more question: Why does the Boot scanner get stuck and no pop up or some sort of announcement from Avast?
Thanks

You really should update it soon, maybe have a look at What to do about SP2

as for the boot scan question, thats one for the more experienced users here, my knowledge of it extends only to scheduling one :wink: sorry.

-Scott-

Thanks for your reply, I guess I didnt bother to up date because: I always run sandboxed(virtual environment)+Spyware terminator+Avast+Superantispy +Spywareblaster ,and this brought me to think that Im more than sufficiently protected and thus,did not need the sp3 and the constant disk space consumed by the updates.
As for my previous question,is it possible to address the question to someone in your team that could answer?

Thanks

You already have :wink:

We are all just avast users like yourself. (with the Alwil staff dropping in occasionally)
When someone who has the answer (alwil or not) is online, they will try to answer your question.

I suppose all of us are a team of sorts :slight_smile:

-Scott-

The one thing missing from your signature is what firewall you use ? I know ZA can have some issues hanging a normal on-demand scan as it has some hook into the system volume information folder (part of the system restore function). Now I don’t know if a) you use ZA or b) if it would still be monitoring access to that tracking.log file in the system volume information folder.

I use Online Armour firewall.