Box Drive's system extension failed to load

Pinned
New post

Comments

292 comments

  • Antonio Giglio

    Actually it does. On BigSur (11.2.3) - M1 MBP - with BoxSync 4.0.8016. But it's nowhere as seamless as BoxDrive. But at least it works.

    0
    Comment actions Permalink
  • Benny

    Thanks all. Might give Box Sync a try in the meantime then.

    0
    Comment actions Permalink
  • 0
    Comment actions Permalink
  • トダテヨウヘイ

    hmm…… Interesting.

    https://techcrunch.com/2021/03/22/box-shares-rise-on-report-company-is-exploring-sale/

    0
    Comment actions Permalink
  • Benjamin A Pillmore

    Great, a long awaited beta that uses the same architecture as the previous version and allow a kernel extension...

    So...we are getting... nothing? This is different from the existing workaround and previous version how?

    0
    Comment actions Permalink
  • Tan Sharma

    So 9 months after the announcement and 4 months after this thread took off, all we have is a recompiled KEXT? That about sums it up doesnt it? 

    This is still no good for us as it's still a Beta product which we cant deploy across our fleet. So Box Drive is still broken

    0
    Comment actions Permalink
  • Tan Sharma

    Dear Box, 

    Would it be possible to confirm why the Beta package is loading the KEXT from /Library/Filesystem again? Is this because the path is hardcoded in the application? We highlighted in this very thread that macOS does not expect KEXTs to be in this location: see https://support.box.com/hc/en-us/community/posts/360051323454-Box-Drive-s-system-extension-failed-to-load?page=1#comments

     

    0
    Comment actions Permalink
  • Jenn French

    I finally got the Beta and it works perfectly on my M1 Macbook Pro. Thank god. Box Sync was an okay work around but it's not usable, and Box is useless without Box Drive.

    1
    Comment actions Permalink
  • Pete Stanley

    Agreed. Anything beta is not a solution. We need a truly KEXT-less product or nothing.

    Don't think we'll be holding out until the expected solution is due to land...

    0
    Comment actions Permalink
  • David Maestre

    Not perfect but working for me on my M1 machines with MDM Profile pre-loaded. 

    Machine has to rebuild/recompile the Kexts and it restarts. Twice.

    Then you have to approve the extensions and restart again. 

    This process will make your machine lag a big especially if you have alot of programs that run or startup in the background. Give it some time and it'll all get loaded.

    It's a step in the right direction but far from being Kext-less.

     

    0
    Comment actions Permalink
  • rmashintchian

    @Tan Sharma - /Library/Filesystems is the default location where this particular kernel extension gets installed.  Can you clarify which version of the OS you're using?  Do you see this see this issue on Mac OS 11.2?  If you do, can you please submit a support ticket and include a sysdiagnose so we can diagnose further?  Thank you.

    0
    Comment actions Permalink
  • Tan Sharma

    @rmashintchain , I can see from the package that it installs to /Library/Filesystems , question is why?

    I’m running macOS 11 and even on intel machines the os expects to load extensions from specific locations - /library/Filesystems is not one of them. A lot of this is detailed in this very thread.

    Now that the Beta is out, what is the timeline for a working public release?

    0
    Comment actions Permalink
  • Bill Elkus

    Has anyone heard whether Box Sync will eventually support M1 chips?  Their OS page makes it clear they do not support it today:

    https://support.box.com/hc/en-us/articles/360043696234-Understand-the-Box-Policy-For-Browser-And-OS-Support

    I prefer Box Sync over Box Drive, for two reasons: (a) since a copy of all files is copied to my computer, I have offline access on airplanes or in other locations without solid Internet coverage, and (b) my backup software Carbon Copy Cloner doesn't recognize Box Drive and will not back it up.

    0
    Comment actions Permalink
  • Kathryn Yee

    @Bill Elkus I'm not the most tech savvy person (so I could be wrong/taking some risks), but I think Box Sync does work for M1 chips? I used it briefly the other day, but my issue was that it only synced 100GB of data--this might have been a limitation of my institutional account though. Box Drive actually does work offline, but the issue is that the M1 chip version currently requires you to set your computer to reduced security. If you're okay with that, it works well. I'm not familiar with backup software, but since Box Drive syncs well, I basically just backup all of my files to Box. Occasionally, I'll also use an external hard drive, but at the moment I don't have one that fits all of my Box files and my local hard drive contents.

    0
    Comment actions Permalink
  • Benjamin A Pillmore

    Age of thread: 5 Months

    Age of last moderator update from Box: 1 Month

    Latest Update from Box (yesterday):

    "Later this year, Box will release a version of Box Drive that no longer requires kernel extensions, therefore no longer requiring Reduced Security mode to run.   In the interim, customers who would like to use Box Drive will need to enable Reduced Security mode in order to use the product."

    -- https://support.box.com/hc/en-us/articles/1500004479962-Box-Drive-support-on-devices-with-M1-chips

    5 Months we have been airing our frustrations...

    10 Months since Apple made DTK's available to developers: https://www.apple.com/newsroom/2020/06/apple-announces-mac-transition-to-apple-silicon/

    And now we are met with a delivery date of "later this year"? Are your roadmaps written in crayon too?

    Everyone else seems to have figured out how to AT LEAST make their app work via Rosetta with many offering native M1 support for some time now on Big Sur no less...

    What's the hold up? Is this upgrade too hard? Did Content Cloud seem like a better idea than supporting existing users? Or do you guys get last pick of the developers on the market?

    This is beyond ridiculous at this point.

    Reduced security mode as a workaround...I mean, come on...

    5
    Comment actions Permalink
  • Kyle

    M2 is being fabbed for a (probable) fall release of Apples flagship notebooks in the Apple Silicon flavor with a possible 14" version as well.  Do you think Box Drive will be ready for this one, or nah?

    0
    Comment actions Permalink
  • Randy Juhl

    Although most of this thread is about the M1 machines, my MacBook Pro (Intel) had the same problems until I just updated to Big Sur 11.3.1 and lo and behold, Box Drive is up and running again -- no more fail to load errors!!??  (Box Drive version 2.20.136)

    0
    Comment actions Permalink
  • Kelly Gabrysch

    I have an iMac 5K Retina, Intel i9 3.6 Ghz 8 core, Big Sur 11.4... none of this M1 stuff is my issue. It 'WAS' working OK, although I couldn't copy files to Box for a while, only from. Then, just like everyone else, suddenly "Box Dive's system extension failed to load". I HAVE SET THE SECURITY AND PRIVACY settings properly and it has full disk access... Still nothing, and it's impossible to get it to work. I have to use the web based version which is annoying. Looks like this has been going on forever! And for Apple corporate to use BOX as much as they do, I can't believe they are letting this happen. So annoying. This needs to be fixed NOW, not later.

    0
    Comment actions Permalink
  • Barbara Lewis

    FINALLY! After a year and updating my Mac mini to Big Sur 11.3.1, I finally have the Box drive on my desktop again! Still don't understand what took so long. Only one problem so far, the desktop version won't let me drag/drop files into folders. Had to go to the web version for that.

    0
    Comment actions Permalink
  • TH

    Just updated my 2018 Intel MacBook Pro to 11.4, and now I am getting the failed to load extension for the first time.  

     

    edit: I uninstalled it, restarted the Mac, reinstalled Box Drive and it's working now.

    0
    Comment actions Permalink
  • Benjamin A Pillmore

    Age of thread: 7 Months

    Age of last moderator update from Box: 3 Months

    Latest Update from Box (EDIT: 3 months ago):

    "Later this year, Box will release a version of Box Drive that no longer requires kernel extensions, therefore no longer requiring Reduced Security mode to run.   In the interim, customers who would like to use Box Drive will need to enable Reduced Security mode in order to use the product."

    -- https://support.box.com/hc/en-us/articles/1500004479962-Box-Drive-support-on-devices-with-M1-chips

    7 Months we have been airing our frustrations...

    1 YEAR since Apple made DTK's available to developers: https://www.apple.com/newsroom/2020/06/apple-announces-mac-transition-to-apple-silicon/

    And now we are met with a delivery date of "later this year"? Are your roadmaps written in crayon too?

    Everyone else seems to have figured out how to AT LEAST make their app work via Rosetta with many offering native M1 support for some time now on Big Sur no less...

    What's the hold up? Is this upgrade too hard? Did Content Cloud seem like a better idea than supporting existing users? Or do you guys get last pick of the developers on the market?

    This is beyond ridiculous at this point.

    Reduced security mode as a workaround...I mean, come on...

    1
    Comment actions Permalink
  • Pete Stanley

    @Box, it's been long enough to get a plan together and keep your customers in the dark on core functionality. PLEASE PROVIDE AN UPDATE on state of development supporting modern system extensions!

    0
    Comment actions Permalink

Please sign in to leave a comment.