Boot-time scan stops before 100% done

Avast Free Antivirus / Premium Security
1

Hi,

I ran a full system disk scan at boot time.
It completed %100 of the first disk.
At about 44% of the scan on my 2nd disk avast said it was complete and processed to continue to Windows boot.

Either it did perform a complete scan of my 2nd disk and the % is wrong
or
it did not perform a complete scan.

What could it be?

Thanks
JM

2

Outside of windows I don’t know how accurate this percentage is likely to be, it may be able to get a count of total files and try and base its percentage on the number of files scanned against total files. The possibly problem is not all files are scanned on your HDD so there will be a percentage that wil be skipped this could account for the closure when you don’t see 100& displayed.

Did your first drive have any large jump from xx% to 100% as that too could be the same. There is a file that you can check as that contains the stats of a boot-time scan and if it didn’t complete that too I would guess wouldn’t be written to. I think it is C:\Program Files\Alwil Software\Avast4\DATA\log\aswboot.txt.

3

Hi David,

I did check the aswBoot.txt file (below).

Bizarre though: out of the 2 disks scannded (X: and C:) it does report the scan for the C: drive.
However there are no reports for the X: for which I know it did perform a full scan.

Both C: and X: are internal HDD system disks.

Based on the # of files tested for C: it does appear complete.
However my current # files have changed since I had performed the scan so I cannot confirm it did a full scan.

JM

07/29/2008 16:07
Scan of all local drives

File C:\System Volume Information_restore{0902FB74-F249-43E2-8915-2D110685BE0E}\RP15\A0008306.dll is infected by Win32:Trojan-gen {Other}, Deleted
File C:\System Volume Information_restore{0902FB74-F249-43E2-8915-2D110685BE0E}\RP15\A0008864.dll is infected by Win32:Trojan-gen {Other}, Deleted
Number of searched folders: 26770
Number of tested files: 229214
Number of infected files: 2

4

I’d say it’s possible that there are some special (e.g. huge) files at the “end” of the scan - which are processed quickly (faster than expected), thus causing the percentage to jump significantly.
It’s hard to say more without seing the corresponding drives, but in general I wouldn’t be worried about it, if the scan finished successfully (i.e. if you see the final statistics displayed).

If you wish, you can attach the file \Data\Log\aswBoot.log here and I can check if there’s anything suspicous inside.

5

I see you managed to find the aswBoot.txt, I inadvertently gave the \log\ folder as the location where aswBoot.log lives not \Report\ folder, but everything appears fine as covered by Igor.