i already reinstall it a couple it times but the boot scan still would not work, my avast is updated always both VPS and Program update, so any suggestions…please…
What OS do you have?
Boot Scan is only for 2k/XP
do i make AVAST do a boot scan or see it run a scan when booting up plz,
win98se with 650 mhz,256 ram dsl pro package,
thanks for the info, “AA”
As MacLover2000 said. Bootscan is only for 2K/XP, not for 98(se).
There is a way you can run avast before windows loads.
Install Avast for dos and change the autoexec.bat so that it will run Avast for dos before windows loads.
I am running Windows XP with the Home version of AV and, although I have sceduled a boot time scan and it reports that a scan in scheduled, it will not run when I reboot. I have tried clearing and rescheduling the boot time scan with no luck. Any ideas?
Click on the Menu button.
Choose Schedule Boot Time Scan.
Doing so displays a dialog allowing you to schedule virus scanning.
Check Archives, if you want scan all the archives.
Specify whether all the disks or just a specific folder should be scanned.
Select Advanced options for scheduling details.
Select how to automatically process infected files.
Choose how to automatically process infected system files.
Click the Schedule button to confirm the settings.
Are you doing this? If not, try it.
Also check the Avast log file as well as the event log and the system log for errors.
The boot takes about the same time as it does when you don’t schedule the scan?
In any case - schedule the scan, reboot and when you’re back in Windows, check the file \Data\log\aswBoot.log. Is it there? If yes, attach/post it here, please.
I unscheduled the boot scan I aready had set up and followed your instructions exactly to create a new one. I rebooted and the system seemed to start up as normal. I checked the scheduled scan and it still shows as being scheduled.
Checked for the aswBoot.log file and it did not exist. I did find this entry from yesterday in the error.log file:
7/28/2004 12:34:33 AM 1090992873 NT AUTHORITY\SYSTEM 1992 AAVM - scanning error: x_AavmCheckBootDirectEx: avscanScanReal of *BOOTA failed, 00000022.
Not sure if this is related. It appears that no entry was made with today’s reboot. I am using Windows XP Professional with SP1.
I think it’s not related - the log record is about scanning BOOT record of floppy A:
How did you check that the boot-time scan was still scheduled after restart - tried to schedule it again?
Please, open regedit and check the value BootExecute in the key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Normally (when nothing is scheduled), only the following line should be there:
autocheck autochk *
When avast! boot-time scanner is scheduled, a reference to aswBoot.exe should appear there.
Is there anything else inside? Is the path to aswBoot.exe short or long?
Can you dump the content of the key to a file and post it here? (note that if you export the key, a big amount of data will be saved - the whole Session Manager key; the only interesting part here is the BootExecute value).
Here is what mine says:
autocheck autochk *
C:\PROGRA~1\Alwil Software\Avast4\aswBoot.exe /A:“*” /L:“English” /archives
Not sure what it means. 
I noticed that the path is long but not in quotes. This is how, what I would consider a simple scan, was written to the registry.
Do you have the latest build of avast? (4.1.418)
Yes, that is the build I have dated June 2004.
I think this version logs the exact hex dump of the registry key to
\data\log\aswBoot.log, right Igor?
It may be worth trying to send this file to Igor’s e-mail address for further inspection. Version 418 of avast should actually contain some means of preventing of the behavior you were describing.
Thanks
Vlk
Would be glad to send it but like I said earlier, it does not exist on my PC.
I thought that I found the problem when I noticed that NAV had not totally cleaned itself up. I went through the registry and got rid of the NAV and Symantec keys but I still have the problem.
Vlk, I can’t schedule a boot scan into XP :‘(
Should I send the file aswBoot.log to Igor? :’(
I believe the problem is not with the key - but in the fact that there is a long path there; it should be short. However, I checked the code and wherever the scheduling is called from, the GetShortPathName() call is prepended… I really don’t understand.
What happens when you unschedule and schedule the scan again? The long key is created again?
Technical: what exactly does it mean “you can’t schedule”?
I’m sure I schedule a boot scan but nothing happens… 
I’ll try again and post the results.
OK, one more thing: please, open regedit and navigate to
HKEY_LOCAL_ MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
What is the value of NtfsDisable8dot3NameCreation in the right part of the window?
Mine is set at Hex 1.
Hm, that’s the problem then.
The “short file names” are disabled on your system; however, the boot-time scanner needs them, because it simply doesn’t start with a long one.
We may try to do something about it (such as installing the scanner into the system folder, instead of the avast! installation folder) - but right now, I’m afraid it won’t work for you (unless you enable the short file names again).