MWBAM_Customer

Thanks, @AdvancedSetup, when I checked, I already had 1.0.1358, so that installed invisibly without issue, thank you. In @Erix's post, he refers to version 4.4.0.117, rather than 4.4.2.123. I'm not sure if the Dashboard Card refers to the issue I reported in my first post regarding Detection History, and also Scanner reports, but that issue remains. However, when Malwarebytes is maximised, the Settings options are also maximized.

You're welcome, happy to help. It's the first time I've had an issue with an install of a beta in so long, I can't remember when, so kudos to the developers and pre-beta testers. One issue that has persisted for a long time is when configuring a custom scan, Drive C is listed first, then the other drives are listed in reverse alphabetical order. One great feature of the Custom Scan drive selection is after selecting the first drive, using the down arrow selects the next drive listed - this is so much easier than having to click on a lot of tiny boxes and is a great touch.

Thanks for the swift reply Porthos. I've included the requested logs and also the install log created after I successfully installed Malwarebytes and the latest beta. I hope this helps. mbst-grab-results.zip mbsetup.log

I received a notification today of an update to Malwarebytes (beta updates are on) and I selected install. The installer removed Malwarebytes and shut down. I waited for a while, then rebooted, but no install of the new version. Before the reboot, all Malwarebyes services were removed, and there were no running Malwarebytes files. The install folder only contained the following files - mbam.manifest.json MbamBgNativeMsg.exe MBAMInstallerService.exe mbuns.exe I have attached the install log file. The folder "jenkins" is not one I opted to create and isn't on my machine. The install location was D:\Software\Malwarebytes Anti Malware. After the reboot, I downloaded Malwarebytes, and had lost all my settings, but it retained the license setting. I selected beta updates, which picked up the update and installed without issue. When going through reinstating the settings and performing an initial scan, I observed a graphical issue ... When viewing the Detection History and clicking on the Maximise button, the background is maximised, but the frame containing the Detection History remains the same size in the middle of the screen. If there's any further information I can offer to help with this, feel free to ask. Thanks for all your hard work, keeping us secure at this difficult time. mbsetup.log

Hi TempLost, Thanks for the update, glad you've got your install settled for the most part. Your post saved me a lot of head scratching, so thank you. I've also linked this thread in my support request to FoolishIT and will update it when I hear back. Take it easy.

As reported here by @TempLost, I have been encountering an issue when using CryptoPrevent Premium 8 (CP8) and Malwarebytes 3.0.6.1469-1075 CU3 (MWB3). I am running Windows 10 Pro 64 bit 1607 14393.693 and was running CP8 with MWB Anti-Malware 2.2.0.1024 MWB Anti Exploit 1.9.1.1341 MWB Anti-Ransomware BETA 8, v.0.9.17.661 without issue. I recently upgraded to MWB 3.0.6.1469-1075 CU3. Before following the correct clean removal procedures for all the MWB software, I noted TempLost's reported issue with MWB 3.0.6 and CP 8. Therefore, I disabled CP8 when I installed MWB3 as well as all other security and non-essential software. After a successful install, I re-enabled the software, with the exception of CP8, for testing purposes. I ran my system like this for about 4 days without issue. I then enabled Minimal Protection in CP, and ran for about 3 days, again without issue. However, when I enabled Default Protection, MB 3 could not start Exploit Protection. This was flagged as disabled, at boot, and attempting to enable it showed 'Starting' but it did not enable. On one boot, Exploit Protection did manage to start, but Malware Protection (I think) was unable to start. This problem occurs on every boot, and thereafter. Through multiple boots and testing, I have established that the setting "Prevent known malware from starting" in CP8 is causing the issue. I am running Default Protection with "Folder Watch", "Prevent File Types", all "Folder Watch" tab items selected as well as "Folder Watch HoneyPot" enabled. This configuration doesn't interfere with MWB when "Prevent known malware from starting" is disabled. Current CP8 version in use is 8_0_3_2. I have also reported this issue to Foolish IT. If there is any further information I can supply to aid you in this matter, please let me know.

Thanks Firefox, Will all of MBAM, MBAE and MBARW potentially auto-update to Malwarebytes 3.0? I know there's a setting for MBAM and MBAE, but haven't used MBARW in a while, so can't remember if that has a setting too. Also, if I may ask a further question, has any compatibility testing been done between Malwarebytes 3.0 and other non-AV solutions such as WinPatrol WAR, WinPatrol Firewall, Zemana Anti-Logger, PerfectGuard or CryptoPrevent, for example?

Hi Aura, Thanks for the swift reply. Will there be a post on the forums to notify users before the auto-upgrade stage is reached? I have run betas of MBAM, MBAE and MBARW on production systems many times, largely without issue, so previously I had confidence that when Malwarebytes software left beta it was ready and more or less issue free. However, the forums give more of an impression of Malwarebytes 3.0 as software that is a couple of betas short of General Availability.

I have been following the beta's progress with interest and was surprised to see the Beta 3 reach General Availability, considering the number and nature of issues users are encountering. I don't wish to try it yet until more issues are addressed, and will advise friends and family accordingly. My question is will any of the pre-Malwarebytes 3.0 versions of Anti-Exploit, Anti-Ransomware or Anti-Malware attempt to update to Malwarebytes 3.0? If that is likely, I'd rather take steps to prevent it until I am ready to deal with my machines individually and have confidence it will cause no issues. Many thanks.

Thanks for the information Nathan. I had disabled CM before installing MBARW. As MBARW seems like a keeper, I've uninstalled CM now. I'd noticed the EasySync Solutions site had been down for some time. I'm surprised Malwarebytes hadn't redirected the url or put an announcement up to say that it had been bought by Malwarebytes. Had I known that, I would have waited before buying anti ransom software. I see that a redirect is now in place.

Pardon me for butting in on someone else's thread, but the news that these fixes are happening for users as soon as they have been reported as fixed in the threads is great news. From reading all the threads here, it seemed implied, but this is the first time I have seen it stated. After reporting a potential false positive myself, I thought the fix would come out in the next beta release. Surely a feature such as this and rapid response to issues deserves to be clearly stated in the product announcement? Or at least clarified in the fix confirmation, otherwise people won't be testing the fixes. To put it another way, someone might look at the number of threads reporting issues and not want to try MBARW, believing these issues are outstanding, rather than fixed! Maybe also marking the threads as solved?

You're welcome, thanks for all your hard work.

Hi, I'm using the following security/anti malware/privacy programs with MBARW 0.9.4.299 on win 8.1 Pro I stopped using CryptoMonitor as Malwarebytes owns the company that produced it and employs its owner, so I assume it will perform at least all of its functions. Confirmation of this would be useful, as the EasySync Solutions site had been mentioning a new and improved version for some time. As to the relative protection provided by competing products and overlap or conflicts, that would be useful to know. I've only had one minor issue with MBARW when it was very slow/unresponsive, which considering this is the first public beta might have been a compatibility issue, or entirely unrelated. Hope this helps. Memory Resident Norton Security 22.5.5.15 Malwarebytes Anti-Malware Premium 2.2.0.1024 Malwarebytes Anti-Exploit Premium 1.08.1.1187 Raxco PerfectGuard WinPatrol Licensed WinPrivacy Licensed WinAntiRansom Licensed On demand CryptoPrevent (Default Settings) MBAR Super Anti Spyware Spybot Anti-Beacon Spybot Search and Destroy Spyware Blaster Depreciated CryptoMonitor

Hi, great work on the product, only one program has tripped MBARW so far .... Win 8.1 Pro MBARW 0.9.4.299 Process Hacker 2.36 (r6153) Note, there were two detections, one for the file, one for a registry entry for it, which I believe is used to replace the stock task manager. Zipped files attached. After the quarantine and reboot, MBARW seemed very slow and didn't appear in the task tray. - This was the first issue encountered since install. Closed MBARW with task manager and restarted it - was very slow to appear, but did eventually. Performed rest of report procedure despite being MBARW very slow to respond. Rebooted, no problem since. Hope the information helps. Other security/anti malware/privacy programs in use Memory Resident Norton Security 22.5.5.15 Malwarebytes Anti-Malware Premium 2.2.0.1024 Malwarebytes Anti-Exploit Premium 1.08.1.1187 Raxco PerfectGuard WinPatrol Licensed WinPrivacy Licensed WinAntiRansom Licensed On demand CryptoPrevent MBAR Super Anti Spyware Spybot Anti-Beacon Spybot Search and Destroy Spyware Blaster Depreciated CryptoMonitor MBARWFILES.zip ProcessHacker.zip

You're welcome Ron, I know some installers check for incompatible software already installed, I was just thinking of the easiest way to reach your less techincal users. Fortunately I identified the problem before anyone complained, as MBAM is on my recommended list, and IOBit software used to be. The only reason I'd continued with Malware Fighter was for its registry monitoring for system changes. Their software certainly is a great example of how not to treat your free software customers by trying to foist additonal products on them by less overt means.