Jump to content

unable to access update server


Recommended Posts

Using latest version of MWB. Not premiium version however. Anyway, I get the above msg when doing a manual update and then strangely, it updates to the current date. I'm not sure if the update has happened or not. Any thoughts would be appreciated. Thanks.

Link to post
Share on other sites

Hello Dublin70:

 

What you have related would be the expected behavior if logged in through a Windows Limited User Account (LUA).

 

However, if logged in through an Administrator's account, further investigation is indicated.

 

Thank you.

Link to post
Share on other sites

Well well - that must be something new as I have always done manual updates from that account (LUA) w/o this happening. I went to my admin acct and sure enough, no problem. With all this in mind, can I trust that the update has been completed (on LUA) even though initially, I receive above message, followed some minutes later by the correct date as to update. Thanks very much for your input.

Link to post
Share on other sites

Hello Dublin70:

 

What you have related would be the expected behavior if logged in through a Windows Limited User Account (LUA).

 

However, if logged in through an Administrator's account, further investigation is indicated.

 

Thank you.

 

Is there a reason why it does that? I am also experiencing the same problem and through a LUA, but this has only started happening recently.

Link to post
Share on other sites

Hi:

 

Hello cruise_the_vistas:

 

A Malwarebytes staff member will be requested to respond to your query.

 

Thank you.

 

FWIW, it appears that @cruise_the_vistas is already working with @tetonbob here: https://forums.malwarebytes.org/index.php?/topic/170748-malwarebytes-keeps-switching-to-premium/

 

<just mentioning it, so that @Dublin70's thread doesn't end up being inadvertently hijacked...>

 

Cheers,

Link to post
Share on other sites

@Tabvla and @cruise_the_vistas:

 

Thanks very much for your feedback.

The Malwarebytes staff members are aware of your reports and are conducting testing to replicate the behavior.

There's no need to cross-post in threads started by other users, especially if you have your own threads.

It can contribute to confusion for everyone, including the OPs, and especially since there are many, many different, unrelated causes of "updating" problems.

 

Please be patient and wait for a reply in your own threads about the behavior you have reported.

 

 

@Dublin70:

 

Please be patient & wait for a reply from the staff here in this, your thread, when they have more information.

 

 

Thanks to everyone for your patience and understanding,

Link to post
Share on other sites

Dale thanks for your feedback.

 

This is not a "problem" as such.  If the Malwarebytes Team have decided to change the behaviour, that is fine - but it would be helpful if a note was posted to that affect.

 

Normally, I would agree with Ron Lewis (AdvancedSetup) that allowing Standard Users to make changes to programs is a very bad idea.  However, the one exception to that rule would I think be allowing Standard Users to update the Database of security software - and I mean the Database ONLY.

 

I cannot see any way that someone logged-in as a Standard User could do any harm to any system by simply updating the Database.

 

For normal daily work I always login as a Standard User - this is good practice.  I only ever login as an Administrator when I need to do Admin tasks.

 

T.

 

Link to post
Share on other sites

  • Root Admin

I don't control how the program is written or managed - I'm only saying how it "should" be run and there are NO exceptions period. No LUA should be allowed to add, change, or remove ANYTHING that can potentially affect either another user account or the entire system. As an example, let's say that you as the System Administrator only update the database once a day at noon. Then you run some tests to verify that the update caused no problems. Then a LUA comes along at 3 PM and updates MBAM database but this time there is a FP that removes a valid OS file by mistake. You as the System Admin have no idea the user did this and though you may eventually track it down to MBAM you're not going to initially blame it because you already updated and tested at noon with no issues. Another scenario perhaps is that the LUA updates but for some reason has network issues or other and the database gets corrupted. Now the program has no database to run with and the user won't report it and often wont' notice that the program is not working. These are extreme examples but the point is one should never allow LUA to affect other user profiles or the entire system period. Now, that said.. I can tell you that the program is not locked down like that and it does allow a LUA to do just about anything in my testing. LUA can add exclusions, can delete quarantine files, etc, I still need to confirm if they can actually update the database or not as I was not able to test that last night.

Link to post
Share on other sites

Hmmm.... yes, I think Ron makes a good point.  In a corporate environment the scenario he describes is exactly what drives IT managers crazy.

 

A Home or Small Business environment is rather different.

 

But I can understand that to code for different behaviour depending on the type of user would probably be an unnecessary complexity.

 

So......  if the behaviour of MBAM 2.1.8.xxxx has changed from 2.1.6.xxxx then the Malwarebytes Team should post a notice to that affect.  If this is a "bug" and not an intended behaviour change then the Team should say so.  Currently users don't know whether this is a bug or an intended behaviour change.

 

T.

 

Link to post
Share on other sites

  • Root Admin

Difficult to stay on top of these as there are a few different, yet similar posted topics. As you're one of the ones that have posted on this subject as well I did post the following in the other topic.

 

Okay  I have confirmed that a Limited User Account cannot update the database. Though they can do pretty much just about anything else with the program.

I cannot duplicate yet this issue of the Web protection module being broken by a LUA or Admin account stopping or updating, etc. so if in fact it is an issue I'll have to review that further to see if I can duplicate the issue or not.

 

At this time version 2.18 cannot update the rules database using a Limited User Account. It must either be run by the internal scheduled task (highly recommended method) or by an Admin level account if running an update check manually. Limited User accounts will try and fail with the AKA Domain error.

 

However initial testing under 2.16 seemed to operate in the same fashion but I was not specifically testing for LUA database updates in 2.16 - I will install and test on a system and try to verify if 2.16 has changed in this capacity or not.

 

https://forums.malwarebytes.org/index.php?/topic/170417-unable-to-access-update-server/

Link to post
Share on other sites

  • Root Admin

No, we don't typically merge them as often the reported issues often can have underlying different causes and not easy to help individual users. Though it's not locked down in this forum it's best to stay in your topic so that if something is different for Dublin70 they can get individual support for it. Yes it's very possible the issue is the same but not for sure at this time.

 

Thanks

Link to post
Share on other sites

After reading Ron's post of today, I still do have the question: even though my LUA cannot update the database manually, a few seconds after it says it cannot, it is updated to today's date. Can I trust that it has been updated or should I just go to admin acct and do it to make sure. I sure would like to be lazy and just trust that it is current but will not if you advise against. Thanks very much for all help.

Link to post
Share on other sites

  • Root Admin

At this time I personally cannot confirm this behavior Dublin70 - Our internal QA Team and Development Team though has been alerted to this behavior and are also starting to investigate it on their end. At this time I would recommend using an Admin level account to ensure the updates. If the File or Web blocker shows in the task tray as not being enabled at any point though please let us know.

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.