MBAM doesn't auto start for standard/non-admin user in Windows 7

[superaj]

We have MBAM Pro/Premium installed. I have been working on this all morning and can't seem to get MBAM to start in a standard user/non-admin user account.  Here's what I've tried from scouring the forum and Google:

 

-uninstall MBAM with mbam-clean, re-install under the standard user

-uninstall MBAM with mbam-clean, re-install under an admin user

-As standard user, add MBAM to startup folder in the Start menu, set the shortcut and mbam.exe to run as administrator

-Toggle the auto-start settings in MBAM under an admin account

 

MBAM autostarts just fine when logging in as an admin user, but it will not auto-start for the standard user.  We have to manually start it from the Start menu and provide the admin password.

 

Any help is appreciated.

[1PW]

Hello superaj and

We apologize for the delay in responding to your post. Let's start by cleaning and then gathering some diagnostic information from a proper environment.
 
Please delete any and all previous copies of the four (4) files listed below from the user accounts.
 
Please login to the Administrator's account and repeat the deletion of any and all of the below four (4) files.

While logged in as the Administrator, please download and save fresh copies of the following four files only to the system Administrator's desktop:

• mbam-clean-2.1.1.1001.exe
• mbam-setup-2.0.3.1025.exe
• Farbar Recovery Scan Tool
• mbam-check-2.1.1.1001.exe

In the following steps, please only execute the above four files via "Run as administrator".

• Please try the following and let us know if this corrects your issue: MBAM Clean Removal Process 2.x. Please do not change any settings after MBAM2 is installed.
• If that does not correct the issue, then please read the following and individually attach (do not cut, paste or compress) the 3 requested logs in a reply to this thread: Diagnostic Logs.
• The 3 files, from Step 2, to be individually attached from your desktop are: CheckResults.txt, FRST.txt and Addition.txt. Please do not Copy and Paste or compress them into your reply.

Please let us know the status of your issue in a reply to this sub-forum thread.

Thank You.

[superaj]

I tried step #1 above, which did not fix the problem.  I had already done this previously as mentioned in my original post.

 

Following the instructions in step #2 and #3, I have attached the diagnostic logs here.

 

Please advise.

Addition.txt

CheckResults.txt

FRST.txt

[superaj]

Just wondering if there's an update for this issue?

[superaj]

Any update to this issue would be really helpful...

[1PW]

Hello superaj:

 

Please allow me to sincerely apologize for the prolonged period for analysis of your report files.

 

In sifting through the hashes in one of your reports, unexpected results suggest a possible faulty install, or corruption.

 

Please undo any & all system changes you may have tried while troubleshooting.

 

After a fresh, cold start into the normal boot mode, and logging in as only the Administrator, please completely delete all previous downloads of: mbam-clean, mbam-setup, mbam-check, FRST64, C:\FRST, and their output reports.

 

Please disable any and all installed/running anti-virus applications. (MSE + ?)

 

Download (only from Malwarebytes' servers) and save, only to the Administrator's desktop (C:\Users\Administrator\Desktop), the same above executables. Then, using the above MBAM2 Clean Removal Process 2.x procedures, please run mbam-clean-2.1.1.1001.exe two times with the mandatory system restarts at the end of each execution. After logging back in as the Administrator again, run mbam-setup-2.0.3.1025.exe. When appropriate, please allow MBAM2 to come up and enter your license ID/Key for elevation to Premium, and update to the current database, then run a Hyper Scan to completion.

 

Please re-enable MSE.

 

We are only establishing a known good install of MBAM2 at this point.

 

I wish to re-emphasize that your actions take place while only booted into the normal boot mode and from only the Administrator's account using fresh files saved only to the Administrator's desktop.

 

After having accomplished the above, please run the three diagnostic applications and attach their output diagnostic logs to your next reply to see if a proper install/activation was achieved. Make no system changes and only passively check to see if a Limited User Account (LUA) sees MBAM2 running without further interaction. We can continue from there.

 

Thank you.