Avast mistaken for rootkit?

Avast Free Antivirus / Premium Security
1

On Monday when Avast updated, my Malwarebytes picked up 7 files as rootkits shortly after
These files are
C:/WINDOWS/SYSTEM32/DRIVERS/aswsp.sys
C:/WINDOWS/SYSTEM32/DRIVERS/aswMonFlt.sys
C:/WINDOWS/SYSTEM32/DRIVERS/aswHwid.sys
C:/WINDOWS/SYSTEM32/DRIVERS/aswRvrt.sys
C:/WINDOWS/SYSTEM32/DRIVERS/aswRdr2.sys
C:/WINDOWS/SYSTEM32/DRIVERS/aswsnx.sys
C:/WINDOWS/SYSTEM32/DRIVERS/aswstm.sys
I thought these might be Avast files, but I wasn’t 100% sure so I left them in quarantine. Over the past few days, my Avast has started to return a bunch of 1920 errors for file in C:/Windows/Temp. Are the things in Malwarebytes quarantine Avast files which Avast needs to scan fully, and will I be safe if I let them out?

2

They are avast files - Report these to MBAM as false positives.

Since these are drivers they are loaded very early in boot process - I’m none to surprised if avast throws up errors. So I would restore them from the MBAM quarantine.

When where these detected by MBAM on-demand scan or in real-time (on-access) if you have the MBAM Premium version ?

3

You were doing a scan while you were installing, right?

4

Yes, which I won’t do anymore

5

OK, so everything’s safe and I just need to pull them out?
And they were detected by an on-demand scan

6

Yeah thats what causes that… finish/stop all your scans before installing any software. The files are fine.