I ran an automated eraserl bat file overnight, and this morning the Eraser results screen said that Eraser had failed to remove a temporary directory from C:, which is the first time I've had that message from Eraser. Also I had a "Critical" Prevx warning screen saying that Prevx had jailed a file named mqad.dll that it found in the C:\~ERAFSWD.TMP folder, saying that C:\~ERAFSWD.TMP\mqad.dll was "the subject of the following behavior:
- Created as a process on disk"
C:\~ERAFSWD.TMP also contained these other files:
autodisc.dll
diantz.exe
findstr.exe
localui.dll
mqad.dll
share.exe
It was definitely a cause for concern to find that Prevx jailed a file in a directory that I've never seen before, and that the directory also contains serveral other ominously named .exe's and .dll's.
Are these files supposed to be in this directory? What could make Prevx think that something attempted to create mqad.dll as a process? What might Eraserl do that would cause Prevx to react to a file in that dir as malware?
Thanks.
- Created as a process on disk"
C:\~ERAFSWD.TMP also contained these other files:
autodisc.dll
diantz.exe
findstr.exe
localui.dll
mqad.dll
share.exe
It was definitely a cause for concern to find that Prevx jailed a file in a directory that I've never seen before, and that the directory also contains serveral other ominously named .exe's and .dll's.
Are these files supposed to be in this directory? What could make Prevx think that something attempted to create mqad.dll as a process? What might Eraserl do that would cause Prevx to react to a file in that dir as malware?
Thanks.