webwerker

Thanks everyone. I think some points are being missed. If I select, in general settings, that I want both PUP and PUM to be treated as malware, a reasonable person would assume that any hits would not only show up in the logs (which I realize can be opened as a text file - but why can't you just highlight the entry and copy the registry path?) but would be quarantined as well. This does not happen. Perhaps this is an incidence of the scan reporting items that have already been deleted. Also, I am using the premium version. not sure why that's relevant. However, my main point was that it would be nice to be able to add a descriptive name to custom scans created by users so it is obvious at a glance what it's configured to do. Thanks for your consideration. Eric

What I'd like to suggest is that you give the user the opportunity to give a name to any customized scans they create. As it is, as you know, any custom scan is named, with the greatest precision, "Custom." Users who have never created a custom scan or have only created one will probably not see this as an issue at all. In my case, however, I have created more than one custom scan. I have done this mainly to get around what may be a bug or may be normal behavior or..., whatever it is, it is ambiguous. Because I don't like stuff happening behind my back, I have chosen to have both PUPs and PUMs set to be detected and treated as malware. By doing so, what I thought would happen is that they would end up being quarantined and not just reported in the log. Some of these things are so tricky that they are listed under users who don't exist and can't be found in the registry, at least by ordinary means or even with some advanced registry editors that enable searches by ID, parts of strings, etc. The entry reported by Malwarebytes just doesn't exist in any obvious way. Maybe they're in an archive or backup, etc., and, if so, Malwarebytes should tell me so. However.... The only way I have found to flag both PUPs and PUMs as malware and so be quarantined is to build a custom scan because the "custom" button in the Custom Scan settings window will let me select both PUP and PUM. When the custom scan runs, they are reported and quarantined. Unfortunately, none of the default Malwarebytes scans produce this result even though I have both selected under the Detection and Protection setting. This is why I've had to construct several Custom scans, basically to reproduce the default scans but with the addition that they detect and quarantine PUPs and PUMs. And so, for me, in my case, it would be helpful to be able to give a custom name to custom scans. Thank you for giving this a high priority just for me! Oh, and by the way, when I am creating or editing custom scans, Malwarebytes crashes frequently. I have never had the program installed before so it hasn't overwritten an earlier version. I am using version 2.0.2.1012 on Win 7 Pro.