Hi all!
I'm new to this world and have been trrying to use a few VSTs cracked by Team VR. As you might already know, they are simple executable files. I click on them, choose the folder I want the VSTs to be installed (C:Programfiles/VSTPlugins) and let it do its thing. However, once installaiton is finished, the vsts are nowhere to be found. Program directories are there but no sign of .dlls.
Anyone has any clues as to what could be happening? Thanks!

 

Wellcome to the forum.
As i remember,you have a choice to install it to another place...., If you know precisely the name of the plugin, you can try to find it with this(below)search engine.
Its portable, just run it and(it will take a moment to index your files)search for the particular name of the plugin...!

Everything Search Engine:
https://www.voidtools.com

 

@Abbienewbie This thread has an improper title. Your problem is not that you are not able to install Team VR's plugins. Your problem is that you can't find the plugins that you have installed because the path has been changed in the registry. Therefore, you should edit the title to avoid confusion. I have attached a file that will set the path that you wish to have for your 64bit VST installations. Let me know if you need one for 32bit plugins. Simply unzip and double-click on it.

 

is your Antivirus deleting them?

Change your antivirus

 

Tried to reproduce your problem on a virtual machine but it always installed the dll's.

Stupid question:
Did you select to install the VST2 plugins? By default in most VR's installers, only VST3 and AAX are selected,
VST2 installs optionally by manually selecting them.



There's just one problem with VR's installers - they create a dir even if you not select to install VST2.
They just didn't link the dir selection to the decision from the components page or forgot to add the exception

Code:

if
(not isComponentSelected('VST2 64...')) then
begin
    DirPage.Edits[Browse64].Enabled := False;
    DirPage.Button[Browse64].Enabled := False;
  end else begin
    DirPage.Edits[Browse64].Enabled := True;
    DirPage.Buttons[Browse64].Enabled := True;
end;
...and probably add CreateDir := False;

So if they simply would swap the pages and add an exception, the empty dirs wouldn't be there.
Had the same problem when creating my first multi-dir installer.

So I added the exception which disabled the creation of the empty dir to not confuse the user.




An even easier solution would be to auto-delete created empty folders after the installation
if the component isn't selected (if VR reads this thread)

 

Last edited: Sep 21, 2019

If you chose to install a VST3, opposed to a VST2...

For 64 Bit VST3's, Look In: C:\Program Files\Common Files\VST3

For 32 Bit VST3's, Look In: C:\Program Files (x86)\Common Files\VST3

If you chose to install a VST2, opposed to a VST3, the most likely explanation for plugins not appearing in the selected directory, after multiple attempts, is that your anti-virus is automatically deleting the files.

 

Oh another thing. If you use Avast Anti Virus like me, turn off folder protection.
I had that option on and Avast locked specific folders like Documents and Appdata
so nothing was allowed to write data into these folders.

 

u use antivirus or firewall, they mostly block, change or delete vst s