Hello I installed the Waves bundle at Sonoma. It was working fine until I make some changes about the security policy within OS. I believe I was using in Reduce Security mode. I enabled the kernel extension control for disk accessing purposes. Later I disabled it but in the meanwhile I realized AUs are not working anymore.I'm not exactly sure If those were related somehow. To me it looks like a permission problem. Now I returned to Full security mode and it did change anything. VSTs of Waves and all other AUs still fine. I ran the ''AU Reg Utility 14'' from Waves app folder and its failed to detect AUs.

How can I fix this?

Thank you

 

I'm just doing a quick read of this: https://support.apple.com/guide/deployment/system-and-kernel-extensions-in-macos-depa5fb8376f/web

Screwing around with kernel extensions and system wide Root can be a terrible idea for most users. Can you show what you did exactly, to cause your problem? Or maybe link to some instructions you followed....

For right now, I would disable SIP and see if your plugins begin working again. You can either call SIP Disabled a temporary workaround for your current snafu, or you can just run with SIP disabled. (not recommended, usually).

from above link:


Kernel extensions with System Integrity Protection

• If System Integrity Protection (SIP) is enabled, the signature of each kext is verified before being included in the AuxKC.
  
  
• If SIP is disabled, the kext signature isn’t enforced.

This approach allows Permissive Security flows for developers or users who aren’t part of the Apple Developer Program to test kexts before they’re signed.

 

oh, this probably doesn't matter; but when you have something go wrong like this you can need to re-codesign plugins. Run this in terminal and it will re-codesign every plugin on the machine. Let it run, it takes a few minutes:

cd /Library/Audio/Plug-Ins/

find . -name "*.bundle" -execdir sudo xattr -cr \;
find . -name "*.VST" -execdir sudo xattr -cr \;
find . -name "*.vst3" -execdir sudo xattr -cr \;
find . -name "*.component" -execdir sudo xattr -cr \;
find . -name "*.dpm" -execdir sudo xattr -cr \;
find . -name "*.bundle" -execdir sudo codesign -f -s - {} \;
find . -name "*.VST" -execdir sudo codesign -f -s - {} \;
find . -name "*.vst3" -execdir sudo codesign -f -s - {} \;
find . -name "*.component" -execdir sudo codesign -f -s - {} \;
find . -name "*.dpm" -execdir sudo codesign -f -s - {} \;

And you could also use BatChmod on your /Components folder and let it apply to all subfolders too.

 

Thank you for reminding about kernel settings. Yeah I read that its a little bit risky option but I had to do it. I was trying to access and edit some files on an uncompatible disk format for Mac. I install a couple of softwares like Tuxera Disk Manager. I think I also made some terminal commands but Im not sure right now what was all those about.

I return to Reduce Security option now, which it was like that when I use AUs normally.
This is a representative image, not my settings. I only choosed Reduce Security and disable additional permissions related to kernel extensions.




I tried to re-codesign within terminal it successfully completed but did not solve the issue.

I also gave a shot for BatChmod. It did not solver either. All the procedures about those attempts looks successfully completed. I tried to use AU Reg Utility after each attempt, every attempt failed. I restarted the OS a couple of times and tried to clean temp and leftovers with additional software. Reanalyzed plugin folders with Ableton in different states, not fixed.

Thank you for your time and effort

 

well, I did not want to suggest you skip any of the easy possible solutions. If one works, you are done. I found myself in a similar boat a few weeks ago, trying to force a kernel extension for an old hardware pci card. The least time consuming option to me, and the only one even remotely suggested by any of the Mac tech site was the good old "save and pave". Is it possible to fix? Sure. But no-one is going to take the time going through all gyrations involved to fix it. Unless they do not have a current Time Machine backup of the system.

I ended up just doing a restore and was back to normal in a couple hours. Sometimes your options are to fish or cut bait.