This is getting worse instead of better. I am not a Mac user and cannot help you with your decision to switch.

1.) Audio plug-ins not working any more
FWIW, Eventide have confirmed that it is a bug introduced by Apple in their upgrade to the MobileDevices framework.
They suggest an upgrade to 10.13, which I'm reluctant to do at the moment, despite having safe copies of the boot disk, etc.
https://discussions.apple.com/thread/253769152


2.) safe mode may help diagnose existing problems. For macOS HighSierra.

Note: Before you begin, to print this guide, click the Share button in the Help window and choose Print.

1. Choose Apple > Shut Down.
   
   
2. After turning off your Mac, wait 10 seconds and press the power button.
   
   
3. Immediately after your Mac starts up (some Mac computers play a startup melody), press and hold the Shift key.
   
   
4. Release Shift when you see the gray Apple logo and progress bar.
   

To exit safe mode, restart your Mac. Don't press any keys when starting.

https://support-apple-com.translate...l=auto&_x_tr_tl=en&_x_tr_hl=de&_x_tr_pto=wapp

 

Finally i had some kind of success.

I just installed a clean version of MacOS Sierra on an external SSD and did a migration from my problematic Sierra system to the newly installed SSD.

Now nearly every plugin is running again in Logic and also Wavelab when i start the OS from the external SSD. Only a handfull of plugins didn't validate with "couldn't be opened" "crashed validation" and "failed validation". But i think i can fix this with reinstalling or updating.

The next thing i will try is to install Sierra over my current problematic Sierra installation. Hopefully this will fix all errors in the same way.
If this is not working i have to install a clean version on my system drive and do a migration like i did with the external SSD.

I will keep you updated. Thank you for all your help guys!

 

Ok, so reinstalling MacOS Sierra over the corrupted MacOS Sierra on my System Drive did not work. Everything was like before. Every error was still there as if nothing happened. I thought that could fix it but it was not the case.

So i decided to delete my system drive, installed a clean version of MacOS Sierra. Migrated all the data from my new external MacOS system. I also have a timemachine backup from mid april 2022 but i took the data from the external OS which was already working.
After the procedure i've also reinstalled a clean OS over this one just to be sure.
So now everything is working fine again like on my external OS installation.

Again thank you for all your help! But i'm still curious what was causing this problem.

 

i found the problem while doing a manual look inside my HD and found slatedigital has a lot of malware attached to it. I deleted every instance of anything slate related and it got rid of that issue. the only issue i get now is the a kilohearts issue so i now have to find where that file is. Not sure if that might help anyone. I had a ANA 2 problem as well and it was running fine but then the patch disappeared and needed ilok activation but i just got rid of the program itself in its entirety.

 

Hi Greg,

I've recently run into a similar issue with my Roland plugins, and also with Reaktor (all the other NI VIs load fine though).

I also use DSP Quattro (as a Mastering DAW) and all my plugins load OK in DSP Quattro (Roland and Reaktor). So the issue is Logic.

I upgraded from Mojave to Ventura - and to Logic 10.8 from 10.5.1 - never had any such problems with the old setup.

Anyway - wanted to share this:

Hopefully, it can help you and/or others reading this. It's an $8 purchase. Well worth it.

Cheers!

 

All this application does is force Logic's AUValtool to "see" the plugins which need to be validated. It does nothing to actually fix the problem AUValTool is reporting. The application OSX Validate All AU's does the same thing, and it is free. That application above just works on some newer versions of MacOS. Charging people money for a little utility app like this is pretty "bold".

The actual problems can be Crashing Validation due to incorrect MacOS version or processor type, Permissions, or Code Signature, etc. All that force validation will do is force the AUValtool to check the installed .component plugins; and usually will do this without a reboot.

Once this shows on AuValtool output window, the plugin is being evaluated already. Otherwise that window would remain completely empty, like it isn't doing anything. Validation is just failing:
--------------------------------------------------
VALIDATING AUDIO UNIT: 'aufx' - 'SCii' - 'Abrn'
--------------------------------------------------

 

Last edited: Nov 15, 2023