Avast just ran it’s skedualed weekly scan when it was finished these were the error messages that these files could not be scanned??? they are avast files, non of my other scan’s resulted in this always “no Virus found” I did a repair, updated program file and did a boot scan result was NO Virus Found! What’s up with the first scan???
Thanks but now I have another issue, just ran a full system scan again and this time shows a Trj? as: local settings\ temp.…\mbam.exe.hdmp Win32 Crypt-GCA (trj) I put it into chest? is this another false positive? been running malwarebytes with no issue’s as well as Avast until the now 2 incidences? OK after I post this reply I’m going to run malwarebytes and see what happens. Oh it showed as a temp folder so is it ok to delete it?
there are some exlusions of files that you may sett in avast and MBAM so they dont conflict
the guide is in malwarebytes forum…i post the link if i find it, unless somone else here do it
this file is an MBAM dump file created at a time of a problem/crash of mbam, that may have the contents of its memory, etc. at the time of the crash.
This .hdmp file could contain malware signatures and or encryption (based on the malware name given by avast), so it is almost impossibly to say it is an FP. I suspect it isn’t given it is a dump file that could contain malware signatures and that is the very thing that avast is looking for, virus/malware signatures.
I suspect it isn’t given it is a dump file that could contain malware signatures and that is the very thing that avast is looking for, virus/malware signatures.
[/quote]
Hummmm! but I haven’t had any issues with mbam, no crashs that I know of, only awhile back got a message to update program that there was an issue on the previous update, which I did. it’s been running normal. OK well I did move that file to chest then Deleted it as Asyn siad it was ok to do? Should I also run MS tool to clean all temp files?
These dump files can be created and the user not be aware of a crash/problem with the product. The file type itself is what indicates there was an mbam dump.