• Content count

  • Joined

  • Last visited


About thisisu

  • Rank
    Research Engineer

Recent Profile Visitors

9,081 profile views
  1. Hello and welcome to the forums. This isn't a false positive. The installer is well-detected ( as the installer insists that you also include components that modify your browser -- hence our potentially unwanted (PUP.Optional) detection.
  2. No problem Regards
  3. Hi and welcome to the forums. The file is not detected by us. As someone who has run into this before, I would tell whoever compiled this executable to look into something called dual digital signatures. I run into this error as well when trying to download the file using Microsoft Edge on Windows 10. Works fine on Chrome
  4. No problem. Please wait until AdvancedSetup returns as he may have some additional clean up steps for you. Enjoy your weekend
  5. Ok good, any remaining issues?
  6. Yes, doing so should stop the notifications regarding WinRange.exe.
  7. Hello, try updating MBAM database to 2016.07.16.01 (current version) and scanning your system again. We added some "PUP.Optional.WindowRangeManager" detections which should pick up the program you're referring to.
  8. Hi, thanks for the information. I hadn't noticed this before. I will look into it. Regards
  9. Hi and thank you for the report! This will be fixed in the next update.
  10. Hello, Thanks for continuing to support our software after 5 years! It's much appreciated. The reason the detection hasn't changed after all this time is is because it's still a potentially unwanted modification (PUM). The PUM.Optional classification is different from actual malware which are typically labeled as "Trojan", "Worm", "Spyware", or "Backdoor" instead. Since you or someone you know deliberately changed this policy from its default value, you can safely ignore the detection MBAM gives. As far as Windows 10 not being detected, it could be an issue but it's outside the scope of this subforum. If you want answers regarding this, please create a topic here. Thanks
  11. You're welcome.
  12. Those files are related to BitDefender and therefore aren't malicious. I suspect they contain information about previous or current BitDefender product and/or definition updates. JRT removes them to tidy up as they aren't required to run BitDefender and somewhat slow down diagnostic log analysis. They aren't put in any type of quarantine folder or Recycle Bin. They are gone. If you did want to restore something JRT deleted, use the System Restore point that JRT created prior to it starting any scans.
  13. Fixed in 8.0.7 which was released today.
  14. Fixed in 8.0.7 which was released today.
  15. Fixed in 8.0.7 which was released today.