Jump to content

blender

Staff
  • Posts

    1,223
  • Joined

  • Last visited

Everything posted by blender

  1. Hello, Thank you for the report. This was a detection by our heuristics engine. It should be fixed now. Might take a few minutes before you see it.
  2. Hello, Thank you for reporting. Having a look now. I'll get back to you once I have a look.
  3. Thank you for the report. Confirmed False positive and fixed.
  4. Hello, I am not seeing a detection on this file. Are you still seeing this @Chas4?
  5. Hello, No hits here either. This was fixed May 21st. Might want to check your mail server is getting updates in a timely manner.
  6. Hello, I am not seeing any hits on my machine so it looks to have been fixed already. As stated by above, VT is sometimes slow in catching up.
  7. Hello, Thank you for reporting. This has been fixed already. Sometimes VT takes a bit of time to catch up on their engine/database updates. I am not seeing the hit on my machine.
  8. Hello again, Indeed this is a false positive by our heuristic engine. It is fixed now and you should see results in a few minutes.
  9. Hello, Thank you for reporting. I am having a look now and will reply back once I am done analysis.
  10. Hello, Thank you for reporting. This should be fixed shortly.
  11. Thank you for reporting. This should be fixed shortly.
  12. Hello, Can you zip and attach a sample file please along with a log of the detection? Thank you,
  13. Hello, Thanks for reporting. This has already been fixed. Please ensure MBAM is up to date and a re-scan should show clean.
  14. Hello, This has been fixed. It should only be a few minutes from time of this reply to when you can use the app. Thanks for reporting!
  15. Hello, Yes please post the logs. File too if possible. Thank you,
  16. Thank you. Yes, Virustotal links are fine to use. Our engine format and configuration in VirusTotal is different than our consumer and corporate products’ default configuration. In VirusTotal we use a command-line engine with different configuration and detection techniques/heuristics which might detect more than the commercial product. There are also false-positive suppression mechanisms in the commercial product which are not present in the command-line engine in VirusTotal. These files have been whitelisted for our commercial products and it is not detected anymore.
  17. Hello, I'm not getting any detections. Any chance you can attach the log(s) please showing the detections? Thanks!
  18. Hello, I cannot reproduce the detection. If you re-scan, are you still seeing it?
  19. Awesome. Looks like you are good to go. Any further issues, please don't hesitate to contact us again.
  20. Did you delete the files from recycle bin that were in the test folder? If they are still in the trash, can you restore them back to the test folder, rescan that folder and post the new log here please. If you already emptied the trash, then you can go ahead and delete the test folder we made too. As long as everything is running OK, we won't need that folder any more. Thanks!
  21. Decent chance that next time you run a program that requires the old .NET you will likely be offered to re-install it. (if anything is using such an old version) In any case, I just realised you are running an older version of MBAM itself. -Software Information- Version: 4.1.2.73 We are currently at 4.3.0.98 which should fix the issues with those files. If you are not already being prompted to update, open MBAM >> click the gear looking button at top right>> click "check for updates". Follow instructions for installing the updates. You may be required to reboot. Should be good to go after that.
  22. Those sub directories in the assembly folder have many versions of .NET files from multiple versions of .NET. Perhaps you don't see any errors now but I wouldn't be all that surprised if something pops up later on. Those files are legit. Something in our heuristics detected them. I suspect the issue has already been fixed. I'm not sure which version you would need to re-install. Let me see if I can find someone else to pop in to have a look here. Don't delete anything else ...
  23. If you mean delete the files out of the original location (out of the assembly\....\ folder, no.. don't delete them. They are part of your .NET install. If you mean, the files you copied to "test" using cmd, yes, you can delete those. Let's try this: Shut down Malwarebytes by right clicking icon by the clock and choose "shutdown Malwarebytes" (OK UAC prompt and prompt from MBAM if asked) Open cmd again (search menu>> search for cmd>> right click and run as admin). Copy/paste the following lines one at a time into cmd and hit enter after each one: cd C:\ProgramData\Malwarebytes\MBAMService del hubblecache exit cmd Once done, restart Malwarebytes and re-scan. You can just double click the desktop shortcut to get it going again. Yes it will take a moment to restart and if you look, hubblecache will be back.. just replaced with a fresh one. If you don't want to wait the 2+ hours to scan, go ahead and scan the C:\Windows\Assembly folder itself. Let me know how it goes. Thanks!
Back to top
×
×
  • Create New...

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.