Box Drive's system extension failed to load

Pinned
New post

Comments

292 comments

  • Robin Crumby

    Still not working for me on Big Sur on brand new MacBookPro with M1 chip. Is there any update from Box when this will be fixed? This is ridiculous.

    0
    Comment actions Permalink
  • Laura Watts

    @Orla Dunleavy 
    Where do you find box.fs in the first place, in order to move it to the new folder you created?

    0
    Comment actions Permalink
  • Tan Sharma

    /Library/Filesystems

    https://support.box.com/hc/en-us/community/posts/360051323454/comments/360013689894

    0
    Comment actions Permalink
  • Sebastien Zuchowski

    Very frustrating for Box to take so much time to fix this. This issue is critical for many enterprise user, and may push to move to other alternative to Box. MacBook Pro, M1 chip, Big Sur 11.1. Again very frustrating...

    1
    Comment actions Permalink
  • Jon Taylor

    Dear Box. This issue is immensely frustrating and it is becoming embarrassing; both Big Sur and the M1 Macs were announced in June! As the IT Manager of a medium-sized charity, I am now seriously exploring alternatives to Box as the basis for our remote/hybrid working model :(

    1
    Comment actions Permalink
  • Laura Watts

    Just so everyone knows, this isn't just a Big Sur/M1 issue. My MacBook Pro is still using Mojave, and with the most recent Box update to version 2.19.294, I am experiencing this same file extension problem. My iMac is running on Catalina and on the previous Box version, so I will not be updating Box on that computer until this is resolved!

    0
    Comment actions Permalink
  • Romain Nouzareth

    This is worrisome, means their tech team is out the game, and that management has no vision about it... a few days yes, but many months? Dropbox does not have this issue so I moved back...

    2
    Comment actions Permalink
  • Doug Cowburn

    Hello, Brent, Director of Product Support:

    It has been a month since your update and months since box.com has known about the M1 computers. Canceling box.com is my next step. 

    1
    Comment actions Permalink
  • Olivier Morel

    The problem with Dropbox, if you use it with Box: it's the collaboration / online edition with Pages, Numbers and Keynote described here: https://support.apple.com/en-us/HT207876 - Dropbox doesn't support this capability.

    0
    Comment actions Permalink
  • Nurlina Amin

    Why is it only available to Enterprise customers in early 2021?

    When will it be available to ALL customers?

    I'm disappointed that Box isn't more quick on this matter, especially having been one of your early customers.

    0
    Comment actions Permalink
  • Bill Elkus

    Possible workaround:  Box Sync

    https://support.box.com/hc/en-us/articles/360043697194-Installing-Box-Sync

    I had abandoned Box Sync for Box Drive two years ago.  Box Sync places an actual copy of the shared contents on your computer, then keeps it current via syncing vs. Box Drive which puts a virtual copy and then grabs files as you request them.  Box Sync works for me in Big Sur on a 16 inch circa 2020 MacBookPro.  Plus I like not having to depend on a vendor and online access availability in order to access my files.  

    I suspect Box Sync is slower than Box Drive in displaying updates, and it consumes more resources updating files you may not need.  

    But at least it works, which is more than I can say for Box Drive.

    0
    Comment actions Permalink
  • sam

    I have M1 and Big Sur. Interested to beta test when solution is out "Early 2021" - any update from the Box development team?  Please ping me to beta test.

    0
    Comment actions Permalink
  • Edouard D

    Dear all.

    I've just got an answer from the support telling :

    I just confirmed that there is no date that has been set yet since it hasn't started yet. 
    You may follow this page for updates when more information is released concerning any upcoming betas or solutions that contain a fix. 
    https://support.box.com/hc/en-us/categories/360004130774-Product-Announcements

    We are not considered, the work is not started !!!! Go your way, they will not help us.

    0
    Comment actions Permalink
  • David Maestre

    Wow -- still no work-around or anything. Sad. 

    All we need is a osxfuse.kext that's compatible. 

    0
    Comment actions Permalink
  • Kristi-Lynn Jacovino

    I'm on the M1 chip and I just figured out a workaround using Box Sync: https://support.box.com/hc/en-us/articles/360043697194-Installing-Box-Sync

    Once you connect it, you'll have to go to Box and manually choose which folders to sync, but that wasn't too much trouble for me: https://support.box.com/hc/en-us/articles/360044196393-Marking-Content-for-Box-Sync#marksync#marksync

    I was able to install Box Sync and sync the folders that way, seems to work pretty much the same as the Box extension I was using previously, so maybe that'll help others with the M1 issue for now!

    0
    Comment actions Permalink
  • Bjørn Andersen

    Box seems to work fine on my Intel iMac running Big Sur, but at every reboot I get this notification:

    Allowing or not allowing it makes no difference, it will show up at next restart. Any ideas how to get this out of the way?

    0
    Comment actions Permalink
  • colohost

    Same; every single time.

    0
    Comment actions Permalink
  • John Carbuccia

    @Tan Sharma. Do you know if this will work on an Intel based system? The problem a user I support is on her macOS Mojave Intel based system.

    0
    Comment actions Permalink
  • Tan Sharma

    @John , no reason why it shouldn't work on Mojave, provided one of those directories exist.

    If you're using a MDM you might want to whitelist the Bundle and Team Identifier. It's also worth making sure that the user has not blocked the extension as part of TCC by accident. You should be able to read the user TCC plist for this.  

    Alternatively a clean uninstall using the script provided by Box and a reinstall should work too. That works for me on Catalina, so in theory should work on Mojave too. 

    Best

    Tan

    0
    Comment actions Permalink
  • Laura Watts

    I am using macOS Mojave on an Intel-based system, and a clean uninstall and reinstall using the script provided by Box did not work for me.

    0
    Comment actions Permalink
  • John Carbuccia

    @Laura Watts - clean uninstall/reinstall didn't work for me either on Mojave.

    0
    Comment actions Permalink
  • Tan Sharma

    @Laura, @John I'd be interested to know what error you get after a re-install on Mojave.

    I take it you get nothing box related for: kextstat | grep -v com.apple ?

     

    0
    Comment actions Permalink
  • Laura Watts

    I get the same error message I've gotten since this started:

    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. If the problem persists, please contact Box Support to further troubleshoot the issue.

    0
    Comment actions Permalink
  • Tan Sharma

    @Laura, trying to load the extension manually should give you a more verbose output of why it's failing (similar to what I mentioned here: https://support.box.com/hc/en-us/community/posts/360051323454/comments/360013689894)

    To try and load it manually you can run the following: 

    • sudo kextload /Library/Filesystems/box.fs/Contents/Extensions/11.0/osxfuse.kext
    0
    Comment actions Permalink
  • Ela Matthews

    Any update on this please? 

    0
    Comment actions Permalink
  • David Maestre

    Why are we talking about Mojave on this thread? lol

    Still waiting for a fix for M1. 

    I have it currently working on Intel Based machine with a Profile loaded from MDM servers. 

    0
    Comment actions Permalink
  • sam

    I am currently using Box Sync which is an OK workaround. See below customer service most recent response to me after requesting an ETA for Beta for M1 (and Big Sur OS) incompatibility:

    Jan 13, 2021, 12:49 AM PST

    Thank you for reaching back to us. I understand where you're coming from.

    Currently, there are no ETA when the Beta program or fix will roll-out. You may subscribed from our support page to get informed once we released a new update: M1 support for Box Drive Private Beta.

    Best,

    Box Product Support

    0
    Comment actions Permalink
  • sam

    https://support.box.com/hc/en-us/articles/360043697194-Installing-Box-Sync

    This is Box Sync workaround I am using in the meantime, found on one of these threads.

     

    -1
    Comment actions Permalink
  • Jürgen Fae

    I reported my M1 issue earlier.

    Box is essential for our business. for anybody interested: we now use CloudMounter until Box is able to update this. It's ok. sometimes loses connection, but overall a good workaround.

    Personally, I think this is a disaster for Box. but obviously there are too few M1 user up-to-now ...

    1
    Comment actions Permalink
  • Jenn French

    @Sam I am using the Box Sync work around too (grateful for the savvy folks on these threads). It is an okay solution; luckily I have plenty of space on my hard drive but only synced certain files in an abundance of caution. It sure seems like there are a lot of us MAC users! But everyone else in my office (who uses Box) uses Windows.

    I am disappointed by the slow fix and the lack of response from customer support to all of these comments.

    0
    Comment actions Permalink

Please sign in to leave a comment.