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

          5 days later

          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...

                These recommendations DO NOT WORK on a new processor! Everything is cyclical, the problem arises again and again. There is no decision!

                  I bought my M1 MacBook Pro one week ago and was struggling to get Boxcryptor to work. I tried everything in this post to no avail. Finally, I tried setting my Mac to Reduced Security again and got Boxcryptor to work. But I have to leave my Mac at Reduced Security in order to keep Boxcryptor working. I really do not like having to do this.

                  I emailed Boxcryptor 4 days ago asking if a future update will fix this issue of needing to keep our Macs at the Reduced Security settings, but so far have not heard back (well it is the holiday season). Anyway hopefully someone at Boxcryptor can figure this out once and for all.

                  Jim

                    9 days later

                    Same issue here. I installed the stable version (Boxcryptor_v2.39.1119_Installer.dmg) but entered infinite allow and reboot loop...

                      I use another piece of software: Mountain Duck https://mountainduck.io
                      This seems to have no problem mounting userspace volumes that support files-on-demand without installing Kernal Extensions.
                      Would it be possible for Boxcryptor to utilise whatever filesystem mounting method for macOS?

                      8 days later

                      And same issue here. Can we please hear from someone at Boxcryptor with the latest status on fixing this issue on their end?

                        15 days later

                        Same here. Infinite loop since weeks …
                        Any advice from the development team?

                          • Robert

                          • Post #55
                          • Edited

                          Hello everybody,

                          If you run into the "Endless system extension approve / reboot loop", the solution is to reset the macOS kernel extension management and make sure that you have the latest Boxcryptor version installed.

                          I'm very sorry for the inconveniences, but there is little we can do on our side here. I hate pointing fingers at others, but the new kernel extension management which Apple completely rewrote from scratch in macOS Big Sur is brimming with bugs - even in the latest 11.2 update. We have filed more than 10 bugs to Apple of which 7 are still open - one of them is the "Endless system extension approve / reboot loop" bug filed under FB8975139. It has been acknowledged as "critical" by Apple and will be fixed "in a future update" - but only Apple knows when this will be. We have worked around this bug in the latest Boxcryptor version, but an additional kernel management reset is required which can only be performed in macOS Recovery Mode. In the end, Apple has to get their stuff together and fix those bugs so that applications work as expected on their operating system.

                          We have a 100% success rate to solve the "Endless system extension approve / reboot loop" when the following steps are followed properly:

                          1. Uninstall Boxcryptor by moving it to the Trash and emptying the Trash
                          2. Verify that you do not have any other version of Boxcryptor on your Mac
                          3. Boot to macOS Recovery
                            • Shut down your Mac
                            • Press & hold the power button for startup until the start options are being loaded
                            • Choose Options
                          4. Open Utilities -> Terminal in the menu bar at the top
                          5. 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)
                          6. Verify that the command has been executed successfully by checking the output for the following content:
                            All third party kexts have been unapproved and uninstalled from /Volumes/Macintosh HD
                          7. Restart your Mac
                          8. Verify that macOS shows an "Panic Medic Boot" alert stating that all kernel extensions have been reset
                          9. Download and install the latest Boxcryptor version and run it
                          10. Allow the Boxcryptor system extension in System Preferences -> Security & Privacy
                          11. Restart your Mac

                          If the problem still exists afterwards, there must have been an error in the process and you might want to follow the steps again. If nothing helps, you can always contact us via support@boxcryptor.com and we'll try to assist you.

                          Best regards,
                          Robert

                            mcx808

                            Mountain Duck does not use a real virtual filesystem. Instead, it runs a local NFS server and mounts the NFS shares as network shares in macOS, i.e. all file operations are routed over a local network connection. It's a different approach which has its advantages (e.g. no kernel extension required) and also disadvantages (e.g. performance and stability) over a kernel extension.

                                Thx Robert, it worked! :-)

                                  15 days later

                                  I was finally able to get Boxcryotor to work fine. I followed the installation steps suggested by Robert many times, but Karabiner-Elements prevented my Mac from rebooting properly after allowing Boxcryptor in Security & Privacy, due to this issue (https://github.com/pqrs-org/Karabiner-Elements/issues/2517). I uninstalled Karabiner-Elements, installed Boxcryptor, and installed Karabiner-Elements again. Now everything works fine.