Box Drive's system extension failed to load

Follow
New post
Regina Marie Henson - depro on 05-13-2021

Message:

Box Drive's system extension failed to load. Please make sure it has been enabled in System Preferences > Security & Privacy and then restart your computer. 

 

Followed instructions, still unable to run Box Drive

 

Platform: MacBook Pro, macOS Big Sur, M1 Chip

43

Comments

317 comments

Date Votes
  • colohost

    I've got a computer running what had been the private beta but reports 2.23; did it upgrade itself and I just need to follow the two steps, and it will continue to report 2.23? 

    0
    Comment actions Permalink
  • John Carbuccia

    Same here Jenn, couldn't get it to work AT ALL. I was asked to enable KERNEL extensions to reduce the system's security in recovery mode. I decided to wait until it's actually working. The BETA Box Drive for M1 does NOT work.

    0
    Comment actions Permalink
  • Tan Sharma

    Am I reading this right? The support article says “ Box Drive macOS 12 and M1 Public Beta ” .

    So you’ve taken a year to release a M1 Beta for a Beta OS? When you say GA available later this year, is this the same timeline as last November when you said a valid solution would be available by the end of the year? To be clear, asking users to drop system security is not a valid solution.

    What is the GA timeline, will it be this side of 2021?

    0
    Comment actions Permalink
  • Curtis Frazier

    I think there’s a lot of confusion. I’ve been running it for the past couple days and it’s working great on my M1 Mac Mini. I was able to change my security settings back to full security as well. You have to follow the directions very closely.

    0
    Comment actions Permalink
  • Tan Sharma

    I’m still waiting for a working general release,
    have been telling our customers it’s on the way. The lack of communication from Box is not appreciated. Perhaps we should time our billing to their comms, would save us a small fortune.

    0
    Comment actions Permalink
  • John Carbuccia

    Curtis Frazier, do we need to FIRST lower our security setting, INSTALL the beta, THEN go back and heighten our security settings? I was under the impression that you can take your BRAND newly bought MacBook Pro/Air/Mini M1, download the BETA Box Drive, install and be on your way... YES, NO, MAYBE? I may be missing something.

    0
    Comment actions Permalink
  • Tan Sharma

    Based on the article you shouldn’t need to change security settings if you’re just installing the new beta release. Article does say: “Operating systems supported: macOS 12“ , so would be good to know if anyone has tried this on Big Sur as well.

    0
    Comment actions Permalink
  • Ben

    These steps worked for me. I did not have Box Drive on the machine beforehand (I had been using Box Sync on my M1 until now).

    1. Installed the latest beta from here.
    2. Run the following command in Terminal:
      defaults write com.box.desktop MacMode fpe (Important note: This command needs to be run as the current user, not as sudo)
    3. Restarted Box Drive

    Used for a few hours so far and no issues whatsoever.

    4
    Comment actions Permalink
  • Curtis Frazier

    John,

    My understanding is a new computer just needs to complete in install as normal...no security changes needed.  I was using the prior version so I had to do the extra steps. 

    0
    Comment actions Permalink
  • John Carbuccia

    Curtis, Benny's steps worked for me. ALSO, I'm using Big Sur and just installed it with no issues AFTER following Benny's steps.

    0
    Comment actions Permalink
  • Curtis Frazier

    John, did you previously hav Box installed on these machines?

    0
    Comment actions Permalink
  • colohost

    I've got a user on an M1 mini who was running the prior private beta.  He's attempted to move to the public beta by way of:

    1) Run /Library/Application\ Support/Box/uninstall_box_drive

    2) Reboot to recovery mode

    3) Set security back to full

    4) Boot back up

    5) Tried to install the public beta BoxDrive.2.23.426.pkg linked from the article

    When doing that, he gets the warning about "To enable system extensions, you need to modify your security settings in the Recovery environment".  This should not be occurring with the public beta on M1 as best I can tell?  Has anyone else run into this?

    0
    Comment actions Permalink
  • Jenn French

    I had the same issue. After you change the security settings and download the latest beta, you need to follow Benny's steps (pasted here). As soon as I did this Box worked perfectly. The guidance from Box was very confusing and their customer support was not remotely helpful. Thank goodness for this thread.

    1. Installed the latest beta from here.
    2. Run the following command in Terminal:
      defaults write com.box.desktop MacMode fpe (Important note: This command needs to be run as the current user, not as sudo)
    3. Restarted Box Drive
    5
    Comment actions Permalink
  • John Carbuccia

    @Curtis I didn’t have box installed. This was a clean Box Drive install.

    0
    Comment actions Permalink
  • Joshua N. Kastan

    Currently running the new public beta (version 2.23.425) on an M1 Mac.  Working great.

    My MacOS is currently 11.4, and I have hesitated updating to 11.6 since I see that there is a known issue with 11.5 (https://support.box.com/hc/en-us/articles/4405801868307-Box-Drive-macOS-12-and-M1-public-beta-support-Known-Issues).

    Is anyone running the public beta on MacOS 11.6 without running into the issues noted as to 11.5?

    0
    Comment actions Permalink
  • Nick Giangarra

    I'd be interested to know if anybody has a workaround for OS 12.0.  Currently when I load the app and try to login it treats the login window as though it's a browser and logs me in like on the website rather than actually load my drive.  This is a major problem that won't allow for me to do my job if I can't get it fixed.

    0
    Comment actions Permalink
  • Jon Taylor

    Nick Giangarra just a note that I've been running the extension on 12.0 and now 12.1 on an M1 Macbook with no issues - it works fine - suggesting the issue may be local to your configuration rather than general!

    0
    Comment actions Permalink

Please sign in to leave a comment.