VST plugin error for SoundCenter opening template

I opened a New Project using the 'Electronic' template. I immediately get a VST plug-in Error box. It does appear to be trying to load the 32b (and I don't know or care if there is a 64b version) of SoundCenter, frankly.
 
I then get a Missing Plug-Ins error box for the SC again. I am using SPro from C3 and this preset isn't even a (Professional) option. 
 
So, do I debug to see if the VST is installed OK (by C3) or mark this as a bad template or try to start another new project?
 
Please, put it on the list. It is a supplied preset/option so shouldn't have errors before I start 'fix'ng er up' as we say.

Hi, its a Project Template from File/New.
I start CW. I have the quick launch disabled so I go right to the menu. I select New. I get the template dialog options. I choose 'Electronic'. SC error, VST not loading. 
So, today I reproduce it. Same error. Being more curious I attempt to load it from the Synth browser. It's listed, so I click it, and get an another installation error msg. 
I did the BrainTree update. SCenter may or may not have been working prior to this. I don't use it, but this template does and it has problems that I didn't know I had. 
Even worse, I'm at a complete loss as to how to 'fix' this. I don't want to spend an hour figuring out which installation file from C3 might need to be re-run.
 
Are you able to load this 'Electronic' template?
I'm with a C3 SonarPro install, it's not indicated as Platinum (like the Acid).
 
 

I did skip the BTree updates to SCenter and SI, since they had been working for my 32b install and I don't use them. I started those DL/installs now via C3. I don't see how they might have been invalidated.
 
So, now I'm DL'ing a ton of samples that I'll never use onto my SSD again. I know SI was working because I occasionally use it in FLS. Maybe, these are 'required' install options now? I'm a bit surprised that the scanner didn't choke on them. Maybe I'll find time to re-scan VSTs, probably not.
 

The update installation finished and started on its own and is doing it's thing (just for SC). C3 reports 'Complete'.
C3 eventually resets as I continue. Noting a 'Red' LED by the NYC Showcase, I better DL it now. I'll never use it, but if a yellow LED might be problem, let's just do the red one and hope its short. Another 20 minutes and its almost time for dinner. I did not schedule any debug time for a synth I'm not interested in and had no choice about installing. I was just trying out a Project template.
 
The IR's are about done, and now I've got another install screen that I probably shouldn't just dismiss.
 
I'm getting real skeptical about this subscription auto update model biz is pursuing. In order to even get this msg to y'all I had these updates as well. A NV graphics driver, a chrome, a MSI mobo util package. Rarely do I not have 3 or more SW updates each day and that's not even the updates that I decide to manually seek out. My laptop had a very different set of updates this morning as well. I'm looking for something in a DAW that I can setup in 2  months or so. It may have issues, but I'll figure them out and I will be able to actually work tracks and not the DAW for 3 or 4 years. Updates are great, but they shouldn't be experiments. Better doc's are needed.
 
I can't recall anything that I've done that might have 'broken' the CS install. 
 
So, fire up Sonar, and msg. I can't do anything about it updating my personal app files (I'm guessing these are my '../user/appdata/roaming/..' ones, but who knows? I've waited this long so 'OK'. Sonar then starts, I go File/New, select the template and the VST plug-in error shows up, just like before.
 
So, I re-scan VST folders, which does indeed find changes. And SC and the Project template subsequently loads correctly. An SI Bass loads OK, though I didn't DL that one yet so it is still yellow. I've gotten a lot more careful about VST installations, so I do not have the 'Scan on Start' enabled as I keep them pretty stable and still need to re-start often. Particularly with issues with do/don't bridge, 32/64, etc aside from just removing clutter. 
 
I've heard some concerns about my being vague, so I'm trying to improve on that via a more  documentary approach. Apologies to those that find it tedious.
 
Short story: The C3 won't update, flag or prompt for a new VST scan if needed. Without doc's for the update indicating this, it could be overlooked. 
 
Long Story: This is not the scheduled activity for this evening.