Avast giving error 42110 when scanning itself?

Avast Free Antivirus / Premium Security
1

Whenever I run a scan avast will always tell me some files couldn’t be scanned, with error 42110 (some files for a game)

Two days ago, I checked the log for full virus scan and found more files from that game (same error, 42110) as well as two errors regarding avast files. They were never there before:

C:\Program Files\Avast Software\Avast\defs\23010404\aswEnjin.dll|>a [E] Error 0x0000A47E (42110)
C:\Program Files\Avast Software\Avast\defs\23010404\aswEnjin.dll|>a [E] Error 0x0000A47E (42110)

The same line repeated twice, and there was only one aswEnjin.dll in the path specified. I scanned the C drive with targeted scan, and no errors were found. Same for scanning just the Avast folder, as well as the aswEnjin.dll itself, no errors

The next day, I did a full virus scan again and the usual errors popped up (normal) but the avast ones this time were

C:\Program Files\Avast Software\Avast\defs\23010506\aswEnjin.dll|>a [E] Error 0x0000A47E (42110)
C:\Program Files\Avast Software\Avast\defs\23010506\aswEnjin.dll|>a [E] Error 0x0000A47E (42110)

I’m aware error 42110 is a decompression bomb, which is relatively harmless, but it’s curious that avast is detecting this about itself. Any insights?

PC is running Windows 11 Home, Avast Free 22.12.6044 build 22.12.7758.769

2

See if this answers your question about files that can’t be scanned:
https://blog.avast.com/2014/02/28/how-do-i-handle-files-that-avast-cant-scan/

3

Basically it’s a “false archive detection” - the unpacker detects “something like an archive” inside the file (but it’s not an actual archive so the subsequent attempt to unpack it produces the weird error).

4

That’s reassuring, probably nothing to worry about then.

Thanks for the replies!