Insufficient permissions for action: Unable to load '' in unprivileged request.
First, I got this error:Įxecuting: /usr/bin/kmutil load -p /Library/Extensions/box.fs/Contents/Extensions/11.0/osxfuse.kext I was trying the 'fix' earlier, but it failed to work on my MacBook 2020 (Intel CPU). What I don't get is why it's so hard for them to release a patch, we've demonstrated a potential "quick fix" in this very thread. You can get the application to work by copying the kext to one of these locations and loading it manually, however this isn't an official fix.īox's claim that it's working on Big Sur (Intel mac's) as expected seems to be exaggerated. The OS expects the extensions to be in specific (pre-defined) directories. If you try and load the extension manually (CLI), the system will tell's you that you're trying to load the extension from the wrong place. This is because the extension isnt actually loaded. you get a notification to say you need to "Allow" the extension in Security & Preferences but there is nothing to allow.
SOFTRAID ERROR INSTALL
Worth noting, if the kext is unloaded from the system post upgrade for any reason you'll end up with the same issue as 2Ģ) Clean install of Box on macOS 11 consistently fails to launch As such the system allows the kext to be used when called by the application. post upgrade Box still works - this is most likely because the kext is already loaded pre-upgrade and that state is preserved. I've tested this a number of times and have found 2 main scenarios :ġ) Upgrade machine that has Box installed to macOS 11 We thank you for your continued patience and active community engagement. We have also added both of these issues to our Known Product Issues article. While we recognize this isn't the greatest news for some, we did want to provide some transparency and clarification. Thanks for your patience as we worked to provide this support. We are no longer accepting new enrollments at this time as our teams prepare next steps to support further launch activities.
SOFTRAID ERROR UPDATE
UPDATE (): Thank you to the Enterprise customers who enrolled in the Private Beta for Drive on M1 devices. Meanwhile, customers on these devices are encouraged to leverage our web-based application ( ). With that said, our Engineers are looking into this issue with high priority and are working with all stakeholders to find a resolution for this quickly.įor customers on Apple’s new Silicon M1 chip, we are unfortunately unable to provide a similar workaround and do not, at present, support the devices on Box Drive. That said, our Engineering team is actively working to add support for the M1 chip on Box Drive. A Beta is planned in early 2021 for our Enterprise customers. A future update of the application that includes a permanent fix may encounter unknown issues for those that have implemented this workaround. However, please note that while this workaround may enable Box Drive, this is not a supported solution. In limited situations where this does not remediate the issue, we've seen some success with a command-line workaround suggested in this thread.