Question about MBAM and malware removal

[tomdkat]

The other day, I upgraded MBAM 1.75 to 2.0.2 on a Windows 7 system and used it to remove several PUPs.   During the quarantine process, some files couldn't be moved until a reboot had been performed.

 

Here is the issue:  after the quarantine process had completed, MBAM reported the system was clean and I was able to close MBAM without issue.  About 2 minutes later, I received a popup window indicating the system had to be rebooted in order to complete the removal process.  After doing this reboot, the PUPs went away and the system was running much better.  I expected to NOT be able to close the MBAM window before receiving the notification that a reboot was required to complete the removal process.

 

Is this a bug or is this by design?

 

Thanks in advance!

 

Peace...

 

 

[daledoc1]

Hi:
 
Until the staffers arrive to weigh in........
 
PUPs are classified as "non-malware detections", so it seems that it could be possible to be able to close the GUI until the reboot notification appears?
 
Having said that, I'm not sure if that delay in notification asking for the reboot is entirely by design or not.
For that, we'll need to wait for the staff.
But it does sound like a bit of a bug, although there may be a technical reason why this behavior is needed.
 
Until then, if your recent upgrade was on top of your 1.75 installation, you might want to try a clean reinstall of version 2.0.2, to see if that resolves the behavior:

To so so, please follow the steps in this pinned topic to uninstall your current version of MBAM and reinstall the latest build - MBAM Clean Removal Process 2x

 
Cheers,

[tomdkat]

Thanks for the feedback!

 

Peace...