Boot time scan skips

Avast Free Antivirus / Premium Security
1

I had been having trouble getting the Windows disk degragment utility to work (it would analyze, start defragmenting at 0%, then quickly skip to 100% and close) and wondered if it was malware. So I scheduled a boot time scan, and oddly enough it did the same thing as the defragment utility: Computer restarted, the boot time scan started at 0%, then after a few seconds it just quit and started up windows. I decided to go ahead and reformat, but even with a fresh windows install I’m having the same problems. Degfrag doesn’t work, boot time scan doesn’t work.

I’m running Windows 7 with bootcamp on a Macbook, almost never use my mac partition.

I searched the forums, but all of the fixes to the problem were computer specific and I didn’t see anything where the user was running bootcamp. Where do I start? Thanks

2

I recommend going to the apple page for solving this problem defragmentation

http://www.apple.com/support/bootcamp/

3

Please post the file c:\ProgramData\AVAST Software\Avast\log\aswBoot.log (after the problem has reproduced).
Thanks.

4

Could not find a .log for aswBoot

Before running a new scan I made a copy of the first aswBoot.txt file, which was the most recent from the failure I had earlier today. It is named “Copy of 3rd scan log.txt”. I also ran the boot scan again, this time it seems to have worked. The file is attached as “aswBoot.txt”

When I look at the logs under Avast’s interface, the former scan details say Run time, Tested files, Tested folders, Amount of data tested, and infected files all as 0. The second scan gives a Run time of 0:38:19, Tested files at 218434, etc. and no infected files

Why would it fail repeatedly but scan fine now?

EDIT:
I guess both files were logs to begin with. The renamed file shows as .txt, and on this forum the newer aswBoot file says .log. Please forgive my ignorance of file types

5

Honestly, I don’t know…
The log shows that the second scan finished correctly - and the previous one interrupted without any log entry in the middle of a scan (where “in the middle” may mean during the scanning of the first file, it’s impossible to say - but everything was set up correctly, the function to start the scanning has been called, and then the logs ends; no information about any crash, no information about the scanning function having finished… nothing. The process has simply terminated (or was terminated)).
Also I’m not aware of any changes in the yesterdays virus definitions that could change the behavior.
So… I’m afraid that’s a mystery :frowning: