LiquidTension

Thanks for the file. This is related to a license state change that occurred before the upgrade. We have a defect filed.

Hi @unknownguy, Thanks for the report. Please gather logs with the Malwarebytes Support Tool and attach the generated file so we can take a closer look: https://support.malwarebytes.com/docs/DOC-2396

Thanks for the feedback. This particular page has only been brought over from Malwarebytes version 3 and hasn't been properly worked on yet for version 4. Once it's complete, the page will appear more inline with version 4's appearance (and not have any of the display issues you're seeing currently).

Great, thank you!

Thanks for the file! The display language issue is reproducible and we've filed a defect for it.

Great, thanks for the update!

Hi @lllobs, Thanks for reporting the issue. This is reproducible and we have a defect filed. As mentioned, the issue is caused by scan remediation being performed on an external drive. When this occurs, the following workarounds are available: Eject the drive in Explorer -> This PC (Open Windows Explorer, right-click the drive and click Eject). Stop Malwarebytes Service (Right-click the Malwarebytes icon in your notification area and click Quit Malwarebytes). Restart the computer.

Hi @TempLost, Thanks for the feedback. Could you gather logs with the Malwarebytes Support Tool so we can see why your display language changed after the upgrade: https://support.malwarebytes.com/docs/DOC-2396 Thank you!

Hi Maurice, Please gather logs with the Malwarebytes Support Tool so we can see why this was added.

Thanks for the logs, @ukbadge. The logs unfortunately do no contain much information. It looks like quite a few 3.8.3 install attempts were made in quick succession - the likely cause was a temporary rate limit by our licensing server. If you encounter any further issues, please let us know.

Thanks everyone for letting us know!

Hi @Phxflyer, Thanks for the report. This is not expected behaviour - even with over-the-top installing from a previous beta version. Let's collect logs (however, there may no longer be any pertinent details due to the uninstallation): https://support.malwarebytes.com/docs/DOC-2396 Please attach the generated mbst-grab-results.zip.

Hi @BillH99999, The fix is not present in the new version. It will be in a future component package update.

Hi @BillH99999, We will have a fix for Windows 8+ users in an upcoming release. It's not present in the current beta version.

Hi @boombastik, Not in this beta release. We may release a new component update to beta users that has the fix for this issue.

Detection for the file is being removed. With the next database update, you should find it's no longer detected in a scan.

Thanks very much!

Thanks. Could you check if a file named tmp-rww.xpi exists in your %temp% folder. If it does, please zip the file up and attach it in a Private Message to me. Does the block only occur with opening Microsoft Edge or other browsers as well?

Hi @fredvries, Once you have the product reinstalled and activated, please could you reproduce the block once more and rerun log gathering with the Malwarebytes Support Tool. Make sure you avoid clicking Start Repair. Please attach the generated mbst-grab-results.zip.

Thanks for the logs. Note that as you are running a Windows Insider Preview version, less testing has been performed for this OS version. Have you encountered this issue with other computers? Could you disable Web Protection (using the toggle on the Dashboard) and then shut down/power back on the machine. Do you still experience the issue with Web Protection disabled? Does setting Malwarebytes Service to delayed start have any impact? Download mbamservice_delayed.reg using the link below: → https://malwarebytes.box.com/s/15jbt7tifcetlhcgmszzb6appbak56w4 Right-click the Malwarebytes icon in your notification area. Click Quit Malwarebytes followed by Yes if prompted by User Account Control. Open your Downloads folder or location of the downloaded mbamservice_delayed.reg file. Double-click mbamservice_delayed.reg and click Run followed by Yes if prompted by User Account Control. Click Yes when prompted to continue. Click OK. Now please restart the machine

Thanks very much. Please let us know how you get on with version 4.

Hello, Thanks for the report. Could you generate a memory dump of mbam.exe whilst it's in the hung/not responding state? To do so: Wait for the Malwarebytes user interface (mbam.exe) to become unresponsive. Open Task Manager. Look for either "mbam.exe" or "Malwarebytes" in the list of running processes. Right-click the process and click Create dump file. A file named mbam.exe.dmp will be saved to your %temp% folder. Please zip this file up (right-click -> send to -> compressed (zipped) folder) and attach the file or upload it to a file hosting service of your choice. Could you also run the Malwarebytes Support Tool and gather logs: https://support.malwarebytes.com/docs/DOC-2396

We've been able to reproduce this and have a defect filed. Thank you for reporting.

Thanks for trying out the beta and sharing feedback, @boogeyman!

Hi @MSimm1, Could you verify if the crash still occurs with our latest Malwarebytes version 4 please. To do so: Open Malwarebytes. Click Settings. Enable the Beta Updates setting. Scroll back up and click Install Application Updates. Follow the prompts to install the Malwarebytes version 4 beta. Once installed, please verify if the MbamTray crash still occurs. If it does, please zip up and provide the latest crash dump (from the %localappdata%\CrashDumps folder). Thank you!