I think I've narrowed it down to a bitbridge issue.  At least what I could find searching the net.  But no solutions that I've seen.
 
Until this last update, all 32bit and 64bit plugins worked perfectly.  Since the update I get the "teleport server" error when opening mixir2(32 bit) which locks up.  I can close it via the error dialog that comes up.  However, Sonar itself also locks up at that point.
 
As I am writing this, I decided to install the 64bit version of MixIR2 to see if that would make the difference.  However, in the preferences menu, under vst settings, the scan and reset buttons are grayed out.  I can not rescan the folders.
 
Side note: I was using the 32bit version of MixIR2 because of another 32bit vst called Chainer that is 32bit and only runs 32bit vsts.  FYI: Chainer is a vst host that can be used standalone, but is no longer supported and only ever was 32bit.  I have been using it as a guitar rig setup.
 
So I guess there are a couple things going on here that I can not figure out.  The grayed out scan/reset buttons.  And the what I think is a bitbridge problem.
 
Thanks for any help.
 

it's not an immediate solution but the best and most future proof one: try to eliminate all 32 bit plugins. I did that 2 years ago and it definitely improves stability and eliminates funky issues on your DAW.
 
virtually every plugin that is still being sold now should be available as 64 bit. for older ones there is usually a far better replacement, e.g. you could possibly replace your 32 bit chainer with either Sonar FX chains or if you need advanced routing, try DDMF metaplugin http://ddmf.eu/product/

Disabled scan buttons mean SONAR cannot find the vstscan.exe either because the program is missing or the registry entry is missing or wrong.
 
By default the scanner is located in C:\Program Files\Cakewalk\Shared Utilities
The registry entry for the scanner is HKEY_Current_User\Software\Cakewalk Music Software\SONAR\Cakewalk VST X64\VSTScanPath and the default value is C:\Program Files\Cakewalk\Shared Utilities\VstScan.exe
 
If the scanner is present and the registry key is missing, try holding the SHIFT key while launching SONAR. All SONAR to run the personalization process. If this does not work or the scanner is missing reinstall.

Rob[atSound-Rehab]
it's not an immediate solution but the best and most future proof one: try to eliminate all 32 bit plugins. I did that 2 years ago and it definitely improves stability and eliminates funky issues on your DAW.
 
virtually every plugin that is still being sold now should be available as 64 bit. for older ones there is usually a far better replacement, e.g. you could possibly replace your 32 bit chainer with either Sonar FX chains or if you need advanced routing, try DDMF metaplugin http://ddmf.eu/product/

 
Very true!!  If you step up to all 64 bit you'll never regret it.

I have to agree going completely 64 makes the most sense.  Unfortunately Chainer can only use other 32bit vsts.  I wish the guy that came out it still supported it.  Its super easy to use.  I pretty much use it as a standalone rig so I don't have to load up Sonar everytime I want to jam along with stuff or build tones.  But I end up using it in Sonar because because its so easy to recall my entire set up.
 
I suppose I could recreate the settings using Sonar FX chain.  The Metaplugin looks promising.
 
As far as the scan button goes...I do have the exe file in the shared utilities, however I don't have the registry folder "VSTScanPath".  Therefore no default value.  Can I manually edit the registry, if so how, or should I just reinstall Platinum?  Which I don't see an option for reinstall in the CCC.  Just uninstall.

FYI.  Holding the shift key didn't do anything.  The program wouldn't launch.
 
 

Right-click on SONAR, hold the SHIFT key and click Open on the context menu

Bingo...that did it.  Thanks scook.

So is there no fix for the "Teleport Server not responding" error?  It seems strange to me that it worked well before the update.
 
Is there a way to tell if bitbridge is doing its job?  It also seems strange that it is only happening with the MixIR2 vst.
 
And for what its worth, I just had the 32bit vsts working until just getting the "scan" button working again.  Maybe something related there?
 

Bitbridge was last changed in May 2015. Does the problem go away when SONAR is rolled back?