Version 1.60 and XP Pro SP3

[Jaeger1121]

Just updated from my "old" version of free MBAM to the "new" version through the updater. Upon restart of MBAM get an mbam.exe - application error stating that "The instruction at memory xxxxx referenced memory at xxxxxxx. The memory could not be 'read'."

Granted it only took a few minutes for me to navigate to the forums and find the "fix" of using the MBAM cleaner file posted in another thread but what about all those "little old ladies" that I've suggested MBAM to over the years? This is just an opinion but if you have a "push this button and we'll remove the old and install the new for you", it should really work as advertised, especially given that you're trumpeting your "new relaease". I expect half-done patches and solutions from Microsoft (part of the reason I'm still on XP) but I didn't realize that you folks would sink to the same level once you started offering a Pro version.

There are enough crapware programs and patches out there. Please don't add your company to that mix.

[AdvancedSetup]

Yes we understand the frustration however this issue did not arise during any internal or external beta-testing of Malwarebytes Anti-Malware 1.60, as can be seen from reading the threads in our beta-test forum. It was highly configuration-specific, and apparently we didn't have any beta testers with the very specific configuration.

If you are a user who experienced this issue, and are willing to help us, please join our beta test program! Get involved and you can help us prevent issues like this from arising in the future.

Thank you for your feedback.

[Jaeger1121]

I'm willing to add my very limited skill set.

Thanks for the follow-up.