Nobody cares about such a serious problem??
I have got the same issue with last Avast free and Rescue Disk created several days ago.
After the scan finishes AvastPE shows me:
Firstly, there is an open Notepad file with
This file is just temporary ...
...
Scan begin: ...
[b]Infected files: 130[/b]
Scanner result: 0
Scan end: ...
then Avast opens another window with this content:
Scanned files: xyz
[b]Infected files: 0 [/b]
Size of Scanned files: xyz
Fix automatically or do it manually
So accordingly to Avast PE, the number of infected files is 0 and 130 simultaneously
I chose to “fix manually” and I had got a table with approx. 130 files (a note: the column “virus name” was blank for all files). Later in Windows, i tried to rescan some of these files from the context menu, and I got no malware but files that “could not be scanned”:
error: archive is password protected
error: the file is a decompression bomb (this happened with “memory-report.json.gz” from a Firefox profile)
I used this thread to report a bug, so I will use it to file a feature request:
the report in the notepad is a useful feature, because it allows users to save the report
but another report in the notepad is missing after the fixing procedures
That Avast can not scan password protected files is normal. Otherwise the password protection wouldn’t make sense.
About the Rescue Disk ( and its actions ) : It’s a very long time ago I have tried/used is myself, so I have to look at it first.
@Pondus
Here are the photos.
By the way, this little test wrought havoc in my Windows 10 (UEFI SecureBoot) installation.
I had to re-install Windows after that.
In fact, Avast Rescue deleted thousands of Windows files after I clicked the right scrollbar in order to scroll the “Fix it manually” window, as you can see in pictures n.3 and 4 (in my next post).
I see this as a serious issue.
I would recommend Avast removes “Rescue Disk” from the Avast suite until it is fixed.
@Milos
I can’t send the detected files because Avast Rescue deleted them, like I said.
Anyways, they were thousands of files in the c:\Windows folder.
I was testing the “Rescue Disk” (actually a pendrive) on a malware-free system (according to Avast IS and other scanners). It was a perfectly functioning system, before Avast Rescue broke it.
Regardless of what files they were and why Avast detected them, Avast Rescue gave incorrect and contradictory information (51,000 infected files… then 0 infected files!, then again they were listed in the “Fix it manually” window) and deleted those files without user request (I just clicked the scroll-bar, not the Delete button! you can even see where the cursor was in my photo #3).
I also tested Avast Rescue on another PC, an old notebook with Windows Vista: no problem there.
Maybe Avast Rescue has issues on systems with UEFI SecureBoot?
I don’t think you need to analyze files.
In order to recreate the bug, have passworded packed files in the scanned system (see my previous posts for details)
It seems unlikely that UEFI would cause the issue. The issue happened to me on two different computers with BIOS. edit: one computer was with Windows XP, another one with Windows 7.
Anyways, I noticed the first two file names in the list (as in my screenshot #3: AcGenral.dll and AcLayers.dll in C:\Windows\AppPatch). I retrieved those two files from a recent backup of mine (a few days before the Rescue disk test) and compared them with the same files in my brand new Windows 10 installation (reinstalled after Rescue disk destroyed Windows). Same hashes, they are the same files exactly.
I guess am going to send those two files in case it helps, even though they are the same files that can be found in any Windows10 Home 64-bit installation: AcGenral.dll v.10.10240.16384 and AcLayers.dll v.10.10240.16425.
.