Specific Installation Path on Windows

[Matt_SF]

Hi folks,
I'm facing something weird, maybe some of you had the same problem :

My exported VST3 instrument is not recognized by some DAWs if it's installed in a custom plugin folder.
In order to be "seen", it has to be installed in this specific location :
"C:/Program Files/Common Files/VST3" -(didn't try with other Steinberg's default plugin folder)

Concerned DAW are (so far) : Cubase 11, Reaper, FL Studio, Maschine.
Gets correctly recognized by Ableton Live & Studio One.

VST2 plugins seem to be always recognized, and VST FX plugins : meh, sometimes they are recognized, sometimes not...

Has anyone any clue on how to solve this ?

Cheers !

[d.healey]

Do other VST3 plugins placed in custom locations show up in those DAWs?

[Matt_SF]

@d-healey yes I usually install other companies VSTs in a custom folder and never had any problems. Only my plugins are messing around

[d.healey]

@Matt_SF Check the meta data in the project's jucer file, there might be something in there you need to change.

[Matt_SF]

@d-healey ok thanks David, i'll take a look and report back !

[Matt_SF]

@d-healey So I found this :

changed it to :

but didn't get any luck.

Update : Reaper did found my plugin, I think it was my mistake.

I'll continue to investigate ...

[Matt_SF]

So after looking around everywhere, there seems to be a simple answer :

Unless your DAW allows you to select a custom VST3 folder, you have to install them in Windows default location which is "C:/Program Files/Common Files/VST3".
One can be fooled because Cubase and FL Studio allow you to set custom locations but it only works for VST2 plugins.

As Steinberg's putting it : "The VST3 format has a dedicated installation path all VST3 plug-ins must comply with." Simple.

@d-healey And I can confirm that other dev's VST3 plugins are not recognized by Cubase either. I didn't pay attention to that as I was focused on finding my plugin.
I never noticed it because I only use Ableton live and it does allow you to choose a custom VST3 folder.

[d.healey]

@Matt_SF I suspected that was the reason :)

[Matt_SF]

@d-healey Hehe I saw it coming but now I know
Thanks for your help David !