Mbamchameleon Failed to obtain file name information

[zamar17]

I have current version of Malwarebytes (v 2.0.4.1028) running on a Win 8.1 64-bit PC, and as soon as Self-Protection Module gets enabled, it starts spamming Windows Event Log with huge quantities of the same message "Mbamchameleon Failed to obtain file name information - C00000D4" indefinitely until I disable the module. The message doesn't contain the file name, so its impossible to add this file to Mbam Exclusions list.

 

I found many similar threads on this forum, all devoted to exact same issue. None of them was answered by Malwarebytes in a constructive way. On the contrary, all threads either remained unanswered by staff, while volunteers suggested to collect diagnostic logs that weren't used anyway, or the staff member said its "normal behavior" and therefore doesn't require any bug fixing or a different design approach to address.

 

Meanwhile, this endless logging seriously impacts PC performance and clogs SSD drive affecting its lifespan, while contributing nothing to the issue resolution, IF mbam in fact found any issue. Any objective software developer would say such program behavior is definitely NOT NORMAL. A different approach must be found to trap such events that wouldn't clog the system with useless logs. Or, if you want to log them, log the file name, so the PC user can attempt some remedy, such as adding the referred file to Exclusions List.

 

I've questions:

 

 

- when this idiotic program behavior will be fixed, or at least the log content gets useful?

- why it was never addressed before, thus demonstrating extreme neglect of Malwarebytes staff to this useless logging grossly affecting customer PCs performance?

- how I can find the file name(s) & locations that trigger this event?

 

 

Pls do NOT suggest to Disable Self-Protection Module, as this is not a proper solution. If we start disabling every buggy but still functionally useful module instead of fixing its bugs, pretty soon there will be no working modules left. Why then customers need to pay for your software?

[zamar17]

Further, I added Eset Smart Security Suite program folder to Malwarebytes Exclusions, and that didn't stop the above logging. Similar solution was indirectly suggested here. I clean uninstalled and reinstalled MBAM using your Cleaner without any changes in described logging bug. I don't have any other AV packages running. My PC was thoroughly tested and doesn't have any malware causing this issue. Its merely MBAM code design defect that was reported by numerous customers and never fixed.

 

If there is a need to collect any diagnostic logs , let me know what I need to look for in these logs to identify what file(s) cause this endless logging event. At this point hope is slim that MBAM staff would be willing to address such customer reports, at least until some complaints are filed about "fraudulent advertising" reg Self-Protection Module, since the only suggestion customers eventually get is "Switch it off" instead of "We'll fix the issue or find a different design approach shortly".