1PW

Spam Hunters
  • Content count

    7,596
  • Joined

  • Last visited

1 Follower

About 1PW

  • Rank
    1PW
  • Birthday 05/22/1940

Profile Information

  • Interests
    Agnes - loved forever.

Recent Profile Visitors

32,077 profile views
  1. Hello coldone: Available data strongly suggests a false positive, and if it has not already been done, you may wish to make the following temporary full pathname file entry in MBARW GUI Dashboard -> Exclusions: C:\Program Files\logitech gaming software\lcore.exe Reference: https://www.virustotal.com/en/file/662ea0ee64e94ce6eff742c7e2230646c7e246690772dd666775cd68c34a5534/analysis/ Signed At any time, a MBARW development team member, QA team member or Staffer may request the above temporary exclusion be altered/deleted. Thank you for beta testing MBARW and your valuable feedback.
  2. Hello tedwillard4309 and Please create the following zipped archives for MBARW developer team analysis: Create a .zip archive of the directory C:\ProgramData\Malwarebytes\Malwarebytes Anti-Ransomware\ Create another .zip archive of the directory C:\ProgramData\Malwarebytes\MBAMService\logs\ Please attach the zipped archives to your next reply. Thank you for beta testing MBARW and your valuable feedback.
  3. Hello Frankmeister and 1. The presence of the MBARW Beta icon in the Windows system's taskbar, just after system startup, is normal at this early stage of project development and affords the user an opportunity quickly verify the state of Anti-Ransomware protection. After verification, the MBARW Beta taskbar icon may then be dismissed at any time. 2. The MBARW Beta development team monitors this sub-forum, and they are also aware of similar suggestions for the system tray icon. 3. To assist investigation of the system's CPU usage, please create the following zipped archives for MBARW developer team analysis: Create a .zip archive of the directory C:\ProgramData\Malwarebytes\Malwarebytes Anti-Ransomware\ Create another .zip archive of the directory C:\ProgramData\Malwarebytes\MBAMService\logs\ Please attach the zipped archives to your next reply. Thank you for beta testing MBARW and your valuable feedback.
  4. Hello TheBBG: You may actually send the logs now. Please create the following zipped archives for MBARW developer team analysis: Create a .zip archive of the directory C:\ProgramData\Malwarebytes\Malwarebytes Anti-Ransomware\ Create another .zip archive of the directory C:\ProgramData\Malwarebytes\MBAMService\logs\ Please attach the zipped archives to your next reply. Thank you for beta testing MBARW and your valuable feedback.
  5. Hello nitrousable: The analysis experts are going to want to start off seeing several diagnostic report files: Please read the topic Diagnostic Logs and then individually ATTACH the 3 requested logs in your next reply to this thread only. The 3 files, from Step 1, to be individually ATTACHED from your desktop are CheckResults.txt, FRST.txt and Addition.txt. Please do not Zip or Copy and Paste them into a reply. Please do not alter, any FRST categories as the configuration is well suited for this forum. Thank You.
  6. Hello MichaelJFoxx and Please carefully read the locked and pinned topic in this sub-forum, How to report a False Positive and for developer analysis, kindly attach the 3 requested .zip archives to your next reply in this thread. You may restart the system in question and the restore the application from quarantine. If an exclusion has not already been entered, a temporary exclusion entry might then be made available to prevent a re-occurrence for your individual system. Thank you for beta testing MBARW and your feedback.
  7. Hello AlexCottle and It is disappointing to read your Consumer Beta testing system is having MBARW Beta issues but each computer is unique. Problems that seem "the same" frequently are not. The same is true for solutions. Solutions may often need to be individualized for your unique testing system. It is less confusing for everyone if a "One Member Per Topic" policy is adhered to instead of posting to the topic of another member. Development Team Members, Staffers, and Helpers will be able to more easily provide both you and the OP/Topic Starter, with individualized assistance. Please start a NEW, and SEPARATE topic by left-clicking this >>Start New Topic<< link now. Thank you always for your patience and understanding.
  8. Hello mbe57 and It is disappointing to read your Consumer Beta testing system is having MBARW Beta issues but each computer is unique. Problems that seem "the same" frequently are not. The same is true for solutions. Solutions may often need to be individualized for your unique testing system. It is less confusing for everyone if a "One Member Per Topic" policy is adhered to instead of posting to the topic of another member. Development Team Members, Staffers, and Helpers will be able to more easily provide both you and the OP/Topic Starter, with individualized assistance. Please start a NEW, and SEPARATE topic by left-clicking this >>Start New Topic<< link now. Thank you always for your patience and understanding.
  9. Hello wahone and Even though MBARW Beta may have stopped a ransomware positive, the following data would be valuable for the MBARW Beta development team: Please carefully read the locked and pinned topic in this sub-forum, How to report a False Positive and for developer analysis, kindly attach the 3 requested .zip archives to your next reply in this thread. If an exclusion has not already been entered, a temporary exclusion entry might then be made available to prevent a re-occurrence for your individual system. Thank you for beta testing MBARW and your feedback.
  10. Hello gogiburn: Please carefully read the locked and pinned topic in this sub-forum, How to report a False Positive and for developer analysis, kindly attach the 3 requested .zip archives to your next reply in this thread. If an exclusion has not already been entered, a temporary exclusion entry might then be made available to prevent a re-occurrence for your individual system. Thank you for beta testing MBARW and your feedback.
  11. Hello exegesis and Please create the following zipped archives for MBARW developer team analysis: Create a .zip archive of the directory C:\ProgramData\Malwarebytes\Malwarebytes Anti-Ransomware\ Create another .zip archive of the directory C:\ProgramData\Malwarebytes\MBAMService\logs\ Please attach the zipped archives to your next reply. Thank you for beta testing MBARW and your valuable feedback.
  12. Hello Wells15: In addition to the Diagnostic Logs that AdvancedSetup has requested, please consider including the following: Create a .zip archive of the directory C:\ProgramData\Malwarebytes\Malwarebytes Anti-Ransomware\ Create another .zip archive of the directory C:\ProgramData\Malwarebytes\MBAMService\logs\ Please attach the zipped archives to your next reply. Thank you for beta testing MBARW and your valuable feedback.
  13. Hello gsheston: Unfortunately of the three (3) requested diagnostic report files, FRST.txt seems to be completely missing and the mbam-check.txt file is severely truncated. Please consider searching for the missing FRST.txt file and check if the mbam-check.txt file was completed properly. Please re-post when you are able. Thank you.
  14. Hello RRin: Thank you for the archive files. I apologize for repeating what I have posted before but, the MBARW Beta development team monitors this sub-forum, and they are aware of similar reports for which they are working on a solution. Thank you for participating in the MBARW beta testing program.
  15. Hello temp_9999: The MBARW Beta development team monitors this sub-forum, and hopefully value will be derived from the archives. Thank you.