Jump to content

Do i have to run update as "ADMIN" ?


Recommended Posts

Hi !

 

Do i have to run updates "as ADMIN" ?

With a USER-account, when i try to update i get:

 

"An error has occurred. Please report this issue to our support team
(include the content of all error message(s) and code(s) in your submission).
PROGRAM_ERROR_UPDATING (5,0, MBAMFiIeIO: :WriteFile)

 

Access is denied.
"

Link to post
Share on other sites

Hi, hackerman1:

 

It might help to know a bit more information:

  • is it MBAM Free or PRO?
  • what is your Windows OS version (XP/Vista/7/8)?
  • what other security programs (antivirus, firewall, etc) are you running?

 

In the interim...

 

One of the staff will correct me if I am wrong, but YES, you do have to run updates from an account with ADMIN privileges.

  • In Vista/7, you can right-click the MBAM desktop shortcut or in your start menu and click "Run As Administrator". I presume there is a similar process for Win8.

 

If you are running MBAM PRO you can set up scheduled tasks (scans and updates) from your admin account.  Any scheduled tasks will then run regardless of which type of user account is active.

 

This forum thread is a bit old. But I am pretty sure the replies from our forum Admin, Exile360, are still valid: http://forums.malwarebytes.org/index.php?showtopic=101395

 

There is more about updating errors caused by security software in this topic: I'm getting an error when I update, ERROR_UPDATING_(numeric code &\or note)

 

 

Please let us know if this resolves your issue.

 

Thanks!

 

daledoc1

Link to post
Share on other sites

Hi !

 

Sorry, i should have said which version it was.

It´s MBAM-PRO, i´m testing the latest version together with the latest version of Emsisoft AntiMalware (EAM), with mutual exclusions.

 

Yes, i know how to setup scheduled updates, but i was referring to manual updates by right-clicking on the taskbar-icon.

 

I´m running Windows Server 2008-R2 with SP1, although I don´t think it matters....

Link to post
Share on other sites

Hi:

 

Thanks for the update.

 

I'm not personally familiar with Windows Server, so we'll need to wait for an expert or staff member to weigh in.

However, I assume that it's still necessary either to schedule the updating task from an Admin Account, to use an Admin Account to manually update, or to "Run As Administrator" in order to update.

 

If you're still getting error messages with Admin rights, then I would suggest that you please check out that KB topic in my earlier reply, to make sure your AV/firewall isn't blocking updates.

 

Alternatively, since you are running PRO, you may wish to obtain free help from the support team.

As your post suggests that this is a business/corporate/commercial or similar installation, you can open a support ticket here: Contact Corporate Support

The team will assist you for free with getting your updating issues sorted. :)

 

The staff/experts may have some additional advice, as well.

 

Thanks very much for your patience,

 

daledoc1

Link to post
Share on other sites

Yes you will need to use "Run as administrator" on the free version.

 

Using an $800 Server as a workstation is wasting about $600 though and any type of business use does require a business license, the consumer free version cannot be used in such a scenario.

 

I´m not using the FREE version.

You seem to have missed what i posted above:

" It´s MBAM-PRO, i´m testing the latest version together with the latest version of Emsisoft AntiMalware (EAM), with mutual exclusions."

 

Who said anything about a server ?

I´m running WS2008-R2 on my laptop....

And it´s no "business use", it´s personal.

Link to post
Share on other sites

  • Root Admin

Well by that name it would appear to be either Web Server 2008 or simply Windows Server 2008 but it is not Windows 7 by that name is all I'm saying.
At the Professional Developers Conference (PDC) 2008, Microsoft also announced Windows Server 2008 R2, as the server variant of Windows 7.

 

If you can run the following scan we can determine for sure what you are running and why it's not updating automatically.

 

Please create an mbam-check log:
 

  • Download mbam-check.exe from here and save it to your desktop
  • Double-click on mbam-check.exe to run it, it should then open a log file
  • Please do not copy and paste the entire contents of the log into your next post, instead please attach the log CheckResults.txt file which should now be located on your desktop to your next post

 

 

Windows 7 editions


Windows 7 Starter
Windows 7 Home Basic
Windows 7 Home Premium
Windows 7 Professional
Windows 7 Enterprise
Windows 7 Ultimate

 

Special-purpose editions

N and KN editions
VL builds work with VLKs (volume license keys)

 

Upgrade editions

Family Pack
Windows 7 is available as a Family Pack upgrade edition in certain markets, to upgrade to Windows 7 Home Premium only

Anytime Upgrade editions


Starter to Home Premium.
Starter to Professional
Starter to Ultimate1.
Home Premium to Professional.
Home Premium to Ultimate.
Professional to Ultimate

Derivatives

Windows Thin PC
Embedded versions

Windows Server Editions

 

Windows 2000 Server (February 2000)
Windows Server 2003 (April 2003)
Windows Server 2003 R2 (December 2005)
Windows Server 2008 (February 2008)
Windows Server 2008 R2 (July 2009)
Windows Server 2012 (September 2012)
Windows Server 2012 R2 (TBA)
Windows Home Server
Windows MultiPoint Server

Comparison of Microsoft Windows versions

History of Microsoft Windows
 

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
  • 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.