Jump to content
Posted 01 February 2010 - 10:17 AM
Posted 03 February 2010 - 02:35 PM
explanation by miekiemoes, Administrators at Malwarebytes
Malwarebytes sees and reports that the association for these files are not the default ones as set by Windows (since malware may alter these associations as well). When you select to remove in mbam, mbam restores it to the default associations again (as set by Windows).
So you have 2 choices here... Or you ignore the detection in mbam, or you don't let System mechanic modify the default associations
It simply means that one of the file associations are no longer using the default Windows setting. This could be on purpose by you or software that you use but it is also a method used by Malware so we flag it. If you're telling MBAM to change it and it comes back then some program you're using is either blocking the change in the Registry or maybe a program you use is reverting it back.
If you chose it and want it to remain that way then you can ignore it. If you did not chose that then have MBAM fix it and if you have software that blocks Registry changes then you need to tell the program to allow MBAM to make the change.
explanation by Malwarebytes Staff
There is at least one tool that disables these as a "security fix" . MBAM cant tell why a modification has happened , only that it has.
Posted 03 February 2010 - 03:06 PM
Posted 03 February 2010 - 03:19 PM
Posted 03 February 2010 - 03:28 PM
Posted 03 February 2010 - 03:33 PM
0 members, 1 guests, 0 anonymous users