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
-
Box Sync - enables you to choose specific files and folders to sync between Box and your desktop and keeps them synchronized.
Box Drive - appears like a network drive and gives you access to all your Box content while you're online. It only consumes local storage for files in your cache and files you mark for offline.
-
Hi there,
I'm having the same issue and can see this is something the Box team are working on. Is it possible to be signed up to be notified as soon as a newer version of Box Drive that supports the new M1 chip is available? Using Box solely on Browser is slowing me down at work quite a bit, so I'm eager to switch back to Box Drive soon as I'm able!
-
They are starting to get some bad press. https://www.macrumors.com/2021/02/01/box-drive-macos-big-sur-m1-mac-issues/
I guess we'll have to try to shame box into supporting M1? -
I have been on Big Sur since it became available and still cannot get Box Drive to work. I ran the uninstall script from the terminal app and then downloaded Drive again and still not working. So frustrating! I have a folder on my desktop where I save everything that needs to upload to Box, at the end of the day I upload to the various folders in Box. Then I have to go back to my desktop folder and delete the uploaded files.
I updated to version 11.2 a couple of days ago, so that didn't help either.
-
I asked to join the beta group for M1 Apple users and got this back from customer support. So in summary: no further information available at this time. Coming soon...but not soon enough.
Thank you for reaching out to Box Product Support. I'd be glad to help you with your concern!
I can see you are curious about when we will be supporting our desktop apps on Apple M1 chipset machines. Unfortunately I am not 100% certain when that time will come. I know our product team is still working in conjunction with Apple to make the two products compatible.
The Beta is planned in early 2021 for customers. Meanwhile, customers on these devices are encouraged to leverage our web-based application (https://app.box.com).
Thanks for your patience with this! -
It's kind of humorous that Apple is now trying to throw money at developers to get them to send back their Developer Transition Kit mini's that real developers used to have their products ready for the M1 launch, given they shipped out almost a year ago. Box, on the other hand, seems to have not even started M1 development until the production units began shipping. I really hope whatever incompetence within Box, that allowed this mess to occur, has been corrected.
-
New Mac mini M1 running Big Sur 11.2 (20D64). Box is the cloud drive that we are required to use by my employer. It's is very inconvenient to not have desktop access to the files, especially when traveling and internet access isn't guaranteed. I hope you'll resolve this flaw soon, especially since it's been a known issue for almost a YEAR.
-
Has anyone with an M1 tried this script below while in Recovery Mode?: I don't have an M1 system to try the script on.
chflags restricted "/Volumes/Macintosh HD/private/var/db/KernelExtensionManagement"Note: You may need to replace Macintosh HD if you have a different drive name.
After running the above command, restart your machine and launch Box Drive.This script worked for me on systems on Mojave who had similar error message regarding systems extensions failing to load. -
Box drive is not compatible with M1. The installer is not compliant, if it was, Rosetta would do most of the translation.
Rosetta does not translate kernel extensions, so the installer would need to be compiled either specifically for arm or as universal.
Big Sur also uses a cryptographically signed and sealed volume. In short your OS essentially loads from a snapshot where the seal is verified. Breaking the seal is a quite likely a one way street, and could impact future os updates.
If your device is in a MDM, the following might help for intel devices: https://support.apple.com/en-gb/HT211860
-
Box has been a breeze to use, but no ETA on box drive on the M1s at this point is absurd.
Waited until now to upgrade to M1s as now they have full compatibility with our workflow apart from Box. The improvements elsewhere make upgrading a no-brainer even if it means migrating to other cloud storage.
-
Workaround?
There is a program called Cloudmounter. This will mount a number of different cloud servers in a virtual disk that you can place on. your desktop. This will give you access to your files on an M1 Mac. I cannot tell you from my own experience how it will affect syncing or what will happen when Box does get its M1 compatible apps working. But it might be of help to some.
If you subscribe to Setapp, Cloudmounter is included with the subscription.
-
When I look at the THOUSANDS of dollars a year I pay to Box.com for their service this issue makes it far more frustrating. As an office of Mac users who depend on Box.com every day it was a tough decision to move away given the time and effort it took to migrate to Box in the first place. I wont be back.
-
Like Google, it seems they are starting from scratch to build their own version of FUSE that works with the latest processors and OS. The company big-wigs were probably appalled that an open-source project like MacFUSE is suddenly asking for licensing fees to include their project with a for profit software distribution, and are forcing the developers of Box Drive to do it in a way that doesn't include helping out a single developer. At least that's my theory.
Please sign in to leave a comment.
Comments
317 comments