Hi, was just wondering what people did in regards to placement of the vst plugins? Do you follow the normal suggested location or do you place it in an easier and accessible place ie C: Vst plugins.

Hi. I use the default Cakewalk\VSTPlugins, both x64 and x86. You can use different folder, but if it not on another drive, I do not know of any advantages by doing it.
(I do however have the samples and content on separate drive)
Best of luck

I placed my VST in
 
C:\DAW_VST\32   (for 32 bits)
C:\DAW_VST\64   (for 64 bits)
 
And add these folders for vst scan.
 
I will also add sub folders within, such as
 
C:\DAW_VST\64\AAS
C:\DAW_VST\64\FXPansion
etc...
 
This is much clearer than default \Program Files and \Program Files (x86).
 
But the main reason I do this is due to the included Nomad plugs that only works on current version of Sonar.
 
I have the full purchased Nomad plugs that I used to placed in the default Vstplugins folder. Then during an update, Sonar replaced all these open plugs to closed ones. Putting it away prevent any of this from happening in the future.
 
 

Is there any disadvantage not to place cakewalk's vst in their own directory?

I'd recommend putting the 32 bit VST2 folder outside Program Files (x86): some 32 bit VSTs are old and expect to be able to write to their installation directory, which is blocked by UAC if the folder is in Program Files (x86) or below.  Moving the whole path outside there removes that issue.
 
x64 programs aren't allowed to write to Program Files folders, and VST3 spec defines the path (C:\Program Files (x86)\Common Files\VST3) so presumably are also written to work properly (so that folder is safe).

Thanks. so C: Vst plugins. looks viable and practical option!

It will work. Just remember to specify folder for vst scan.

I suggest sticking with the defaults that follow Windows conventions. Moving stuff around to non executable locations can cause user account control problems if you are not running as an administrator.
For exception cases where you have old plugins that are not UAC compliant you can put those in a different location.

Agreed with Noel.
 
I have to add that I only place VSTs in alternative folders for those installations that asked for for it. I leave Sonar default installation to where it installed.

What I do is I create a desktop shortcut to any hard to find folder I might need. 
So it doesn't bother me when a folder is in an obscure hidding place. 
 
On the topic of folders, a new trick I just discovered when I built a computer for my Daughters family. They need things simple. I used a 126 SSD for C  and 2TB DATA drive. But having a data drive serves no purpose when people use default document, music and picture folders. The little SSD will be overlowing in no time.
Then I discovered those default Document, Music and Picture folder icons  can be re assigned to the data drive.
So now their "library" directory only goes to the data drive. There is nothing defaulting to C drive. Right click the icons / properties. But do it right away after the OS install.