First bug : The boot-time scan ignores the exclusions set in the settings, ie it scans even excluded folders.

That’s a feature. It’s not only exclusions, it’s also the alerts etc. – in short, the global avast settings are not taken into account by the boot-time scan. This behavior is by design… :wink: :stuck_out_tongue:

Second bug : The boot-time scan sort of corrupt the PAGEFILE.SYS (the swap file). When windows boot after a scan it says something like "swap file corrupted, a temporary swap file have been created". I have the swap file on the second HDD (not in C: where Windows is installed).

Hmm, unless there’s a virus avast opens all files in read-only mode so I quite don’t know how it could damage the file…

Does this happen every time you run the scan?