Hi really can't find an answer on-line so hopefully someone here can help. Every time I install a VST the installer defaults to a previous install folder (Independence Pro)in my VST 2 (my name VST64)default folder. I have to Browse for the correct install folder every time. How do I remove this location default (Independence Pro)to which I didn't make? It's like Windows decided that's were everything should be installed and made it a default location. Any Tech guys know how to change this would be appreciated

 

Many installers are badly developed - they cannot detect where the 64-bit VST 2.4 "home" folder is located when this folder is correctly declared into Registry!

Some of these installers always assume the "default" folder such C:\Program Files\Vstplugins or C:\Program Files\Steinberg\Vstplugins ... and don't care about the Registry key/value.

I'm using C:\VST64 too on my rig.

NOTE: VST3 doesn't need Registry key/value because plugins are always installed into C:\Program Files\Common Files\VST3 (and subfolders), to follow Steinberg convention.

 

Last edited: Nov 27, 2022

To expand on @MozartEstLa 's correct answer: there are two registry entries, for 32 and 64 bit plugin paths.

You can save this to a file:

Code:

Windows Registry Editor Version 5.00

; VST 64-bit path
[HKEY_LOCAL_MACHINE\SOFTWARE\VST]
"VSTPluginsPath"="c:\\vst64"
; VST 32-bit path
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VST]
"VSTPluginsPath"="C:\\VST32"

Adjust the paths to your liking, name it "vstpaths.reg" (or whatever, as long as the extension is ".reg") and run it. Make sure that there are no empty lines before "Windows Registry Editor Version 5.00" and the paths have backslashes doubled and you're good.

And as MozartEstLa said, not all installers respect this, and some might fuck with them, as you've experienced.

Hope this helps!

 

Please be careful in giving advice like this. Especially using the registry. Some vst2's can depend on residing in other directories?

 

What do you mean, please explain?

By official spec the plugin path only specifies the location of the .dll or .vst3 file/bundle, locating everything else (like patch or wave data) is done by the plugin itself. If the plugin then relies on those registry keys (which no plugin does), then the resources are already installed there.

 

Big Thank You to @MozartEstLa & @phumb-reh really appreciate your help with this It's been driving me nuts so finally popped the question here. Many Thanks

 

Ha!! Just went to that location to do a subkey and there's already one called VST and guess what!? in the data value is the C:\VST64\INDEPENDENCE PRO\ Name being VSTPluginsPath !! So I'm assuming I just need to change that the above to correct it? Really don't understand how that got written into the Reg but like you said bad code I suppose .Thanks again for your help would not have even known to look here in the Reg. Thanks

 

Agree, I've used that registry key to set my install location to something else for several years now. Zero issues at all, and I've installed hundreds of plugins. If a plugin needs to install something in an exact folder, it's not going to look in the registry for that location... at least not this registry entry.

This is a regular process that a lot of people do.

Yes

 

I decided to name mine with numbers first to keep them at the top of the folder hierarchy.
Then i decided to symlink certain VSTs into folder for use with audio editors and other MM progs that don't need to scan everything.

And I decided to have "-hold' folders to keep VST files i MIGHT need (usually VST2 if the VST3 versions are buggy), but also for alternate GUI replacement DLLs, and my old Massive DLL for batch converting old KSD files, (+ a savihost-made .exe with it) and other folders like that.

(I keep a copy of Savihost for VST2 in my main VST2 folder. I have VST3s associated with Savihost for VST3s, so i just double-click them and they load as .exe)

After some years it's just how it evolved.
And my VST3 folders are the same , but the main VST3 folder syminked to the normal location of "Program Files\Common Files"

 

I stand corrected because your registry fix seem to have worked perfectly for the OP.

Usually I'm reluctant to suggest such settings involving the registry, because not all people understand what and where to adjust.

But in this case I have to admit that your suggestion helped the OP to solve his problem

 

The key (HKEY_LOCAL_MACHINE\SOFTWARE\VST) and its string/REG_SZ value (VSTPluginsPath) must be unique, aka... for ALL VST 2.4 plugins (not for a specific plugin).

The best way is to place your plugins into subdirectories (eg by vendor),
for example C:\VST64\Arturia for all Arturia plugins, C:\VST64\Synapse Audio for all Synapse Audio plugins, and so on.

But the Registry value set in Registry must stay as C:\VST64
(sort of root/home folder for all VST2 plugins).

 

I agree, I don't have mentioned 32-bit, because... I don't have 32-bit VST2 plugin on my rig (I avoid them).
But I confirm the "WOW6432Node" for 32-bit plugins on 64-bit Windows.

 

Last edited: Nov 27, 2022