Now that I have installed the Kontakt 5 Player VST, I'm wondering if I put the dll's for the vst on the correct path.
 
The default for the install put the VST dll files in :C:/Program Files/Cakewalk/Vstplugins/.  Now I'm wondering if I during the install I should have changed from the defallt and put them in C:/Program Files/VstPlugins/
 
I don't care all that much where they are, but my primary concern would be that, during a Sonar upgrade or reinstall, the Cakewalk/Vstplugins directory gets over-written or some such thing and deletes the Kontakt dll's. Anybody know if that can happen?
 
>Is it possible to just move the dll's to the other path? I know that some folks say that can lead to problems.
 
>Should I uninstall and reinstall the Kontakt 5 Player?
 
>Should I just leave as is?
 
Suggestions/Opinions welcome!
 
Thanks-

What I generally do and has worked well for me is:
 
Make a separate folder (i.e Paid VST) for all 3rd party VST's and its kept here: C:/Program Files/Cakewalk/PaidVst
Within the Paid Vst folder, I make subfolders for each company's VST (IK, NI, Toontrack etc...) and direct the VST's (during installation) to those respective folders.
 
I leave the C:/Program Files/Cakewalk/Vstplugins folder just only for Sonar stuff and don't install anything within that.
 
It's better to have it all setup efficiently rather than try and move them to a different location (some of these installers can get confused easily and do something unwanted).....so, if it's not a chore to uninstall and reinstall to a set/desired folder, that should work out for the best.    

Unless you completely uninstall SONAR first, an update won't disturb your Vstplugins folder.
 
Getting creative with plugin folders often leads to headaches later on.
 
For example, say you install a product in a custom location and later update it but forget to specify the custom location, allowing the product to be installed in its default path. Now you've got duplicate instances and it's difficult to tell which one's current when inserting plugins. I've wound up with duplicate Kontakt DLLs doing that. It was not an easy mess to recover from, as I'd referenced DLLs in projects from both locations and therefore couldn't simply delete the dupes. Nowadays, with some exceptions, I let products decide where to install themselves.