![malwarebytes premium 3.5.1 license key malwarebytes premium 3.5.1 license key](https://3.bp.blogspot.com/-8e5MWvkX77Y/W_FiIM4NC4I/AAAAAAAAAMo/36pHFEB8U1o2GCfOo0oPcyS3-9yylRlgQCLcBGAs/s1600/001.png)
Created on admin account with which credentials Malwarebytes is uninstalledĭouble-click mb-support-X.X.X.XXXX.exe to run the program These are created for every user account who opened Malwarebytes UI Mainly I spotted these locations not being deleted: This has been reported by other users in other topics. This is either a failure of MBST to grab and run FRST or UI is misleading about Run FRST step.
![malwarebytes premium 3.5.1 license key malwarebytes premium 3.5.1 license key](https://i.pinimg.com/originals/fc/20/38/fc2038b06f3994d529dfd33fce7a2b42.png)
To have full logs you have to manually download and run FRST scan with default settings before running MBST. If FRST never ran or its logs were deleted, logs would be incomplete. MBST doesn't actually run FRST during logs collection, it just scrapes C:\FRST\Logs and grabs what's in there. I saw this even with MBST 1.6.2 and now version 1.7.0. If I allow Support tool to install MBAM after cleanup, it installs the very old MBAM legacy 3.5.1 for XP. Both downloaded executable and unpacked executable to admin user temp folder have admin rights flag set. I don't remember exactly when and where but I read somewhere that Windows refuses to autostart programs that have admin rights flag set, especially if they try to run from HKCU. There I saw MBST autostart entry is in a Run key under HKCU. I was able to manually start post reboot cleanup using Autoruns tool. I drafted this report in this topic, but I think it deserves a topic of it's own for better visibility, especially as I discovered more issues.ġ.It doesn't autostart after reboot to perform post-reboot cleanup despite being logged on as admin both before and after reboot and UAC being already set to defaults since the very beginning. Endpoint Detection & Response for Servers