Initially I had the same problem in that Sonar froze when I tried to use it. I found that the 64 bit VA-2 dll was in a different place than my normal VST folder while the 32 bit was in the correct folder. Once I moved the 64 bit dll to my main 64 bit VST folder and rescanned everything worked fine.
 
I don’t know if that is your problem or not but I thought I would explain how I got mine to work.
　

jimusic

Photo_G Could this be a permissions issue? I installed VA-2 as admin, and run SONAR as admin, and it works perfectly for me here (x64 too).
G

This is something I had not thought of G.
 
I'm the only one who uses that computer, so I just take all that for granted, especially since everything else works fine, but perhaps you could refresh my memory on this.
 
What step(s) do I need to do before/during the install process to make sure of this?
 
I have installed this thing twice now, with no difference in behavior, [although not everything may have been completely uninstalled - it was 3 or 4 AM - ].
 
Thanks,
 
Jim

Hi Jim,
 
When installing VA-2, right click and select "Run as Administrator",  Then do the same with SONAR when you launch it.
 
G

Thanks kindly to both MarioD and Photo_G.
 
I will do all these things and report back later tonight or tomorrow with hopefully good news.
 
Thanks Buds,
 
Jim 

I had tried VA2 in X3 64 bit. No issues work fine. The only problem is my A500Pro controller did not work well with knobs reassignment. I have no problem reassign knobs from my Korg Krome synth. Other than that the synth is PHAT! My question is I own synthmaster fully upgraded, Harmor and Zeta+2. Do I still need to take 49 bucks to upgrade from ultra analogue session?

MarioD
Initially I had the same problem in that Sonar froze when I tried to use it. I found that the 64 bit VA-2 dll was in a different place than my normal VST folder while the 32 bit was in the correct folder. Once I moved the 64 bit dll to my main 64 bit VST folder and rescanned everything worked fine.
 
I don’t know if that is your problem or not but I thought I would explain how I got mine to work.
　

I discovered the same thing. The installer installed the 32bit version in the Cakewalk VST folder but install the 64bit version in the AAS Program folder. The installer does not give you the opportunity to choose. Once I moved the 64bit version to the correct folder and excluded the 32bit version, all was well.

I'm seeing the VA-2 .dll in both Program Files & Program Files (x86) menu trees, and they're identical. 
 
EDIT:  Ok, looks like that has worked - moving it, that is.
 
When I re-scanned Sonar, the (32 bit) tag as no longer visible in the browser window, and it loaded up properly, which was the first time it did in that DAW.
 
I was then able to switch banks & patches just fine, including any buttons.
 
I then tried it in Cubase with the exact same results, [except I had to do nothing at all in Cubase], so that must have been all it took.
 
Whenever I install a new synth, I name a project by it's title to see if it will load up.
 
So I guess Cubase re-scanned it by itself, upon reopening that project, which it looks like it always does at the start-up logo, hence the short wait time of a few seconds.
 
I hit record and laid a few tracks down using different patches just to be sure.
 
So Happy Thanksgiving [depending which country you're in] and thanks for giving me the solution here. 
 
Cheers Buds!
 
Jim

Hey...64bit version works okay my X3...that is, when I put my glasses on to see everything it! It is so tiny on my 2560x1600 monitor and not much bigger on my 1920x1080. Rob Papen's Blade is the only soft synth I own that can be re-sized for larger screens.

Fabio Rubato
Hey...64bit version works okay my X3...that is, when I put my glasses on to see everything it! It is so tiny on my 2560x1600 monitor and not much bigger on my 1920x1080. Rob Papen's Blade is the only soft synth I own that can be re-sized for larger screens.

Yes, it is hard to read that small isn't it?
 
On my 18" monitors, I have the resolution set at 1366 x 768 and it is still a bit tough to see.

I had the same problem - not seeing VA-2 in the plug-ins.
 
The owner name on the VST DLL was 'Administrator', but all my others are 'Jim', so I changed the owner.
 
Then I reset the VSTs in Preferences and re-scanned. 
 
Now it shows up.
 
The same thing happened in Live. The fixed worked for it, too.
 

arachnaut
I had the same problem - not seeing VA-2 in the plug-ins.
 
The owner name on the VST DLL was 'Administrator', but all my others are 'Jim', so I changed the owner.
 
Then I reset the VSTs in Preferences and re-scanned. 
 
Now it shows up.
 
The same thing happened in Live. The fixed worked for it, too.
 

Very interesting...Never seen that before.
 
But glad it worked out.