64/32 bit VST Plugins Paths confusion

Hi I am having a lot of difficulty understanding the 32/64 bit concept. Let me explain my story (sorry this will be long)
 
First I bought Windows 7 and asked for 64 bit version to the salesman. It is writen in small carracter on the DVD that it is 64 bit.
 
In comes Sonar Platinum and Control center:
 
After bying Sonar Platinum I started downloading and installing stuff from the Command Center. Half way through the process, I clicked on the Command center settings button by curiosity and I recieved an error message: Please correct the following errors: 32-bit VST Plugins and 64-bit VST Plugins paths must be unique
 
Pardon me for saying but, why in hell doesn't the Vst paths set themselves automatically, and if not, why doesn't Command Center warn you in plain vue instead of waiting for me to click on the setting button by chance??? But worst of all, there is no instruction as to where to put the paths nor how to name them!!
So I posted my question on the forum and I recieved the following message from the Forum Host: Change the 32 bit path to  C/Program Files (x86)/Cakewalk/VstPlugins... I asked for clarification about that but the forum host never explained!
So I created a folder named "Vstplugins 32" in the path: C/Program Files (x86)/Cakewalk/VstPlugins and then  and renamed the existing  Plugin folder in the C/Program Files/Cakewalk/VstPlugins path "Vstplugins 64" I then went into Sonar's pereferences menue and changed the VST Paths to both of these paths and deleted the original paths, so Sonar would look into my new paths when doing a VST scann. I then went on and finnished downloading and installing the items from the command center. 
After downloading everything I went and took a look at my VST folders in the finder and realised that Sonar had created new VstPlugins folders (with plugins inside of them) alongside the two that I had created. I now had 4 Vstpluggins folders, two 32 bit folders and two 64 bit folders. I then thought to myselfd that naming the folders "Vstplugins 32" and "Vstplugins 64" was a bad idea because Sonar whent on to create folders in the same locations without the 32 and 64 mention... So what I did is take all the plugins that were in the "32" and "64" folders that I had created and dragged them manually in the new folders created by Sonar... Then I recieved an error message from Addictive drums saying that there was a problem with the plugins paths. So I went into the XLN installer app and changed the 64 bit path to the path where I had tranfered all the 64 bit plugins. But XLN refused to recognise this path so I put back the Addictive Drums plugin in the "Vstplugins 64" folder...
So now I have three VST plugins folders: two 64bit ones, and one 32bit one. The "Plugins 64" folder has only Addictive drums in it... Both other Vstplugins folders, if I look into them, seem to have all the same plugins (all of them)..  Another freeky thing is that when I go in the Sonar browser and look for VST plugins and instruments, many 64 bit plugins have the "(32 bit)" mention alonside there names: "Session drummer x64 (32 bits)" and "Rapture Session 64 (32 bits)..
To finish, I wanted to load a Tutoral session in the Platinum Sonar content and I recieved the following error messages:
 
Multisample not found f:/cakewalk/rxp/loopmaster/dnb/producer/drum/db_170_k08lp02.rx2, 
 
Missing Plugins The following plugins were refered to but could not be loaded because the are missing or improperly installed 
Session Drummer 64x (Synth Rack)
Pentagone 1 (Synth Rack)
 
Sure enough, when I look in the browser I see Session Drummer x64 (32 bit), and as for Pentagone 1, it can not be found anywhere
 
Why is it so complicated!?!?!?!?!?!?!?!?!?!
 
Can some one help me PLEASE
 
Thank you
 
 
 
 

That is what I would do. Reinstall it all. Sonar 64 can in most cases handle 32 bit VSTs due to Bitbridge. A utility that lets Sonar 64 bit use 32 bit VST plugins. However, its a good idea to stay away from using 32 bit plugins in Sonar 64 bit if you can.  Most VST plugins are now both 32 bit and 64 bit. I wold not install any 32 bit VST plugins if there is a 64 bit version. 
 
Many of us bit the bullet and moved on to full 64 bit a long time ago. Because of that all of our plugins are 64 bit.  Of course when you have a very useful plugin that has not been updated to 64 bit it may be hard to abandon it. One thing I have found is there is always an alternative.    

So you may have previously explained this but to be clear..


Have you gone into CCC and checked the VST file paths to make sure they are unique? The 32 bit path should be somewhere outside the scope of the VST paths set in Sonar preferences if you aren't interested in 32 bit, either way must be different.

Forgive me for stating the obvious, just clarifying.

Before you correct this you may fare better with an uninstall/reinstall. I also recommend verbose mode in CCC settings.