-
Content Count
1,424 -
Joined
-
Last visited
Community Reputation
15 GoodAbout tetonbob

-
Rank
Staff
Recent Profile Visitors
22,719 profile views
-
Thanks for letting us know! The latest Beta is now available: https://forums.malwarebytes.com/topic/267583-malwarebytes-43-beta/?tab=comments#comment-1436637
-
Great, thanks for confirming. My apologies for overlooking that part in your original comment. That experience, as Erix noted, is why we disabled this CU shortly after it was enabled. We've got that fixed in the next Beta.
-
@brad03 out of curiosity, did you receive a tray notification to reboot after this Component Update (CU) was applied?
-
Code-signed EXE file quarantining after executing other programs.
tetonbob replied to RobPerkins's topic in Ransomware
With regards to this: That issue has been resolved and a new version of the Support Tool has been released. You should not see that issue now. -
BSoD - ransomware protection
tetonbob replied to Rimmsi's topic in Malwarebytes for Windows Support Forum
Hi @Rimmsi - we have now in Beta, a fix for this issue. See: https://forums.malwarebytes.com/topic/267583-malwarebytes-43-beta/?tab=comments#comment-1433990 If you are able to install this Beta, we would appreciate your feedback. -
This topic has been moved to the appropriate forum location, and will be investigated by the Browser Guard team.
-
ISHA Foundation has Trojan virus on Website?
tetonbob replied to bcorkins's topic in Website Blocking
This URL does not appear to be blocked. As @Porthos mentioned, this site is still blocked ishafoundation.org I've moved this topic to the correct location. Our Research team will investigate. For reporting possible False Positives with our Web Protection, please post in this forum: https://forums.malwarebytes.com/forum/123-website-blocking/ Thank you. -
Forced restart is not acceptable
tetonbob replied to lyesbkz's topic in Malwarebytes for Windows Support Forum
Hello. Please see: Users have now the options to schedule reminders for a reboot when one is needed -
Blender was detected an removed because it was detected as ransomware.
tetonbob replied to oats's topic in Ransomware
Thanks to all for your reports. Our latest version of Malwarebytes Premium is now in Beta, and intends to address this issue, along with other features and bug fixes. If you are interested in installing this Beta version, you can read more about it here: The plan as of now is to release this build to General Availability next sometime next week. -
Hi @TXDocs - would it be possible to run our data collection tool on the machine which experienced the detection of the TxDocs.exe file? Can you please collect and upload as an attachment the diagnostic data using our MBST? Download and run the Malwarebytes Support Tool Accept the EULA and click Advanced tab on the left (not Start Repair) Click the Gather Logs button, and once it completes, attach the zip file it creates on your desktop to your next reply If you prefer, you can send that data to me via Private Message.
-
We’ve been experiencing a service outage with our licensing systems. This should now be resolved. We apologize for any inconvenience.
- 1 reply
-
- 1
-
-
Greetings @Gdavies - Our Research Team will need more detailed information before we can address this. Can you please collect and upload as an attachment the diagnostic data using our MBST? Download and run the Malwarebytes Support Tool Accept the EULA and click Advanced tab on the left (not Start Repair) Click the Gather Logs button, and once it completes, attach the zip file it creates on your desktop to your next reply
-
Blender was detected an removed because it was detected as ransomware.
tetonbob replied to oats's topic in Ransomware
Thanks. The same workaround will apply here. Can any of you provide some detailed steps on how we might reproduce this issue? The Blender software is not one I'm familiar with. -
tetonbob started following southwest.tn.edu
-
Blender was detected an removed because it was detected as ransomware.
tetonbob replied to oats's topic in Ransomware
Thanks for the logs. For now, while we investigate the issue, the only workaround will be to add this file to the Allow List: C:\Program Files\Blender Foundation\Blender 2.90\blender.exe -
Thanks for your report. We're investigating this issue. We will post back when we have more information.