Fix VST cannot be opened / developer cannot be verified in MacOS Catalina, Big Sur, Monterey

Have you been hit with the ominous message that a VST "cannot be opened because the developer cannot be verfied" when trying to use plugins in MacOS after upgrading to Catalina (version 10.15), Big Sur (version 11) or Monterey (version 12)? Fear not, this video will help you fix it! And this fix will work, contrary to some other fixes involving using the Security & Privacy applet of System Preferences.

In the video I'm using Reaper to display the problem and the solution, but the fix is not related to Reaper and will work for any DAW that uses VST plugins.

I strongly recommend upgrading your OS, since it's the best way to stay protected from viruses, malware and exploits. However, I know that a lot of musicians put off upgrading - sometimes forever. The reason is that you don't know what will break, and Apple is notorious for introducing new security features or dropping legacy support that could affect your DAW or your plugins.

The protection against downloaded executables (Gatekeeper) got a lot stricter in MacOS Catalina, which has caused problems, particularly with VSTs. But with this solution you can upgrade and thereby stay safe, while continuing to use your VSTs.

Caution! Only use this fix on VSTs that you know can be trusted, with no viruses or malware.

00:00 The problem with VSTs in MacOS Catalina
02:41 The wrong solution
03:40 The correct solution
05:15 Some questions (and answers)
05:52 Outro - like and subscribe!

Equipment and software used:
- Reaper 6.50
- Davinci Resolve
- Pixelmator Pro
- iTerm2
- Canon EOS 760D

[DaMooCow]

I can not tell you how much of a relief it was to come across this video. I've been migrating my entire ecosystem (daw, plugins, projects, etc.) from a windows pc to my first mac. When I ran into this issue, I wasn't sure there was a solution at all, so finding this video was so helpful! Thank you for finding and sharing this solution!

[Mojokiss]

I had to create a new VST folder in a place that allowed me access by Terminal, and add the path to FX plugins to rescan in Reaper, even after giving full disk permission. But then this was helpful and worked for me and I finally have my reverb plugin. Thanks.

[julianchavez]

Must be stressful being a genius. This DEFINITELY works! Thank you.

[shivercanada]

Got it to work in Sonoma! You have to DRAG in vet or component to terminal after typing the above, not just type the name of the plugin and it worked for me thank you!!!

[matsthys]

July 2024 and still works!! Thank you so much for this tutorial and clear instructions!

[yukeemusic]

wow thank you so much for this tutorial <3
I was stuck at first because I didn't know how you got to the folder but I found you replied to that below another comment. so for other noobies: press cd and then and then you get there and can continue like he describes in the video

[MorisoniProductions]

Just to say a huge thank you for a super-clear explanation and workaround for this issue. I have just upgraded to Big Sur, and so far the Terminal fix seems to be working for me, using VSTs within Cubase 12.

[joshuaorr]

Thank you so much for this video, sold a PC I built because I stopped playing video games as much and I bought a Mac because it interfaces into most of my life a little better but man every time I run into an issue like this it makes me want to sell my Mac and go windows again. Much appreciated information

[thepedalpress]

Nice! Bingo. Was tough using Terminal as a noob. Ended up dragging and dropping directory from Finder that was denied permission to access.

[przymrozek]

Awesome tutorial! Worked for me on MacOS 14.6.1. The only difference was that Reaper could not load the VST (it was a freshly installed one), so I could not load it onto a track; I had to go to that failed to scan-->select the plugin (after I removed the quarantine parameter as you described in detail in the video). Then the plugin simply showed up! Thanks a lot :D

[vidak.]

Oh my god MAAAN! This worked just SUPER fine!
One note - for some plug-ins you need also to clear quarantine from "Components" folder the same way

[christsampson]

YOU ARE MY HERO FOR THIS!!! this video should have way more views. Thank you!!

[merrimac]

Had to log in just to say thank you. Shout out to all the creators who post solutions to obscure problems, you the GOAT!

[rhythmace]

Thanks for this! It's not the first working solution I've come across for this issue, but although I don't remember what the first one was, I do remember it was fiddly and not very intuitive, hence me not remebering it! I'll definitely remember this one, it's clearly the most direct and logical route to a resolution. Cheers!

[beegee]

super helpful unlike pretty much all of these types of tutorials. thx brodie

[donovanrebbechi]

thank you ! This worked like charm, those popups had been bothering me for quite a while

[rishabhsingh]

Dude such a niche topic and of course there's a vid for it, props we need more people like you and its why the net exists!

Thank you, you’re a lifesaver! Nice drop C riffing in the background 🙌🏻🤟

[MrKjellstrand]

Thank you so much! Now I can listen to old DAW tracks again :)

[alessandrog]

THank so much and subscribed!!! it worked exactly like you said. I'd like to add one thing tough, if you just type the name of the vst it might not work. so the solution is simply drag and drop the whole vet file inside the terminal instead write the name of the file. it gonna write down automatically the address location of the file then everything like you explained. Thanks again!