Box Drive's system extension failed to load
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
-
@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!
-
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.
-
@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".
-
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.
-
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!
-
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.
-
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
-
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
Please sign in to leave a comment.
Comments
318 comments