Level up your Box knowledge with brand new learning paths on Box University. Visit training.box.com to get started

Box Status

Comments

10 comments

Date Votes
  • Q Manning

    Same issue with macOS Big Sur. Halp.

    2
    Comment actions Permalink
  • Michael Brennan

    I’m on High Sierra and cannot solve this issue

    It started when I loaded a security update from Apple as you are advised too, no cleaning and reinstalling has helped

    If anyone has any ideas it would be gratefully received.

     

     

    0
    Comment actions Permalink
  • Jeremy Jordan

    I am having the same issue too. Anyone heard an update?

    0
    Comment actions Permalink
  • Sara Strobaugh

    I submitted a support ticket and received an update that involves running a terminal command about permissions on kernel extensions while booted into recovery. It is untested as of yet. Speaking with a colleague we are first going to attempt to reapply management from Jamf. As this is an enterprise computer and box is managed by jamf.

    0
    Comment actions Permalink
  • Marcos Tenório

    The same problem here, someone solved it?

    0
    Comment actions Permalink
  • beggiato
    • Edited

    I'm having the same problem. I was using Box Sync before deciding to switch to Box Drive. According to these posts (see links below) on the Box Support site, the Box Drive installer is supposed to remove Box Sync and clean up your files BEFORE installing Box Drive. There's even a prompt saying that it will uninstall Box Sync but I never saw it. I think the fact it's not uninstalling Box Sync properly, is causing some conflict. I even tried to uninstall Box Sync manually, reinstall Box Drive and reboot, but I got the same error message.

    https://support.box.com/hc/en-us/articles/360043697354-Switching-from-Box-Sync-to-Box-Drive

    https://support.box.com/hc/en-us/articles/360044196753-Uninstalling-Box-Sync-Using-the-Box-Drive-Installer

     

    2
    Comment actions Permalink
  • Jeremy Jordan

    Hi beggiato - I tried this and am still getting the same error. Has anyone had any luck?

    1
    Comment actions Permalink
  • Paolo Fascia

    Solved, find my post

    -13
    Comment actions Permalink
  • bike4life

    "find my post" well that's helpful..

    0
    Comment actions Permalink
  • Scott Norton

    Having the same issue on a late-2019 MBP running Big Sur on an Intel x86_64 (NOT M1) chip. The top advice on this site seems to be pertinent to the M1 macs, which does not apply to me.

    0
    Comment actions Permalink

Post is closed for comments.