Jump to content

Search the Community

Showing results for tags 'beta'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Malwarebytes News
    • Beta Testing Program
  • Malware Removal Help
    • Windows Malware Removal Help & Support
    • Mac Malware Removal Help & Support
    • Mobile Malware Removal Help & Support
    • Malware Removal Self-Help Guides
  • Malwarebytes for Home Support
    • Malwarebytes 3 Support Forum
    • Malwarebytes for Mac Support Forum
    • Malwarebytes for Android Support Forum
    • Malwarebytes for iOS Support
    • False Positives
    • Comments and Suggestions
  • Malwarebytes for Business Support
    • Malwarebytes Endpoint Protection
    • Malwarebytes Incident Response (includes Breach Remediation)
    • Malwarebytes Endpoint Security
    • Malwarebytes Business Products Comments and Suggestions
  • Malwarebytes Tools and Other Products
    • Malwarebytes AdwCleaner
    • Malwarebytes Junkware Removal Tool Support
    • Malwarebytes Anti-Rootkit BETA Support
    • Malwarebytes Techbench USB (Legacy)
    • Malwarebytes Secure Backup discontinued
    • Other Tools
    • Malwarebytes Tools Comments and Suggestions
  • General Computer Help and Security Updates
    • BSOD, Crashes, Kernel Debugging
    • General Windows PC Help
  • Research Center
    • Newest Rogue-Ransomware Threats
    • Newest Malware Threats
    • Newest Mobile Threats
    • Newest IP or URL Threats
    • Newest Mac Threats
    • Report Scam Phone Numbers
  • General
    • General Chat
    • Forums Announcements & Feedback

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Location


Interests

Found 27 results

  1. Greetings! We have a new Beta available through our in-app Beta channel 3.5.0 We’ve started rolling out upgrades for this version. If you are signed into the Beta setting and don't want to wait to be notified by the program that your upgrade is available you can always grab the upgrade manually by clicking Install Application Updates in Settings > Application (if you're running MB 3.2 or later). Here’s the list of changes / improvements in 3.5.0: Performance/protective capability Added support for Hypervisor Code Integrity (HVCI) and Device Guard to meet Microsoft compliance requirements Improved the remediation process so fewer reboots are required Improved the accuracy of the Web Protection module Improved driver management for increased stability Continued improvements to overall protection, detection and remediation Usability Updated the dashboard design to better showcase Malwarebytes real-time protection features Updated Notification Center behavior to make it easier to dismiss Numerous other user interface and copy enhancements Stability/issues fixed Fixed issue where anti-ransomware module could cause high CPU and memory use Fixed an issue where Malwarebytes would open to the scan tab instead of the dashboard Fixed reported crashes related to Web Protection Fixed several translation issues Addressed other miscellaneous defects Thanks!
  2. I installed the Malwarebytes Firefox Extension (beta) but every time i open this link rebrand.ly/advancedir which leads to my website's link https://usefulsoftwaresritesh.blogspot.in/2018/02/hey-friends-today-i-am-writing-about-my.html?zx=ee0185d9b1870d66, Malwarebytes blocks it telling that it is a phishing website. Very bad experience. You can download the screenshot from https://transfer.pcloud.com/download.html?code=5ZFFam7Zlx0spK89OqfZEeaLZMU0SDCihREHg3UVTbyQeYJBlhjCy.
  3. I can confirm that the 3.4 beta fixes the update failure which was occurring when Windows TEMP/TMP is on a RAM Drive. (As previously reported in the topic "Update Failure IS because of TEMP on RAM Drive" in Malwarebytes 3, Malwarebytes Forums at https://forums.malwarebytes.com/topic/206678-update-failure-is-because-of-temp-on-ram-drive/) During installation, the initial "Runtime Error (at ...): Could not call proc" error message still appears but, after that is acknowledged, installation continues with a request for a Windows re-start so that installation can be completed. After restarting, a prompt is issued asking if the user wishes to run a file from an address in the TEMP directory (on RAM drive). When this is agreed to, installation proper begins and proceeds as would have been expected. For me, the process appears to have completed successfully and resulted in an on-top update from MBAM 3.3.1.2183 to MBAM 3.4.0.2380 Beta. The process was straightforward and I did not need to tamper with any environment variables at all. My previous settings were all preserved apart from the currently usual need to restore the 'Display Language' to my required value. Thank you for the fix.
  4. I tried to install v. 3.1.0.1716 over the top of 3.0.6.1469-10103. The install seemed to go fine, but after re-booting I got the "unable to connect to service" error and MB would not start. I never had any problems with version 3.0.6.1469. I just wanted to let you know that I used mbclean to uninstall MB from the system and then re-installed v. 3.1.0.1716 and this time it worked fine. All protections started up without any problem and a threat scan ran in a normal amount of time for my machine. I just thought folks might want to know another experience and how it went. Hopefully this will help someone else if they run into the same problem. Thanks, Bill
  5. Malwarebytes Anti-Rootkit is over 4 years old now, yet it's still in the BETA version, why?
  6. I've been using MB beta version for close to a week now on my Windows 10 64 bit ENVY laptop. I must say it's running beautifully with no hangups nor any type of quirks. Scans run, updates working and absolutely no problems. Attached is my MB checkresult. Can anyone tell me if what it says is good or bad? I can't understand most of it. Thanks MB-CheckResult.txt
  7. even with new beta 3.1.1 of malwarebytes and new setting for manual scan I had set the setting to lower the priority of manual scan to improve multitasking . but this did not help at all . still high memory usage during the Threat scan I thinks . so any plan to find more fix for the software ?
  8. A possible weirdly-timed coincidence, no doubt, but IF I Uncheck all 4 Modules via the System Tray M icon does THAT do all I can to eliminate MBAM as a Suspect in not being able to Safely Remove my Western Dig Ext Drive (ie) "Close all programs and try later". Tried for 2 days & no success ........ Never was an issue with v2 and I can't think of a system change other than the v3 Upgrade that has occurred just Before this issue started. There are reasons I prefer Not to Turn-Off the computer or even re-boot to switch to a 2nd Backup Drive, so Any Suggestions / Clarifications are appreciated. v3 Running Perfectly.
  9. I also seem to have a problem after updating to 3.1.1 - all worked well (including initial boot this afternoon) until Windows install two critical security updates (KB4016871 and KB4020821) - now the exploit protection refuses to turn on. I have since rebooted twice and still get the same problem. Note - this is not like the Web Protection failing to start (would just stick on Starting...) - when Exploit Protection is toggled on, it thinks about it for a second and then toggles back to Off. I have Kaspersky Internet Security installed, which is also up to date, and have included the relevant folders in the exclusions of both applications.
  10. After becoming disheartened with MBAM 3.06 and returning to tried and true 2.2.1 several months back, I noted the release of 3.1.1 and decided to give it a shot. I ran mb-clean after removing MBAE and then installed 3.1.1. It installed and updated without issue, and activated my pro key, also without issue. I lives happily with my ZoneAlarm firewall and Avira av. After many months of frustration, trying to get 3.06 (in various flavours) working properly, it's only fair and fitting to offer the dev team a big THANK YOU for sorting it out. Well done.
  11. This is on Windows 10x64 Pro Build 15063.250 V1703 with the beta version 3.1.1.1722 of Malwarebytes When running a system scan or a customs can of my system SSD which is a Samsung 950 Pro NVME M.2 SSD partitioned as the C and D partitions, the scan runs fine. However, when the scanner jumps to the heuristics scan component, it finishes the heuristics scan in 1-2 seconds. My system is fast, but not that fast. Logs are attached. Addition.txt FRST.txt logs.zip MB-CheckResult.txt
  12. I've just successfully upgraded to the new beta release from 3.0.6 CU4.1. As suggested, I ran an over the top installation. As others have done, I voluntarily rebooted after the installation although this was not requested by the installer. The installation went smoothly. I have noted that during the upgrade, my premium (lifetime) licence and activation were correctly retained, along with scheduled tasks and exclusions. As reported by others, the UI language was reset. After the upgrade, updates were reported as "Updates: Current" on the dashboard, but clicking on that found more to install. A bug that I've not seen reported yet. In the reports list, clicking the head of the "Date and Time" column to sort by date seems to sort the opposite direction to that which the sort arrow suggests (arrow pointing down returns an ascending date order and vice-versa). I noted reduced memory footprint (now 230MB, previously 260MB), and the Office 2016 save crash was fixed. My system is Windows 10 pro x64 v1703, running Malwarebytes 3 Premium alongside Kaspersky Total Security 2017 (MR0 patch e), and Macrium v7 Home paid. Prior to this upgrade my issues were: The office 2016 "save as" crash (apparently fixed in 3.1 beta) Occasional infrequent protection start failures (any of the four real time modules), recent (pre 3.1 beta) updates much improved a previously much worse occurrence rate. Out of ten or so random failures over the past couple of months only one was not fixable by Quitting Malwarebytes from the system tray icon and immediately restarting it from the desktop icon. The one occurrence for which that cure failed was fixed by a reboot. (3.1 beta status – unknown as of yet – time will tell) Suggestions: Rename the default "English" language setting "English (US)". UK users cannot see it's sub-optimal for us. As I suggested in another topic, add tooltips to data the "Location" and "Threat" fields of reports (and the quarantine list) to allow quick perusal of reports without fiddling with column widths. As another forum user suggested, add "Stopping..." as a status for the real-time modules. You can click to disable them and not realise the click was accepted and the service is pending stopping. Then click again (which is also accepted) and eventually you see the protection turn off then flick back on again as both clicks take effect. Resurect the "Known issues" list on the forum. As others have said, having forewarning of significant issues, or a place to check for known issues during troubleshooting can be a massive time saver. [please nobody other than forum or Malwarebytes staff respond to this point - enough unnecessary unpleasantness was spread in the other topic about this] "Protection History" on the dashboard does not say much useful. it needs to put the figues into context (a limited time period that the counts cover?) and maybe even click through on the "Scan detections" and "Real time Detections" figures to lists of those detections. x64
  13. I am getting same event errors with the new Beta 3.1.1.1722. I may have gotten them with 3.1.0.1716 but cleared my Event log. Log Name: Application Source: Application Error Date: Thursday, May, 4, 2017 10:53:37 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Jim-PC Description: Faulting application name: MicrosoftEdgeCP.exe, version: 11.0.15063.0, time stamp: 0x58ccbae4 Faulting module name: EdgeContent.dll, version: 11.0.15063.250, time stamp: 0xc697795c Exception code: 0xc0000409 Fault offset: 0x0000000000075817 Faulting process id: 0x2574 Faulting application start time: 0x01d2c537d06db9b1 Faulting application path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe Faulting module path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\EdgeContent.dll Report Id: d4d4b0fa-db8d-431f-b587-4e3d6799de80 Faulting package full name: Microsoft.MicrosoftEdge_40.15063.0.0_neutral__8wekyb3d8bbwe Faulting package-relative application ID: ContentProcess Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-05-05T03:53:37.042052000Z" /> <EventRecordID>5227</EventRecordID> <Channel>Application</Channel> <Computer>Jim-PC</Computer> <Security /> </System> <EventData> <Data>MicrosoftEdgeCP.exe</Data> <Data>11.0.15063.0</Data> <Data>58ccbae4</Data> <Data>EdgeContent.dll</Data> <Data>11.0.15063.250</Data> <Data>c697795c</Data> <Data>c0000409</Data> <Data>0000000000075817</Data> <Data>2574</Data> <Data>01d2c537d06db9b1</Data> <Data>C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe</Data> <Data>C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\EdgeContent.dll</Data> <Data>d4d4b0fa-db8d-431f-b587-4e3d6799de80</Data> <Data>Microsoft.MicrosoftEdge_40.15063.0.0_neutral__8wekyb3d8bbwe</Data> <Data>ContentProcess</Data> </EventData> </Event> I ran FRST64 and in Addition file it showed a bunch of these. Date: 2017-05-04 23:30:17.567 Description: Code Integrity determined that a process (\Device\HarddiskVolume4\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe) attempted to load \Device\HarddiskVolume4\Program Files\Malwarebytes\Anti-Malware\mbae64.dll that did not meet the Store signing level requirements. FRST.txt Addition.txt
  14. I clean installed this version on Windows 10 x 32 1703 15063.250. Defender with all recommended exclusions. Seemed to work, then I tried starting Chrome, IE, Edge and Firefox in rapid succession, whilst randomly turning off/on various MB protection layers. IE and Chrome crashed. The issues from the event log are attached, as are MB logs. All seem to be related to mbae.exe. I should add that I haven't installed MB for a while, I've been waiting for the problems to be fixed. So I don't know if previous versions would also exhibit these issues. events.txt MBAMSERVICE.zip
  15. Had two Desktops(A,B) and one Laptop (C) running MWB Premium 3.0.6.1469 : 1.0.103. "A" has Windows 10 Pro , "B" has Windows 10 Home as does the Laptop "C". All are at 1703 15063.250. Initially I downloaded and installed 3.1.0.1716 : 1.0.115 to "A" and "B". No problems other than the Language change to English from English UK and both required a restart. When I did the Laptop, it installed o.k. but didn't require a Restart!. Checking the logs I can see that both "A" and "B" had a file in use so the restart was deemed necessary. The file was:- C:\Program Files\Malwarebytes\Anti-Malware\mbshlext.dll. Laptop file was replaced during the install so no restart was necessary. I don't understand that as I normally follow the same routine for all three. Anyway, noticed that 3.1.1.1722 : 1.0.117 was now released. Installed that to all three and no restarts required for any of them. Currently all three are running with no problems. Just to make it clear, I just ran the install over the existing setup. At the moment I am only running Windows Defender with Malwarebytes3.
  16. Hi All, I installed yesterday Beta 3.1.0.1716 on my Win 10 X64 Creators version and it failed right away, not able to start. I installed it a 2nd time and it started but my machine was not responding at all very sluggish. I backed off to the previous version and all was well again. Today, I tried again with version 3.1.1.1722, install went perfect ane machine is working fine, thank you for the VERY QUICK fix!
  17. Hi all-- Just wanted to let you know we've refreshed the latest Malwarebytes 3.1 beta -- see details here: The main change in this version is an updated version of our anti-exploit protection that fixes an issue where Internet Explorer could freeze. Please simply install this new version over any previous version of Malwarebytes you may be running, whether earlier beta or officially released version. Thanks,
  18. I installed this over the previous version of Malwarebytes Premium and all seems to be OK, with new options showing in the menus. The only negative so far is that my language reverted to US from UK (which means that date format is not dd:mm:yy as I would normally use) and Outlook appeared to have disappeared from the list of protected apps, where I had previously put it. Windows 7 Home Premium SP1 x64 Malwarebytes Premium v. 3.1.0.1716 Avast Free 17.3.2291 CryptoPrevent 8.0 Premium Tweaking.com Windows Repair Pro 3.9.27 (incorporating Registry Backup 3.5.3) Casper 10 Backup
  19. Hi, Have downloaded this new update, installed it on my machine, re-enabled the protection on the Office applications, and the files now save with no problems. Thanks
  20. Jekko an all malwarebytes staff, to solve all issues, program must be repaired and well done from your end my friend. N.B. I tried several things, also did a format Regards
  21. So far I have installed this v3.1.0.1716 beta on two computers.... one is my desktop (see sig) Win10 64bit Version 1607. Second is my Surface 4 Pro Win10 64bit Version 1703. Both computers have Symantec Endpoint Protection with exceptions added. On my desktop all went well, installed over latest MB3 version and scans are normal, no slowdowns or issues thus far. IP Protection test page working, and Anti-Exploit test working. On Surface 4 Pro, different issue... I installed over the top of Version 2. Install went fine. Ran a scan and no matter if the GUI is open or closed it uses 100% of the CPU during a scan. (granted the scan only takes 2 minutes - rootkits enabled - archives disabled) I have rebooted the computer several times and all was well until I tried to turn off self protection. It turned off OK, tried to do a scan to see if it would help with CPU usage, it did not, went to turn it back on and MB3 Crashed and said it had to be launched. Turned Self Protection back on, and now Ransomware Protection turned off, and when trying to turn it back on, its stuck at starting.... IP Protection test page working, and Anti-Exploit test working. I will reboot the surface and monitor, if it continues I will try the clean re-install method instead of an upgrade from v2 to v3.
  22. Computer: ASUS ROG G20AJ, Intel Core i5-4460, 8gb memory, 3.2GHz OS: Windows 10 Home, build 14393, 64 bit One day ago I installed the mb3-setup-consumer-3.1.0.1716.exe program; after reboot, I received a Malwarebytes dialog "Unable to connect the server." I restored my system from a backup image. After browsing the forum, I decided to give another effort: Quit Malwarebytes from the tray icon. Ran the mb-clean-2.4.1.1015.exe program; when it completed, a reboot dialog request showed - I rebooted. After login, the dialog requested "Would you like to download and install Malwarebytes v3.x?" - I clicked on No. The program exited. Ran the mb3-setup-consumer-3.1.0.1716.exe program; installed successfully. I had to reactivate my license. Ran a scan. Seems OK. Rebooted. Seems OK.
  23. I did a clean install on my machine and so far so good. Web Protection is much faster now, the impact on web browsing is minimal and DNS latency is lower than last stable version. The ability to exclude the last website blocked by Web Protection via the tray menu is nice and makes the product much more easy to use and machine learning protection sounds promising. I feel that my machine is running smooth now, but there is some slowdown with Windows Defender (mutual exclusions). My config: Windows 10 CU 1703 x64 Core i5 2500/8gb ram Windows Defender enabled
  24. Installed over previous latest version without problems; did a restart even if it was not asked for. All settings perfectly retained, no issue up to now. This new version did even resolve a pending issue : A BIG thank to the developers ! (Win10 1703 Build 15063.250)
  25. Congratulations to all on this beta release. Over-the-top upgrade (with compulsory system restart) from a previously trouble-free CU4.1 was perfect and all licensing, exclusions, scheduled scans, and customizations were preserved. The threat scan is just as rapid as before. Works and plays well with ESET NOD32 10.1.240.0 (without mutual exclusions) and W10Prox64 Creator 15063.250 Thank you all. ThreatScan.txt MB-CheckResult.txt Setup Log 2017-05-01 #001.txt
×

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.