Yes, but it went away all by itself. The only difference was that the computer went through a couple of restarts.
 
Of course ideally, my computer is become ever-more intelligent, enhancing its AI, and fixing itself 
 
Just a hunch, but with the new drivers, I wonder if deleting the AUD.INI file and letting it rebuild might solve some problems?

Bristol_Jonesey
Yes John this update has caused more problems than anything I've seen since the dark days of X1a/b.
 
They all seem to be related to the Plugin Manager so I just hope the Bakers have enough information to work out what went wrong and issue a fix.

There are zero changes to the vst scanner or plugin manager in the 2016.11 update. Which version were you using prior to this update? Your problems are most likely coincidental and caused by something else.

Both pluginmanager.exe and vstscan.exe show version 22.11.0.111. Do you increment the version number with each release, regardless of whether there have been any changes? Nothing wrong with that if you do (easy for us to verify we're up-to-rev), but it makes it impossible for users to determine if changes have been made.
 
Should note that whenever a scan hangs or aborts, it is almost always a problem with a particular plugin, not with the plugin manager.
 
Back on topic: I have experienced crashes here as well, involving CA-2A and Rapture. Each time, the problem could not be reproduced until after a reboot. After rebooting, the problem reappears, but only once. The following exception (stack overrun) occurs if I drag CA-2A into any FX bin. After restarting SONAR, the problem is gone - until the next reboot.
 
Faulting application name: SONARPLT.EXE, version: 22.11.0.111, time stamp: 0x583d02e6
Faulting module name: CA-2ALevelingAmplifier_64.vst3, version: 2.0.1.97, time stamp: 0x5802558a
Exception code: 0xc0000409
Fault offset: 0x0000000000085e88
Faulting process id: 0x1e8c
Faulting application start time: 0x01d24d854f2cc61f
Faulting application path: C:\Program Files\Cakewalk\SONAR Platinum\SONARPLT.EXE
Faulting module path: c:\program files\common files\vst3\CA2ALevelingAmplifier\CA-2ALevelingAmplifier_64.vst3

Now I feel left out. 

Had issues for the first time with this one as well.  With windows "Cause" can be a grey area. My case was likely an order of operation issue with visual C++ runtime, windows updates and platinum/command center update.
 
To the user it appears cakewalk "caused" the issue.  The technician might recognize that it only "triggered" the issue but that does not matter.  Updating cakewalk hosed my platinum and I was unable to get it working in my studio at all until resolving the a regsvr dll issue. 
 
To the eye it appeared the new command center update caused my issue.  It was likely deeper.
 
Its cakewalks problem if they get caught in an update/runtime hot potato and they know it. I am sure they are aware of it.

I had a minor issues when updating.  
1.   I was guided thru the "setup" again, like when initially installing Sonar.  That has never happened.
2,  Even after this new "setup", I had to assign my MIDI in/outs again. (2nd time)
3.  My latest session had an instance of EZD2 that had no output.  I was able to just delete the synth and install again in that session and it was fine.   ALL other checked sessions with EZD2 seemed fine.
4.  Sonar DID crash when deleting EZD and my "fault reported" showed up about 20 times in my task manager.  I just closed ALL windows in my Windows task bar.
 
After the weirdness above, all seems fine.  My CA-2A seems fine in both FX bin and ProChannel....either as an old instance already in a project or a new insert.
 
I guess we'll see.    The Setup again kinda freaked me a little...as I didn't know if it was the tip of the iceberg or not.......but calmed down now  ;-)

After the update from 2016-10 to 2016.11 Sonar Platinum crashes every time when I open my projects.

When I disable CA-2A (shift+open file) it works.
Then I tried to insert CA-2A into my project again, Sonar crashes immediately.
 
When I create a new project and try to insert CA-2A in Prochannel or FX bin, it crashes.
I did a new installation(Command Center) of CA-2A , without success.
 
What is going wrong with that plugin and the new update?

Don't know if this is related or not, but I did experience a small issue with drag and drop from Windows explorer into the Sonar workspace, after upgrading from 2016.09 to 2016.10 a few days ago (just before 2016.11 was released). 
 
http://forum.cakewalk.com/Installed-the-latest-update-and-now-dragdrop-isnt-working-again-m3519421.aspx#3521517
 
Rolling back to 2016.09, followed by a reboot, cleared the issue.  Then when 2016.11 was released, I jumped on that.  Same issue, but it cleared after a reboot.  No further issues ... Never any issues with crashes or plugin scanning ... Can insert CA-2A anywhere without a hitch.

John
Now I feel left out. 

Maybe we should go to the back of the room
I'm not having these issues either..

When I installed the update the menu at the top of the screen was unreadable and greyed out. This lasted about 20 minutes and then cleared itself. It seems that most times that I have a glitch (very rare) it fixes its self and remains a mystery. I suspect Windows updates are involved because they randomly turn on all the audio stuff I've turned off.
 
With the current rate of change in the OS, Sonar and hardware drivers, I find it almost impossible to establish cause/effect relationships when things get weird on the computer.