Jump to content

MBARW BETA 8, v.0.9.17.661 causes account failure on Startup


siliconman01
 Share

Recommended Posts

This applies to Windows 10x64 Pro V14393.321 (fully updated) on a home built system consisting of an ASUS Maximus VIII Extreme MB, 32 gbytes of DDR4 3200 G.Skill Rip Jaws RAM, a 512 gbyte Samsung 950 Pro NvME M.2 SSD, a 512 gbyte Samsung 850 Pro SSD, EVGA GeForce GTX 980 Ti graphics card, Intel I7-6700K Processor, 3 monitors.  

When I boot up on this fast, fast system with MBARW Beta 8, v0.9.17.661, Windows cannot load my local account and loads the Default account.  I have to restart and then it will load my local account.  If I uninstall MBARW, this does not occur and my system boots up as it should.  I have attached a copy of System Info for your reference.  This is the first time I've installed/tested MBARW beta versions since ~Beta 4, so I don't know if this is a new issue caused by Beta 8 on this system. 

SysInfoSiliconman01.zip

Link to post
Share on other sites

Hello siliconman01:

Let's see if anything significant is revealed within the following archives:

Using the native Windows built-in zip utility, please create the following, separate, .zip (not .7z or .rar) archive files for MBARW developer team analysis:

                                 "C:\ProgramData\Malwarebytes\Malwarebytes Anti-Ransomware\"
                                 "C:\ProgramData\Malwarebytes\MBAMService\logs\"
                                 "C:\ProgramData\MalwarebytesARW\"

Please attach the .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.

Edited by 1PW
Link to post
Share on other sites

6 hours ago, 1PW said:

Hello siliconman01:

Let's see if anything significant is revealed within the following archives:

Using the native Windows built-in zip utility, please create the following, separate, .zip (not .7z or .rar) archive files for MBARW developer team analysis:

                                 "C:\ProgramData\Malwarebytes\Malwarebytes Anti-Ransomware\"
                                 "C:\ProgramData\Malwarebytes\MBAMService\logs\"
                                 "C:\ProgramData\MalwarebytesARW\"

Please attach the .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.

Here are the requested zip files.  Please note that this problem occurs mostly when the computer is rebooted from a full shutdown, not a restart.  A restart seems to work properly.   

Malwarebytes Anti-Ransomware.zip

MalwarebytesARW.zip

MBAMService.zip

Link to post
Share on other sites

Note that the requested zips below are located inside folder  "C:\ProgramData\MalwarebytesARW\"  on version 0.9.17.661 Beta 8, not in folder C:\ProgramData\Malwarebytes

                                 "C:\ProgramData\Malwarebytes\Malwarebytes Anti-Ransomware\"
                                 "C:\ProgramData\Malwarebytes\MBAMService\logs\"

Link to post
Share on other sites

The picture named "BootAccountFaliure.png" is the boot failure screen that is being caused by the installation of MBARW Beta 8.  

My primary AV is Norton Security V22.8.0.50 (latest release).  I have Boot Time Protection turned off in its settings.  However, it would not surprise me to learn that there is conflict occurring between these two security programs.  JMO:huh:

BootAccountFailure.PNG

NormalBoot.PNG

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.