Did get Boxcryptor to work with Big Sur 11.0.1 with M1, but after update to 11.1, and trying your advice from yesterday, the restart problem occurred again.

I'm also experiencing the same issue as SAL with the most recent update. Let me know if there are any logs or information I can send along to help.

flakingbiscuit SAL

Thank you for the feedback. I'd have two questions:

a) Is it correct that you upgraded from macOS 11.0.1 with Boxcryptor pre-2.39.1110 (e.g. 2.39.1101) to macOS 11.1 with Boxcryptor 2.39.1110 ?
b) Did you try the kmutil trigger-panic-medic command in Recovery Mode?

Additionally, the following steps would be very helpful:
1) Open Console app and start streaming (Start button in the toolbar)
2) Open Terminal app and execute the following commands:

sudo kextutil -v 6 /Applications/Boxcryptor.app/Contents/Frameworks/BoxcryptorFoundation.framework/Versions/A/Filesystems/bcfs.fs/Contents/Resources/mount_bcfs.app/Contents/Extensions/11/bcfs.kext
kmutil diagnose

3) Stop Console streaming, search for kernelmanagerd and export the output (Select all -> Copy -> Paste in TextEdit)
4) Send the Console and Terminal outputs to support@boxcryptor.com

Thank you for your help,
Robert

FYI: Based on current feedback (maybe not so much here, but in direct contact in our support), the latest experimental version 2.39.1110 seems to work great on macOS 11.1.

The only source for problems is when a user updated macOS from 11.0.1 to 11.1 and did not already have 2.39.1110 installed. In this case, macOS fails to unload the old kernel extension. Resetting the kernel extension management using kmutil trigger-panic-medic as described above resolves this issue.

Robert I'm one of those folks who upgraded to 11.1 (yesterday) without the latest version of Boxcryptor., which I've now installed.

I've tried the kmutil trigger-panic-medic fix, but no success. I also tried the manual delete extension terminal command above, but that didn't work. Just an error saying the sudo command wasn't recognised or something similar.

part of the problem appears to be that the approvals of the kext aren't persisting from boot to boot. I got it working and then on the next reboot (no other changes/updates) it went back to the problem. Even after the kmutil attempt a couple of times. Will attempt to further diagnose.

Nevermind. This one was total user error. I updated to BC 2.39.1101 somehow vs .1110. Update app to .1110, kmutil flush and then auth and reboot seems to work.

Kyle All cases we saw could be resolved using kmutil trigger-panic-medic. If you'd like, please contact us via support@boxcryptor.com and we'll try to resolve the issue with you.

aknight Thanks for the update. The current macOS and Boxcryptor build numbers definitely have to many ones ("1") and that's a crazy coincidence.

Installation worked with Big Sur 11.1, Boxcryptor pre-2.39.1110 and the kmutil trigger command.
Thx

Robert Got it working. I was referring to your post from 8 December, not the more recent one on 15 December. Followed that one precisely, and it is now working correctly. I'll see if it works with SIP turned back on.

Perfect!
It worked for me!

I had never installed Boxcryptor on my M1 Mac. Used the official release. Nevertheless I got an error stating that the extension could not be or had to be updated (do not remember). Did the steps (allow extension, reboot) but after every reboot I got the same error. So I had to do the kmutil trigger-panic-medic stuff. Now it seems to work.

I was alreay on Big Sur 11.1, maybe that is why.

Robert, the latest stable release works a treat. I've just finished uninstalling the most recent experimental version, and resetting the kernel extension management. I re-enabled SIP while I was at it. On reboot, I had to authorise the extension, which required a re-boot, but on the re-start, no never-ending cycle seeking extension approval. I can navigate to files encrypted with Boxcryptor and de-crypt them without any hiccups.

Looks like you have all nailed the solution! Thanks for your work.

Kudos to the devs for getting Boxcryptor working on the M1. Like others, I needed to to reset the kernel extensions but didn't need to disable SIP. Perhaps down the road, Boxcryptor can be revised to not be solely reliant on that Fleischer osxfuse extension.

Great stuff. Thanks for sorting this out for my M1 MacBook. Kernel reset worked out fine once I followed instructions. Kudos for devs and in particular to your support team "YK" :-)

Hi everybody,

Thanks for the positive feedback - I'm really happy that it turned out well. In the end the major blocker was really "only" that the new macOS kernel extension management is confused by multiple included kernel extensions for the different macOS versions (which was never an issue in the past). Once we removed the kernel extensions for the older macOS versions, everything turned green again

markbyrn A major priority for Boxcryptor for macOS in 2021 will be to evaluate alternatives to the kernel extension, e.g. the new File Provider extension which was first introduced in macOS 10.15 and further extended in macOS 11. A Boxcryptor version without requiring a kernel extension will definitely be the future.

Best regards,
Robert

Thank you! Could finally leave the endless loop. Made my day.

Not working here... set my security settings as requested during the startup options, did the "panic" thingie in the terminal, installed, accepted.... endless loop to accept the software and restart... failure.

Update: worked, it took me though at least 20 reboots...