Jump to content

2 errors "Updates are not current" and "Unable to contact license server..."


Recommended Posts

Main OS: Windows 7:Pro (OEM)
Main Anti-Virus: ESET Smart Security
MBAM Premium user experiencing 2 issues.


1. Error: "Updates are not current" with version 3.0.6.
2. I manually updated to 3.1.2 (using mb3-setup-consumer-3.1.2.1733-1.0.141-1.0.2092.exe)
and received the error "Unable to contact license server. Check your network settings or contact your system administrator for help."
(When the program said I was a licenced/premium user, this error would constantly pop-up after exiting the error message.)

a. I've uninstalled the MBAM with mb-clean-3.1.0.1013 (restart included) (Did not clean anything with CCleaner just in case that'd mess with registry keys).
b. I've Reinstalled to v3.1.2 but the licence reverted to "FREE user", and I'm still receiving the error from #2 about the license server/network settings.
(The error pops up at first launch after install and continues to pop up more than once (about 3 times). Same thing on application boot up.)

How can I go about fixing this, and go back to a premium user with my licence key? (The current existing issue is #2 but I don't know if #1 will re-occur, nor how to prevent it in the future.)

mb-check-results.zip

FRST.txt

Addition.txt

Link to post
Share on other sites

Hello @Dacc

Can you try running the MB-Clean tool and check if that works.

Tool can be found at : https://downloads.malwarebytes.com/file/mb_clean

1. After downloading the tool run the tool.
2. Tool will automatically clean up the older  product and will ask you for a restart.
3. Restart your system and then the MB-Clean tool will prompt you to re-install the latest product .
4. Click on "Yes" to reinstall MB 3.×.
5. Now you will have the clean install.

Does that help.

Link to post
Share on other sites

Can you try resetting your HOSTS file. There's a lot of entries in there that we can't see, and the majority of the time these issues are caused by the HOSTS file blocking access to our servers. Instructions for resetting that can be found here: https://support.microsoft.com/en-us/help/972034/how-to-reset-the-hosts-file-back-to-the-default

Link to post
Share on other sites

6 hours ago, dcollins said:

Can you try resetting your HOSTS file.

dcollins,

I've reset my hosts file. I was using an out-dated list from someonewhocares.org but the problem still remains.
I cleared my windows files with Ccleaner and restarted. I thought issue 2 (unable to contact license server) was solved as the error it didn't immediately pop up, but when I go to settings > account the program briefly freezes before switching to the account tab and error 2 shows up again.

This Network Settings error can be re-produced each time I switch away from, and back to the account tab.

Edited by Dacc
Link to post
Share on other sites

The link shows a white page with the text "OK"

Side note: when FRST.exe automatically scans for updates, Farbar gives the error "failed to update (1)"  
This check for an update failing might be the same thing giving me issues with MBAM.
I've manually updated and ran the scan using the updated version 2017-06-28.

FRST.txt

Link to post
Share on other sites

You're on to something here.
Under ESET I've done:
Pause Protection > But it's had no effect. https://keystone.mwbsys.com/ still gives blank page with "OK".
Pause Firewall > gives blank page with "OK".

However, with the firewall disabled. If I click the "My Account" tab the "unable to contact license server" error doesn't pop up, and it switches to said tab without freezing MBAM.
I've used my licence key again, I'm not sure if this used up my last key usage (3 of 3 uses); I'm able to check for updates, making The "updates are not current" disappear.
Re-Enabling the firewall makes the license server error pop up again.

I guess something needs to be added to ESET's firewall exclusion?

Edited by Dacc
Link to post
Share on other sites

Thank you dcollins. This is a big help. I'm using ESET 10.0.390.0.

I've received an email from support saying to allow (in ESET) a white-list to firewall rules in the direction of either "out" or "both" in order to work.
I don't think adding all of these are necessary to fix the 2 issues I've been having but mbamservice.exe should be added.

C:\Program Files\Malwarebytes\Anti-malware\assistant.exe
C:\Program Files\Malwarebytes\Anti-malware\mbam.exe
C:\Program Files\Malwarebytes\Anti-malware\mbampt.exe
C:\Program Files\Malwarebytes\Anti-malware\mbamservice.exe
C:\Program Files\Malwarebytes\Anti-malware\mbamtray.exe
C:\Program Files\Malwarebytes\Anti-malware\mbamwsc.exe
C:\Windows\System32\drivers\mbam.sys
C:\Windows\System32\drivers\mwac.sys
C:\Windows\System32\drivers\mbamswissarmy.sys
C:\Windows\System32\drivers\mbamchameleon.sys
C:\Windows\System32\drivers\farflt.sys
C:\Windows\System32\drivers\mbae64.sys (64-bit only)
C:\Windows\System32\drivers\mbae.sys (32-bit only)

Also, in that link you provided, setting ESET's "Filter mode" to automatic (in the link you provided) shed some light on why I might've been having this issue.
Mine was set to "Interactive mode". This issue has been resolved. Thanks again!

Edited by Dacc
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.