Avast WEBforum
Other => General Topics => Topic started by: Avalben on December 14, 2008, 12:24:02 AM
-
Dear Avast friends,
I have installed the free version of Avast on my Flybook but have inadvertently interrupted the first sytem scan soon after intallation! :-[ Now on restarting the Flybook it appears to be blocked soon after the bios rooutines are run. What am I to do to restablisk the correct functioning of my Flybook?
Luigi Benelli
Florence
Italy
-
Well avast doesn't block, but scans and alerts to infection.
So are you saying avast detects this as infected ?
-
Well avast doesn't block, but scans and alerts to infection.
So are you saying avast detects this as infected ?
No, it is not that! Fact is that soon after installation Avast (as a lot of other products) needs a system restart and at the restart it launches automatically the first complete system scan: well I have inadvertently interrupted the run of this scan fisrt system scan and switched off my Flybook. Well on switching my Flybook on again it appears to stop soon after the initial memory test during bios execution as if the MBR had been altered and could not now launch the regular windows xp execution.
Regards
Luigi
-
Well the boot-time scan after installation and reboot, before windows starts should only run once (unless you schedule it again). You can interrupt/stop it using the Esc key, but even switching off your flybook shouldn't have any impact and as far as I'm aware avast doesn't alter the MBR under any circumstances.
Have (or did) you another AV installed in this system, if so what was it and how did you get rid of it ?
This could cause conflict between the old and new and that conflict could have a symptom like this.