The title say most of my problem I have tried running it in windows safe mode (windows 10) this instead gives me a screen that says it has 0 files to scan says it’s complete and loads me into windows safe mode. Any help would be nice thank you for reading this <3
You shouldn’t have to do anything special like boot into safe mode, that is all handled in the Boot-Time scan settings, attached image.
Did it download them ?
If not that could be a possible reason for an aborted scan, but less likely.
The boot time scan should handle things all you need to do is select click the ‘Run on next Boot’ button and then just restart the system (see attached image).
If The scan started did you get anything displayed to the screen ?
I am having the same issue on two of my windows 10 pc’s. You set it to boot time scan and then reboot the computer. It looks like its going to start the scan and then it stops within a few seconds and boots to the windows splash screen without doing the scan. It shows on the history of scans that the run time is “seconds” instead of the two hours that it normally would take.
Yes i did all of the things you said and when it tried to scan it did not even get past the first file before it went to the windows login screen
I’m having the same issue I have tried a number of ways to get this working from reinstalling avast to even using the command prompt tool but I get the same it just looks like its about to start the kicks me straight to the windows log in screen. When I check the reports it is saying that 0 files where scanned. Could it have something to do with the latest update?? Any information or help would be greatly appreciated.
OK, I have tried to draw Avast attention to this topic.
Thank you very much <3
You’re welcome.
Hopefully it will come soon, it is a very, very long time since I ran a boot-time scan and they used to be pretty bullet proof.
Having the same problem. After reading that it might be a bug in the recent update, I reloaded 20.7 and boot-scan works like it used to.
This has been picked up by Avast, but Igor told us it will take at least a few days to fix it.
Greetz, Red.
We’ve recently found a problem that may cause the described symptoms. The issue is fixed in the latest virus definitions (201006-2) in beta versions of Avast.
If no problems appear, the production version will get this fix in a few days (again, via virus definitions).
Even though I’m not 100% sure if the problem is the same, I’m rather sure the problem here has nothing to do with a particular version of Avast - because almost all the code of the boot-time scanner resides in virus definitions. So there’s no point in downgrading to Avast 20.7 (for example) - it won’t help. (Yes, if you install it from an offline installer, you might get some old virus definitions which may not contain the problem - but as soon as the definitions get updated, it won’t matter if it’s 20.7, 20.8 or other).
If the problem persist even in the future (say next week), uploading the file “C:\ProgramData\AVAST Software\Avast\log\aswBoot.log” may give us some clues.
Thanks.
Thanks for the clarification Igor.
I’m having the same exact issue, I schedule a boot time scan, reboot the pc, boot time scan appears to start and the within seconds it goes to windows splash screen, highly frustrating. I’ve tried updating avast and repairing it, no luck. Is it a bug with the newest update? Hoping avast fixes this!
See Reply #10 from Igor.
My boot time scan will not run. It gets to start scan then the Windows Boot Up takes over and there is no scan. Tried several times to make it work but to no avail. Please help.
Check reply number 10.
Avast Team,
My Process:
Did a 100% Un-Install and Re-Install of Avast Free
Set the boot time scan to run on next reboot
Downloaded the extra Virus Definitions
Reboot and results in a failure see below and full attachment…
This is what I see in my log as attached, but this is what the tail of the Log looks like:
avfilesScanAdd *RAW:C: [Fs: 03e706ff, NTFS; Dev: 07, 00020020]
avfilesScanAdd *STARTUP
avfilesScanRealMulti begin
What I see when it drops the boot scan is the word: *STARTUP
The scan drops and windows starts up normally.
Could the “Downloaded the extra Virus Definitions” be the killer?
Thanks
Ken
PS,
i5-4670
16Gb Ram
Microsoft Windows 10 Pro (64-bit)
Ver: 20H2
Build 19042.546
WFP: 120.2212.31.0
Update:
Hi,
The devs are aware and working on this.
The expected fix time should be next week.
Please accept our apologies for any inconvenience caused.
I also had the same issue on my computers, but thanks for working on a fix.
It´s working again. Thank you.