Box Drive's system extension failed to load

Pinned
New post

Comments

292 comments

  • Ed

    Hi Box, seriously, please resolve this. I have a significant amount of work to that requires box drive to function as normal. Not being able to use box drive is going to cost me a lot of time (money). Figure it out!

    Sincerely,

    13" MacBook Pro 2018, Intel chip.

    0
    Comment actions Permalink
  • David Maestre

    @Ed & @Ali,

    Box is working for me on BigSure Intel based machine. You have to restart the machine after installation for the Extension to be approved and loaded..

    What error are you getting or seeing after an install?

    0
    Comment actions Permalink
  • Ed

    After restarting the machine, this is what I'm now seeing.

    0
    Comment actions Permalink
  • David Maestre

    @Ed
    What version are you installing?

    0
    Comment actions Permalink
  • Ali Fathi

    @Curtis Frazier's comment is the best; 

    I am now adding another 30 days to each;

    • 180 days since Apple released a developer preview of Big Sur at WWDC
    • 180 days since Apple offered a Developer Mac with Apple Silicon for development and testing [this is the main problem]
    • 135 days since Apple released a public beta of Big Sur
    • 37 days [this is actually closer to 60] since Apple released Big Sur to all users

    Box Drive still does not function. How many engineers you need? 

    @Brent, This is just rubbish, not only I am frustrated but also I am losing my confidence in your service. We moved from Dropbox to Box, that was a mistake! As a director of a deep-tech company now I am disconnected to my staff thanks to your and your organisation's incompetence! 

    4
    Comment actions Permalink
  • Ali Fathi

    @ David, no Box still cab't make its most basic service work on M1 MacBook Pro M1. 

     

    0
    Comment actions Permalink
  • David Maestre

    Regardless just trying to help with Intel Based machines.

    I'll patiently wait for M1 compatibility before I approve M1 in my environments.

    0
    Comment actions Permalink
  • Ed

     

    The current available "Download Box Drive for Mac" on Box's website. Sorry that's not more specific.

    0
    Comment actions Permalink
  • Ed

    David, thanks for your help. Can you point me to the Box Drive 2.17.176 download anywhere else? I'm wary of downloading a zip file from google drive. I'm unclear on which configuration profile to load? I only have one user profile on my machine. Is that what you're referring to or something else? Thanks again.

    0
    Comment actions Permalink
  • Ali Fathi

    @David, thanks for your support, I understand and appreciate it.  We checked the compatibility of M1 with our technical/ specialised softwares and all fine. Literally, every provided came up with updates within 1-2 weeks to sort out the compatibility issue, I could not believe that of all, Box will be the problem. I even didn't check their compatibility based on trust in their competence. I am not sure whether they are even trying to address the problem or not, as the last update was for 10 days ago, the one before that was for 1 month ago saying that we know the problem "Roger". 

    1
    Comment actions Permalink
  • Ermal Dreshaj

    For an Intel-based Mac, uninstalling NTFS for Mac application by Paragon Software did the trick for me.

    I'm using an Intel-based MacBook Pro, having the issue where macOS is refusing to load the Box kernel extension. After seeing Daniel's post here https://support.box.com/hc/en-us/community/posts/360051323454/comments/360014934873 I tried running the same command, and received an error message that the kernel extension failed to load due to an unknown reason.

    I started thinking that it was maybe related to FUSE due to other posts and suspicions here, and thought hard about what is on my system that could be interfering with FUSE, and I realized that NTFS for Mac uses FUSE to mount my NTFS bootcamp drive.

    So, I uninstalled NTFS for Mac and Box Drive now works on macOS Big Sur installation.  It looks like there is a conflict between FUSE libraries provided by both of these programs.  I will try to reinstall NTFS for Mac and see if problem appears again.

    0
    Comment actions Permalink
  • Thomas Wilkens

    We just fixed the problem on a device without M1 Chip. Delete box.fs in the library and install box again.

    -1
    Comment actions Permalink
  • Doug Cowburn

    When will the issue of box app not working with the M1 chip be solved??

    1
    Comment actions Permalink
  • Benny

    Really need this. I've switched to using the web app but it's so much slower having to download, edit, upload for 50+ files every day. Please hurry!

    0
    Comment actions Permalink
  • Kirycool

    Hi all, I find this file in my mac. This work fine on my macbook pro 2014 with big sur.

    /Library/Application Support/Box/Box/Autoupdater/Updates/2.19.292.pkg

    0
    Comment actions Permalink
  • CL Loh

    Hi can I check if there is any update to using Box in a M1 Chip?  

     

    0
    Comment actions Permalink
  • Bill Elkus

    Box Drive worked fine for me under Catalina. Intel MacBookPro 2020.   Followed all above 'solutions' and none worked for me under Big Sur.  Deleting box.fs and reinstalling got the closest to working ... at least rebooting generated a window asking me to approve the extension.  I did approve it. Still did not work!

    0
    Comment actions Permalink
  • Todd Versteeg

    I can’t believe this isn’t solved yet. You’ve known about it for 2 months. I can’t say I have a lot of trust in a company that can’t even get something like this figured out with my data.. Give us a date when this will be solved. 

    4
    Comment actions Permalink
  • Orla Dunleavy

    Hi everyone.

    I have found that if you use Activity Monitor to "kill" all Box tasks, then create a nested folder with "/Library/Filesystems/box.fs" this will allow Box Drive to work in Finder.

    This will need to be done on each restart though.

    Hope this helps.

    Orla

    0
    Comment actions Permalink
  • Jürgen Fae

    hi Box,

    MS was able to update its Office Suit to M1! How about the Box Drive???

    this is really not good!!

    0
    Comment actions Permalink
  • Todd Stout

    You might want to prominently note the lack of M1 compatibility on your Box Drive download page (https://www.box.com/resources/downloads) since the software available there is only compatible with Mac (Intel) at this time. It would save a lot of time, money, and effort on people like me who assumed that when it said it was compatible with Mac that it meant all Macs. 

    Tardiness at updating software for compatibility is annoying, but forgivable for a major platform transition such as this. As long as we can see the path forward and get regular progress updates we can make an informed decision on whether to stick it out or not and what our purchasing priorities need to be. For an enterprise-focused company such as Box, however, lack of transparency is unforgivable and will have us looking at alternate vendors pretty quickly. 

    1
    Comment actions Permalink
  • Bill Elkus

    Orla wrote:

    I have found that if you use Activity Monitor to "kill" all Box tasks, then create a nested folder with "/Library/Filesystems/box.fs" this will allow Box Drive to work in Finder. This will need to be done on each restart though.

    Could you please give more details on how to do this? What did you name the folder, and where exactly did you put it? Was the only contents of that folder box.fs ?  Thanks

    1
    Comment actions Permalink
  • Jenn French

    Same issue. Brand new Macbook Pro with M1. I use my computer almost exclusively for work, with Box. I love my computer but not being able to use Box is a huge issue. I hope that Box fixes it soon.

    1
    Comment actions Permalink
  • Aline Tashjian

    When can we expect this update????

    1
    Comment actions Permalink
  • Tom Szauer

    Hi Box Team, do you have any updates on when Box will work with the M1 chip and BigSur. Apple doesn't sell Intel based MacBook Air anymore and we just had to place an order for new laptops. Box is THE collaboration tool for our company, not being able to work with it is out of the question. Can you please give us any information at what we are looking for in terms of time for a solution?

    Thank you

    1
    Comment actions Permalink
  • Orla Dunleavy

    @Bill Elkus

    I need to kill all Box tasks in Activity Monitor first.

    I have to do this after every restart of my system and it works.

    1
    Comment actions Permalink
  • Jenn French

    @Orla Dunleavy

    Thank you for your help! Where are you getting the things you are putting into the folder? The 10.11, etc. and the box.fs?

    0
    Comment actions Permalink
  • colohost

    Really peculiar that M1 support is taking this long; the hardware has been available to even low end developers for half a year but big enterprise Box can't get it working.  Perhaps that whole strategy of custom installer / admin rights kernel mod loads wasn't such a great idea...

    0
    Comment actions Permalink
  • BG

    Also struggling with this. Going to be putting the new Mac aside to use an old one to get Box working. 

    0
    Comment actions Permalink
  • Romain Nouzareth

    Its been more than 3 months??? WHERE IS THE M1 EXTENSION????

    You look like a JOKE Box!

    1
    Comment actions Permalink

Please sign in to leave a comment.