I'm having trouble getting this to install as 64-bit plugin - keeps saying it's 32bit. What am I missing? System is windows 7 pro, 64-bit, don't see an option to choose in the installer, either..... any thoughts from those of you who've installed VS-2 over VS-1?

not a bad idea, dmbaer, but I do believe it's going through the whole installation based on the dialogue boxes. I might need to just go back and try again. I'm pretty sure the folders are pointing the right way, etc - just doesn't seem to load the 64 bit plugin.

I have to double check the path to be sure when I'm back home. Thank you for the suggestion!

bitflipper
I've had the same experience with other plugins, and wasn't sure if the installation was 32- or 64-bit until it was done and I went to check where the files ended up.
 
Usually, if it's under c:\program files\cakewalk\vstplugins, it's 64-bit. If it's under c:\program files (x86)\cakewalk\vstplugins, it's 32-bit. (Although for some reason I have Zebra64 living in the x86 tree, so it's obviously not a hard-and-fast rule. It was probably my mistake when I installed it.)
 
Some installers will install both versions, but you can just delete the 32-bit version if you don't plan on using it.

I use a very specific plug-in directory organization - this was suggested by someone on this forum a couple years ago.  I let DAWs install their stuff wherever they want.  But everything else goes under:
 
Program Files/VST Plug-ins/vendor-name (and similar under Program Files (x86) for the very few 32-bit-only plug-ins I keep around).
 
I can tell you with confidence that AAS plug-in installs allow me to easily follow this scheme - I'd certainly remember if they did not.  That's not saying they don't default to the location Dave is talking about, but the point is, I am confident that the installer asks for your preference.  The only plug-in I recall giving me problems along these lines recently is the Loom synth from AIR.