Jump to content

Why Win7 always ask for user account!!


ZeroCold
 Share

Recommended Posts

Hi ZeroCold - Welcome to Malwarebytes.org

That is normal and by design when you start the scanner manually because the program has the ability to make global changes.

In the Pro version, it will update and scan automatically without displaying that prompt.

Even so, you will still be prompted if you start the scanner manually.

Link to post
Share on other sites

Hi ZeroCold - Welcome to Malwarebytes.org

That is normal and by design when you start the scanner manually because the program has the ability to make global changes.

In the Pro version, it will update and scan automatically without displaying that prompt.

Even so, you will still be prompted if you start the scanner manually.

Mine is pro version

and it still say ask for that

Link to post
Share on other sites

Just a follow up with some further information on UAC in Windows 7 to help you understand better.

Note that MBAM falls into the category of programs that perform administrative tasks so when you start the scanner manually, you are prompted. When you run the scanner automatically (Pro version only,) the privilege to start it is automatically elevated as well and you won't get a prompt.

What's New in User Account Control

Before the introduction of User Account Control (UAC), when a user was logged on as an administrator, that user was automatically granted full access to all system resources. While running as an administrator enabled a user to install legitimate software, the user could also unintentionally or intentionally install a malicious program. A malicious program installed by an administrator can fully compromise the computer and affect all users.
By default, standard users and administrators access resources and run applications in the security context of standard users. When a user logs on to a computer, the system creates an access token for that user. The access token contains information about the level of access that the user is granted, including specific security identifiers (SIDs) and Windows privileges.

When an administrator logs on, two separate access tokens are created for the user: a standard user access token and an administrator access token. The standard user access token contains the same user-specific information as the administrator access token, but the administrative Windows privileges and SIDs have been removed. The standard user access token is used to start applications that do not perform administrative tasks (standard user applications).

When the user runs applications that perform administrative tasks (administrator applications), the user is prompted to change or "elevate" the security context from a standard user to an administrator, called Admin Approval Mode. In this mode, the administrator must provide approval for applications to run on the secure desktop with administrative privileges. The improvements to UAC in Windows 7 and Windows Server 2008 R2 result in an improved user experience when configuring and troubleshooting your computer.

Guided Help: Adjust User Account Control settings in Windows 7

UAC is actually a good thing as it prevents a lot of things from happening in the background that you may not have been aware of. It doesn't annoy me at all.

Link to post
Share on other sites

  • 2 weeks later...

Hello ZeroCold:

Some of Malwarebytes' Anti-Malware's executables are not meant to run with administrative privileges, particularly when it comes to the protection module. Please go to the Malwarebytes' Anti-Malware program folder in C:\Program Files or C:\Program Files (x86) if using an x64 version of Windows then do the following:

  1. Right-click on mbamgui.exe and select Properties
  2. Click on the Compatibility tab and uncheck the box next to Run this program as an administrator and click Apply then click OK
  3. Right-click on mbamservice.exe and select Properties
  4. Click on the Compatibility tab and uncheck the box next to Run this program as an administrator and click Apply then click OK

These executables do not need to be set to run as admin because mbamservice.exe already runs with SYSTEM level privileges as a service, which automatically bypasses User Account Control and actually gives the protection module higher than administrative privileges

Hope this resolves your issue

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.