M1 System Extension Cache Rebuilding Loop

This is on an M1 MacBook Pro running 11.1b1.
I installed an Extension from Rogue Amoeba to support their App Suite.
  • Boot into recovery to set system policy to allow user permission of extensions

  • Reboot and install extension

  • Allow Extension in Preferences > Security panel

  • Allow rebuild and restart.

It comes up with an endless loop of failure due to an Extension from Apple Inc. !

The Rogue Amoeba extension loads fine.

Any ideas?
HI, sorry I cannot help you solving the issue, but

I am running into same issue installing NORDLOCKER (

I also come in a loop were the systemextension is constantly blocked in the privacy screen

Nordlocker engineers are looking into it since Nov.

IN the mean time I am X beta releases further both from MacOS as well as Nordlocker
but still not solved
I'm having a similar issue trying to get Google Drive File stream installed.
I had to enable the user management of system extensions but now every time I try to allow the google extension and reboot it comes up with this error.
I encountered the same issue of Google Drive too
I am also facing this issue with Google Drive. Endless loop of rebuild and restart.
Also having the same issue with Drive for desktop on M1 Macbook pro - any ideas?
Same for me with Google Drive. Only way to get out of the loop was to uncheck the permission and abort the Google Drive install.
I got it to work on an M1 MacBook Pro but I can't get it to work on two different M1 Mac Mini's. All of them are running the latest version of Big Sur. The Mini's have the system extension loop :(
Having the same issue with Google Drive on M1 MacBook Pro
Works with the 11.3 Beta 5 that was released yesterday on a M1 MBP.
Same problem here win MacBook M1 2020, MacOS Big Sur 11.2.3 (20D91), and Google Drive.

Upgrading to 11.2.3 fixed a similar problem I had with an update from Apple Inc, which was listed together with the one for Google Drive, now the one from Apple ha gone, but the one from Google remains in endless "give permission/reboot(/give permission/reboot" loop.
Google Drive issue didn't get fixed installing MacOS Big Sur 11.3 Beta 7 today, the only difference is now Google Drive ask to be approved at "Privacy and Security" but there is no option there to approve it anymore. Before installing the beta version, I was in an endless loop where I could see the option to approve the system extension, then asked to reboot, then asked to approve it, approve it, reboot, asked to approve....

Now I get asked by Google Drive to enter system preferences to approve the system extension, but there is no option to approve it.

Neither before not now, Google Drive works anymore.
I've had to mount Google Drive from an external computer. That has a lot of drawbacks. Would love for this to finally get fixed on the M1 Macs
I've had my M1 Mac for more than 6 months now and still can't from it as I need to. This Google Drive and Parallels issue is a real sticking point.

Would love for these issues to finally get fixed on the M1 Macs.
Same problem from yesterday after reboot with Google Drive permission loop. No luck. M1 Air.
Same issue here. Endless loop on M1 Mac Mini.
had the same issue on Big Sur 11.2 but now on the loop issue is fixed in 11.3 beta version and it works
Hey guys, after A LOT of digging, I finally found a solution and wanted to share it here to save everyone the headache. Here’s what I did:
  1. Open Terminal 

  2. Run the following commands:

• sudo rm -rf /Library/Extensions/dfsfuse.kext 
• sudo kmutil clear-staging

3. Shutdown the computer 
4. Restart the computer in recovery mode by holding down the power button until Loading startup options appears
5. Click Option and then Continue 
6. Click Utilities > Terminal 
7. Run kmutil trigger-panic-medic -- volume-root /Volumes/Macintosh \ HD
8. Confirm that the output from this command indicates that kernel extensions have been removed
9. Proceed with Step 3, including reboot

Once I started back up, I hit allow, restarted once more, and Google Drive worked perfectly
I'm having a similar issue after reboot with Google Drive permission loop. After rebooting several times, I can finally use Google Drive. I uncheck the “reopen windows when logging back in” when restart.
My Issue
I was having a similar issue when installing Google Drive. In the Security/Privacy panel, it would tell me the extension had been updated and that I needed to restart, giving me the option to click 'restart' or 'not now.' Whenever I clicked restart, it would restart the loop.

What Worked For Me
I clicked 'Not Now' and restarted on my own. When it restarted this time, the extension was properly installed with no prompt to restart.

Hopefully this helps!
I was having the same issue with Google Drive. The solution posted by ahelpfuluser worked for me https://developer.apple.com/forums/thread/667739?answerId=670780022#670780022
Solution from this post https://developer.apple.com/forums/thread/667739?answerId=670780022#670780022
unfortunately did not work for me.

EDIT:
Solution: Install new version (47)

dl.google.com/drive-file-stream/beta47/GoogleDrive.dmg

Worked well.
https://developer.apple.com/forums/thread/667739?answerId=670780022#670780022
Worked for me.
At the end it says "9. Proceed with Step 3, including reboot", but there is no step 3 so I did a
  • 'reboot' from the terminal and

  • once booted did an install from a freshly downloaded "GoogleDrive.dmg" (was version 47.0.17.0).

  • Then approved the extension in the preferences.

  • Chose "Not now" for the reboot.

  • Closed Preferences.

  • Rebooted from the Apple menu.

Thanks,
Solution This worked for me !

Just careful at step 7 the command is : kmutil trigger-panic-medic --volume-root /Volumes/Macintosh \ HD
with no space between -- and volume.


I've had a similar problem installing the latest version of WD desktop application on Big Sur M1. It kept endlessly looping between restart and approve security. started regretting the WD upgrade. Finally, the problem Resolved immediately after updating to Monterey.

Another non-answer: same problem still on upgrading to Monterey 12.3.1 (21E258) — in my case Seagate Technologies. That's external drive management. My view is that Monterey/M1 Silicon is a technology still in development, patchy, lacking some old functions, introducing problems, and compounded by developers not keeping up, partly because it is still a small part of the stable. Apple needs real investment. Since going to M1 there has been nothing but a series of problems and with big names like Microsoft.

M1 System Extension Cache Rebuilding Loop
 
 
Q