32-bit Plug-ins No Longer Available!

There's only a few 32-bit VSTs showing up in the browser and they're all Cakewalk plug-ins. Third-party 32-bit VSTs are nowhere to be seen.
 
Why? Who did this???

sorry... I got 99 probs ....but a Splat ain't one ......
MC7 matters ....   ;o)   
....hope the re-scan works  ....seriously good luck

Hi. Depending on which plugin layout, they might be in the uncategorized folder.
All the best.

I rechecked my VST locations and rescanned about a million times. They won't even show up in the Plug-in Manager. It definitely has something to do with an update.
 
I will try running SONAR as an administrator and see what happens.
 
Thanks, guys.

ampfixer
When you rescan be sure to hit the reset all button prior to the scan.

 
Yes. It's important to reset AND rescan. Depending on the update, it's essential. 

Update:
 
So, there are 32-bit VSTs in the browser (Cakewalk Sound Center, Dropzone, RXP, Square I and Tone2's Gladiator) but it just seems like as long as there are 64-bit versions of a VST, the 32-bit versions won't show... is that it?

telecharge
It's a preference you can set.
 
Edit > Preferences > VST Settings > Hide Related VST2 Plug-ins

This is a VST3 migration setting and has nothing to do with 32/64bit issues
 

Samuel540
Update:
 
So, there are 32-bit VSTs in the browser (Cakewalk Sound Center, Dropzone, RXP, Square I and Tone2's Gladiator) but it just seems like as long as there are 64-bit versions of a VST, the 32-bit versions won't show... is that it?

Generally you would not want to see or use the 32bit version of a plug-in when a 64bit bit version exists. Often times, the 32bit version will not work correctly when a manufacturer also supplies a 64bit version. While I do still have a need for some 32bit plug-ins in SoundForge, they are in a separate path which is not part of the SONAR 64bit scan path. It is best to keep redundant 32bit plug-ins out of the 64bit scan path. Less work for the scanner and 64bit SONAR runs better with 64bit plug-ins.