Jump to content

Full Disk Access on macOS Catalina


Recommended Posts

  • Staff

The issue described below has been fixed in Malwarebytes for Mac 4.0. If you are still seeing the issue where Malwarebytes Protection does not show up under Full Disk Access, make sure that you have upgraded to 4.0. You can download the latest installer from here:

https://malwarebytes.com/mac-download

Original problem

If you have upgraded to macOS Catalina and have installed the corresponding update to Malwarebytes for Mac 3.9.32, you may see a problem where the app will tell you that you need to enable Full Disk Access. However, when you follow the directions provided, you will not see Malwarebytes Protection in the list where the directions say to look for it.

We are still unsure exactly what changed, and whether this is a Catalina bug that will be fixed in a future release, or whether we need to change something. We are investigating.

In the meantime, you can fix the problem by downloading the Malwarebytes for Mac installer and reinstall it manually. There is no need to uninstall Malwarebytes for Mac first, you can simply install on top of your existing copy. Once you have done this, you should see Malwarebytes Protection on the list of apps to give Full Disk Access to.

Download the Malwarebytes for Mac installer here: https://malwarebytes.com/mac-download

 

Technical background

It seems that something changed between the Catalina betas and the final release, and it is triggered by installing the Malwarebytes for Mac update via the installer process located at /usr/sbin/installer, as opposed to the Installer app located at /System/Library/CoreServices/Installer.app. When installing via the former, Malwarebytes Protection will not appear on the list. When installing via the latter, it will.

We have also observed cases where Malwarebytes Protection will disappear from the list, even though it has already been given Full Disk Access. Despite not appearing on the list, it will nonetheless continue to have Full Disk Access, and will remain capable of detecting and removing threats from locations that are not accessible without Full Disk Access. This is definitely a Catalina bug, which leads us to believe the other problem may also be a related bug.

Edited by treed
problem has been fixed
Link to post
Share on other sites

I'm in Mojave at the moment and looking at my Catalina - Data volume there is no /usr/sbin, so I suspect what you see is actually a hardlink to the System's Installer.app. That could still be a Catalina bug, I suppose.

Link to post
Share on other sites

  • Staff
11 minutes ago, alvarnell said:

I'm in Mojave at the moment and looking at my Catalina - Data volume there is no /usr/sbin, so I suspect what you see is actually a hardlink to the System's Installer.app. That could still be a Catalina bug, I suppose.

/usr/sbin/ is on the system volume in Catalina. See:

https://eclecticlight.co/2019/10/08/macos-catalina-boot-volume-layout/

Link to post
Share on other sites

14 minutes ago, treed said:

/usr/sbin/ is on the system volume in Catalina. See:

https://eclecticlight.co/2019/10/08/macos-catalina-boot-volume-layout/

Ah yes, I see that now. The executables appear to be quite different...

1372639298_ScreenShot2019-10-09at11_20_59.thumb.png.1ce1bd27b3a8a4fa0971a74609e1ab15.png

Link to post
Share on other sites

  • 2 weeks later...
  • 3 weeks later...

Start by upgrading to version 4.0. It’s a free update. You normally must restart the app, in any case, so the upgrade will take care of that for you.

Edited by alvarnell
Link to post
Share on other sites

  • treed unpinned and pinned this topic
  • treed unpinned this topic
Guest
This topic is now closed to further replies.
  • 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.