Did you scan or reset?
Do you have the VST2 version of VKFX installed? I did not see that in the list above.

Its actually the ProChannel versions that are shown in the browser.

I started by doing a reset and rescan after the initial problems all to no effect. But I'm repeating myself now as I stated that in the very first post.

Yes, I know. But that does not answer my question. Where are the VST2 versions installed? They are actually the same dll's and I believe the reason the PC versions are showing up in the VST2 list is because the VST2 versions are missing.

mudgel
I started by doing a reset and rescan after the initial problems all to no effect. But I'm repeating myself now as I stated that in the very first post.

That is what I understood from the first post, I was asking about the process in msg 9 but I doubt it matters WRT your VKFX issue.

Getting crazier. I can instantiate the VKFX modules that are for the Prochannel into an fx bin.
 
I have checked and do not have the VST 2 versions installed at this time

Ah OK I'll put them back and see.

I have had that - suddenly all VST effects are VST Instruments etc.
But even had that in Sonar 8.
Guessing mixing Sonar 8, X3 scans share something about plugins.
And doing a cumulative scan in new Sonar did that too.
 
Complete reset of plugin list and rescan fixed it.

 
Also had duplicates looking in registry one scan was followed by another, so they were duplicates actually. But at that time, I manually removed all those entries - and made rescan.
 
Nothing about adding removing scan paths and stuff though, but never changed it either as I recall.

The VKFX PC module issue is nothing like anything you would have experienced in SONAR 8.
 
There is only one VST scanner for 32bit SONAR and one for 64bit SONAR, it is a shared utility. Up until the new SONAR, there was one VST inventory for 32bit SONAR and one for 64bit SONAR. So when running 64bit SONAR 8 and X3 you were actually using the same scanner building the same registry entries.
 
The new SONAR still uses a shared scanner but builds a separate VST inventory.

What I've done with plugin groups (by vendor) that I've had problems with is to drag them from their location, let Sonar just update the plugin menus then put the group of plugins back and this time Sonar picks them up properly, something a reset and rescan hasn't been able to accomplish.
 
So I've fixed all those issues but the question remains, why did I get corrupt registry entries? Why has there been such a mess after the Cambridge update?
 
BTW, I rolled back to the Braintree update which didn't help at all so I'm fixing all this on the Cambridge update.