Jump to content

Recommended Posts

  • Staff

In the Finder, choose Go to Folder from the Go menu, then enter the following path into the window that opens:

/var/log/install.log

Then click the Go button.

In the folder that opens, an install.log file should be selected. Double-click that install.log file to open it in the Console application.

Next, search for "sudoers" (without the quotes). If you find any lines in that log file saying something about "no valid sudoers" being found, you have a problem with your system that is interfering with the installation. (Note that there may be other messages relating to the sudoers file that do not represent a problem.)

Unfortunately, a damaged sudoers file is not an easy thing to fix, and the best way to do it is to simply reinstall the system. Make sure to make a good set of backups, just in case something goes wrong. Once you've done that, see the following:

https://support.apple.com/HT204904

Follow those instructions to reinstall the system, skipping the section on erasing the hard drive. This will just install a new, fresh system on top of your current one, fixing anything that's broken (like the sudoers file).

If you don't see any of these errors relating to the sudoers file, compress that install.log file (control-click the file and choose Compress "install.log"), then send me a direct message, and attach the install.log.zip file that will be created on your desktop.

Link to post
Share on other sites
  • 3 weeks later...

I can't install on my infected Mac either. It get's as far as "Registering Updated Components" and gets stuck there. See below.

Malwarebytes shows up in Apps but when I double click it, it says "background service is offline, please contact support".

Thank you!

Screen Shot 2017-11-13 at 1.12.03 PM.png

Edited by lk212
New info
Link to post
Share on other sites
  • Staff

Be aware that, on some systems, the installer can stay on that step for a couple minutes. Please be patient and let it finish. If you forced the installer to quit prematurely, you'll need to run the installer again.

If you let it run for much longer than that with no results, please let me know.

Link to post
Share on other sites
  • Staff

Without seeing the install.log file that I requested previously, I can't comment. However, I can say that in each and every case I've seen where the installer has failed, it has been caused by a problem with the system, not a problem with Malwarebytes. 100% of the time. I'm not saying that it's impossible that we could have a bug, but I'd need to see the install logs to know.

What updates are you talking about? Is it Malwarebytes for Mac updates you're having trouble with, or other updates?

Link to post
Share on other sites

Sounds like we had a similar situation, so maybe my solution will help you. I finally called Apple support and they walked me through a bunch of steps including going into library and clearing caches and saved applications state. Turns out Malwarebytes wasn't allowed to completely install so that was the problem. My computer works great after the call with Apple support, including Malwarebytes. The support guy I worked with told me Malwarebytes is what they recommend for use on Macs. I'd say give Apple support a call, I was surprised how helpful they were and what they had me do worked for me. Hope this helps.

Good luck.

Link to post
Share on other sites
  • 1 month later...

I don't mean to hijack this thread, but I cannot install on my MBP either.  I receive the same error message as the initial poster.  The installer hands on "Checking Authorization of Malwarebytes Extension." and then alerts that it could not install.

A few things:

I had MLWB installed before and it worked without issue.  However, I went to uninstall the 1.x version and accidentally used CleanMyMac to uninstall the wrong version.  I thought, maybe it didn't uninstall everything successfully so I located and used the "Remove MalwareBytes.pkg" file for Macs to remove any remnants, restarted, and I am still having the same issue.

MPB running High Sierra 10.13.2

@treedI do have a copy of the install.log that I am going to send you in a PVT message.  Just wanted to let you know here first.

Link to post
Share on other sites
  • 2 months later...

Uhhhh, that's so odd....  Have you checked recently jeromy?  I had to reinstall my OS because that happened to me ... And then I stumbled upon a viruss that Malwarebytes never caught because part of the RTP daemon was somehow missing and dumping errors into the console.  LOL...  It was partally my fault though becausese I fogot to uninstall another scanner first so I'm okay with that...  Even if it did take me an hour or two to recover my apps.  ha..ha.  :o  

:-/

Link to post
Share on other sites
  • 1 month later...

Hi all, almost similar issue about not being able to install on a Mac.  

I have begun getting PUP.Spigot warnings (using Avast, free).  I downloaded Malwarebytes - Mac 3.3.22.1387.pkg but when I try to install it the Mac installer quits unexpectedly.  I am running a Macbook Pro, Retina Mid 2012, i7, 8Gb, NVidia GeForce, and with OS X 10.8.2 (because I am using IBM Notes it has been easier not to upgrade).

Anyone ideas for a solution?  :(

Link to post
Share on other sites

I'm afraid you can't have it both ways. You can't use such an old OS and expect to be completely malware free. I'm not at all familiar with IBM Notes, but can't you at least run OS X 10.8.5 with Security Update 2015-006 for Mountain Lion?

With that said, the current version of Malwarebytes requires OS X 10.10 or above, so that's why you cannot install it. 

You can try to download and install Malwarebytes Anti-Malware for Mac 1.2.4 if still available, but it's less capable and I don't know how much longer it will continue to be supported with current definitions. Should still be available for download from  https://data-cdn.mbamupdates.com/web/MBAM-Mac-1.2.4.584.dmg.

Link to post
Share on other sites

Thanks for a prompt response.  You're right, of course, but everything was fine until just this morning.  

The problem only manifests itself while using Chrome; and Avast warning pops up every minute or so about one PUP or AdW.  When Chrome is not running, not an issue.  I will try 1.2.4 as you suggest, and perhaps with the additional info you might have another.

The machine still performs well so it's perhaps time to bite the bullet and upgrade the OS (and all other outdated programmes)  I only mainly use the machine for IBM Notes hence the long overdue upgrade - but its the installation and functioning of Notes that I know is where I'll face hassles.

Link to post
Share on other sites

Did a bit of research and see I missed the memo about Lotus Notes belonging to IBM now. Didn't find enough to know what version works with what OS X, but in general, it would be unusual for a piece of currently supported software not to work with an fully up-to-date Mountain Lion, so again I would think that's the minimum upgrade you should accomplish.

Knowing that it's Chrome tells me that it's highly likely you have a Chrome Extension that's causing the alerts you  are seeing. I believe the current version of Malwarebytes for Mac is better equipped to deal with such things, but still worth giving 1.2.4 a try, I suspect.

As a minimum, take a look at what Chrome extensions you have installed by clicking on the three vertical dots at the end of the Chrome address bar and choose More Tools->Extensions

913652108_ScreenShot2018-05-21at12_36_57AM.png.cb95afb3ec376e441224dcf44100e8c1.png

and remove any that you don't need or recognize. Nothing you find there is required. Everything you find there was installed by you, either by choice or by accident.

Link to post
Share on other sites

Agree with you about the upgrade, but being in Asia the quality of assistance to Upgrade Notes within a mac os environment has not been too hot.
Thanks for the suggestion.  Re CHrome, the only extensions I have are Google Doc extensions:

 

 

extensions.jpg

Link to post
Share on other sites
  • 3 months later...

I was having this issue in High Sierra when reinstalling (MWB startup engine stopped working), I did check the install log and yes it got something to do with the sudoers.

Check with terminal ( ls -l /etc/sudoers) and saw that permission were wrong, system, wheel and everyone had read/write, so I looked inside /etc/ for sudoers (from finder) and pressed cmd-I, in permissions just changed system and wheel to read only and everyone to no access. Then proceed to install again, this time the installation was successful.

 

 

Screen Shot 2018-09-11 at 1.19.14 AM.jpg

Link to post
Share on other sites
  • 1 year later...

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.