Author Topic: Can I check why a scan wasn't completed?  (Read 1314 times)

0 Members and 1 Guest are viewing this topic.

Offline MrSomeonesbody

  • Newbie
  • *
  • Posts: 3
Can I check why a scan wasn't completed?
« on: July 11, 2021, 01:36:53 PM »
I made a full scan with Avast, but the next day, when I check scan History, it says the scan did not complete. This has happened thrice now and I can't figure out why.

Here is what I see: https://i.imgur.com/B2rqQEE.png

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 76051
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: Can I check why a scan wasn't completed?
« Reply #1 on: July 11, 2021, 02:35:26 PM »
W8.1 [x64] - Avast Free AV 23.3.8047.BC [UI.757] - Firefox ESR 102.9 [NS/uBO/PB] - Thunderbird 102.9.1
Avast-Tools: Secure Browser 109.0 - Cleanup 23.1 - SecureLine 5.18 - DriverUpdater 23.1 - CCleaner 6.01
Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523.0

Offline MrSomeonesbody

  • Newbie
  • *
  • Posts: 3
Re: Can I check why a scan wasn't completed?
« Reply #2 on: July 11, 2021, 03:47:09 PM »
 So is it nothing to worry about? Additionally, is there a way to check which files could not be checked scanned?

 Thank you for responding!

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 87648
  • No support PMs thanks
Re: Can I check why a scan wasn't completed?
« Reply #3 on: July 11, 2021, 07:28:07 PM »
I don't know if files that couldn't be scanned are reported by default (or just volume) in the scan report file.  However you would have to have enabled the Generate Scan Report. 

If so then the scan report file can be found here C:\ProgramData\AVAST Software\Avast\report the file name should match the name of the scan, see attached image.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 23.4.6062 (build 23.4.8118.762) UI 1.0.762/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline MrSomeonesbody

  • Newbie
  • *
  • Posts: 3
Re: Can I check why a scan wasn't completed?
« Reply #4 on: July 11, 2021, 11:57:40 PM »
 Thank you, turns out the problem was an error 0x0000A47E, which is a decompression bomb. Looking at the files that couldn't be read they mostly seem to be compressed files for modified videogame assets, so probably not a concern. Thank you for your help, I can finally sleep easy.

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 87648
  • No support PMs thanks
Re: Can I check why a scan wasn't completed?
« Reply #5 on: July 12, 2021, 12:20:18 AM »
You're welcome.

Decompression Bomb, a file that is highly compressed(as you found), which could be very large when decompressed. This used to be a tactic long ago to swamp the system. Now with modern computers this isn't so much of an issue

The name really is the most dangerous thing about this and I wish they would change it or simply not report it, a real PITA.

These highly compressed files are generally 'archive' files which are inert, don't present an immediate risk until they are unpacked. If you happen to select 'All packers' in your on-demand scans then you are more likely to come across this type of thing. Personally it is a waste of time scanning 'all packers' and that is why it isn't enabled by default.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 23.4.6062 (build 23.4.8118.762) UI 1.0.762/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security