Version V2.39.1101 does not work on 11.1 Beta (20C5061b) -> Not able to enable the system extension

    NBruns
    I also tried 11.1 RC, but had no luck. Removing the kernel extension also did not work.

        NBruns Thank you for your feedback. The kernel extension loading is very likely caused by a confusion of the macOS kernel management which version to load. Boxcryptor comes with different versions of the kernel extension for the different macOS versions (e.g. 10.14, 10.15, 11.0) and macOS sometimes seems to try to load the wrong version for an older macOS version which obviously fails on Big Sur.

        Can you try to manually delete the non-Big Sur kernel extension versions and see if this improves the situation? To delete them, please execute the following command in the Terminal app:

        sudo rm -rf /Applications/Boxcryptor.app/Contents/Frameworks/BoxcryptorFoundation.framework/Versions/A/Filesystems/bcfs.fs/Contents/Resources/mount_bcfs.app/Contents/Extensions/10*

            Hi everybody,

            We're pretty confident that the kernel extension loading problem is caused by the kernel extension manager being confused which version of the kernel extension to load and trying to load one for a different, wrong macOS version. While we're continuing our efforts to provide a single app for all supported macOS versions, here's an experimental version which contains only the kernel extension for macOS 11 Big Sur:

            https://www.dropbox.com/s/capkjj2zf1txcmq/Boxcryptor_v2.39.1110_Installer.dmg?dl=0

            If you experience any problem loading the kernel extension (and thus mounting the Boxcryptor disk) with Apple Silicon Macs, please use this version and I'd be happy to hear your feedback.

            Note: If you already upgraded to Big Sur 11.1, you might have to reset the kernel extension management so that any wrong kernel extension is properly removed from the system after you updated Boxcryptor:

            1. Uninstall Boxcryptor (Move it to the Trash and empty it)
            2. Boot to macOS Recovery by pressing & holding the power button for startup
            3. Open Utilities -> Terminal
            4. Enter the command:
              kmutil trigger-panic-medic --volume-root /Volumes/Macintosh\ HD
              (If your boot volume has a different name than "Macintosh HD", replace it in the command)
            5. Verify that the command output includes the following content:
              All third party kexts have been unapproved and uninstalled from /Volumes/Macintosh HD
            6. Restart your Mac
            7. Verify that macOS shows the "Panic Medic Boot" alert as shown below
            8. Install the latest Boxcryptor version and run it
            9. Allow the Boxcryptor system extension in System Preferences -> Security & Privacy
            10. Restart your Mac

            Best regards,
            Robert

            You will get feedback ASAP, on Friday I will be back in home office.

              • SSAL

                • Post #29

                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. 🤷‍♂️

                                • Kyle replied to this.

                                      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.

                                        Hi everybody,

                                        Thank you all for your feedback and assistance on our way to stable Apple Silicon support. It sometimes was a little bit rough, but we finally have been able to resolve the kernel extension loading problem. As a result, we have released the first stable version of Boxcryptor with Apple Silicon support yesterday and you can download version 2.39.1119 here:

                                        https://www.boxcryptor.com/l/download-macosx

                                        If you did have an experimental version (or a version without Apple Silicon support) installed on your M1 Mac before, you might have to reset the kernel extension management as described here:

                                        https://boxcryptor.community/d/17031-apple-silicon/27

                                        In all known cases, resetting the kernel extension management and then installing the new stable version resolved the issues. If you still experience them, please double check the you executed the kmutil trigger-panic-medic command correctly (double dashes prefix for --volume-root and space between --volume-root and /Volumes/Macintosh\ HD) and maybe try it again.

                                        Thanks again and best regards,
                                        Robert

                                          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.