reinstalling Soundflower required after each reboot after migrating - Big Sur

[mOnZtre]

After I migrated my Big Sur system to a new intel mbp, I noticed soundflower was missing from audio settings.

So after reinstalling Soundflower without a hitch and verifying it was all good and working, I went on my merry way and life was good... until I rebooted that is. and then I noticed that soundflower was missing again. grumpy

when I noticed Soundflower was missing from the sound preferences pane,
I checked to see if the extension was where it is supposed to be, and it was:
/Library/Extensions/Soundflower.kext

but it is not loading on reboot.

At this point I can either do one of two things,
both of which result in soundflower once again becoming available in sound preferences -
1. reinstall from installer

 2. run these commands:
    sudo chmod -R 755 Soundflower.kext
    sudo chown -R root:wheel Soundflower.kext

each "fixes" the issue, and I can happily use soundflower, but after rebooting, the extension once again fails to load.

I've tried the following without solving my issue :

• completely uninstalling
• sudo kmutil clear-staging AND sudo kextcache -i /
• sudo tccutil reset All ( for good measure , didn't know if that would trigger having to reauthorize "matt ingalls", but it didnt)
• reinstalling with signed version ( https://github.com/mattingalls/Soundflower/releases/tag/2.0b2 )

I'll note that during all my reinstallation efforts, the installer has never failed, and I've never had to reauthorize developer "matt ingalls" . I thought if I could somehow reset previously allowed developers I could force reinstalling truly from scratch, but I can't figure out how to do that without reinstalling the os completely.

I've migrated my system to new machines before and never had this issue. I would love for soundflower to be ready and good to go after rebooting without jumping through hoops. Any assistance would be appreciated! Thanks for your help!

[dbh13]

I'm not able to help but have the same problem. What I can add is that I ran Soundflower on a MBP under BigSur (currently 11.6.5) without any issue for several months and sometime within the last month, it "disappeared". My experience is the same as yours - I reinstalled the signed version, thought it was okay, but it lasted to the next reboot. As per your experience, the soundflower.kext is present and I can start it using the method you describe.