Jump to content

MBAR disables when I log off one Windows user


pizzahut
 Share

Recommended Posts

I have two Windows users on my PC.

Login to 1st, MBAR is fine. Login to 2nd, still ok. Switch between users, still in order.

Now when I log off the 1st user, MBAR disables itself and I have to fix it every time I do this.

This is a relatively fresh install as I had uninstalled the previous beta before installing the new one.

The 1st user used to be admin, but have changed it to a standard one now. 2nd user is admin.

Link to post
Share on other sites

Hello pizzahut:

Using the native Windows built-in zip utility, please create the following 2, separate, .zip archives for MBARW developer team analysis:

1. Create only a .zip archive (not .7z or .rar) of the directory C:\ProgramData\Malwarebytes\Malwarebytes Anti-Ransomware\
2. Create only a separate .zip archive (not .7z or .rar) of the directory C:\ProgramData\Malwarebytes\MBAMService\logs\

Please attach the 2 .zip archives to your next reply.  Thank you for your beta testing contribution to the Malwarebytes Anti-Ransomware (MBARW Beta) project and your valued feedback.

Link to post
Share on other sites

Hello pizzahut:

Let's make sure the client files have not become corupted since the last install.  Rather than a simple re-install of MBARW Beta7, please consider a clean install of MBARW Beta7:

1. Close all open user applications followed by a conventional Windows based uninstall of Malwarebytes Anti-Ransomware through the Windows system Control Panel.
2. If MBARW Beta7 was uninstalled successfully, the following sub-directories will have been deleted from a typical Windows 10 x64 system:

                         C:\Program Files\Malwarebytes\
                         C:\ProgramData\Malwarebytes Anti-Ransomware\
                         C:\ProgramData\MBAMService\

3. If any of the above directories remain, please delete them manually.  If necessary, any remaining/uninstalled directory must be deleted in the Windows Safe mode.
4. Execute a conventional Windows restart to the Normal Windows boot mode and log-in through an Administrator's account. <===IMPORTANT!
5. Using an Administrator's account only, download a fresh MBARW_Setup.exe file and save to the Administrator's Desktop from the Malwarebytes Anti-Ransomware BETA 7 Now Available topic.
6. Right-click the saved MBARW_Setup.exe file and left-click RunAsAdmin.jpg  Run as administrator from the context menu and continue.
7. Upon a successful installation, please restart the computer in a conventional manner to the Windows Normal boot mode.

Please reply to your topic with the status of your reported issue.  Thank you for beta testing MBARW and your valued feedback.

 

Link to post
Share on other sites

Hello pizzahut:

Thank you for posting the above-attached archives.

Within the system in question, and using any of its Internet browser(s) of your choice, please go to and closely follow Brink's procedure at:

      Option Two: To Find Windows Build Number in About Windows

If you are unable to reply by posting a preferable screen grab of the "About Windows" result, please use the greatest care in reporting the full and complete Version detail line for that system.

Thank you again for your MBARW Beta testing cooperation.

Link to post
Share on other sites

Hello pizzahut:

In anticipation of analysis of your MBARW Beta7 observations by high level Malwarebytes development personel and others, please generate the following diagnostic report files:

  1. Please read the locked/pinned topic Diagnostic Logs and then individually ATTACH the 3 requested logs in your next reply to this thread only.
  2. 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 kindly pizzahut.

Link to post
Share on other sites

Hi pizzahut--

Many thanks for the logs and details about what you're seeing.  Just wanted to let you know that our QA and Dev teams are looking into this issue.  We're still investigating, but hope that this can be addressed in an update / future beta.

Thanks for testing out the beta!

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
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.