So I know better than to say "nothing has changed" - and of course there have been Windoze updates, but beyond that I have not installed anything new on my DAW since the last SPLAT update. I have a pile of plugins I need to update, but since things are working I've left them in a pile somewhere.
 
On Sunday I fired up Sonar, and impOSCar2, minimonsta, and Oddity2 were all flagged during the scan with the dreaded warning that I should disable them. The scan happens nearly every time I start thanks to the Waves wrapper, still haven't figured out a way around it. But I digress.

So I set it to scan existing and failed and let it go - went and made a nice pot of coffee - and when I came back it was the same thing, these three synths, and only these three synths are being flagged.

I've emailed GForce, and since I'm not yet using Bandlab I don't really have anyone to ask at Cakewalk, so I figured I'd ask here to see if anyone else has run into this.
 
Thanks!

Some plug-in(s) scanning before the GForce plug-ins are likley causing the error. I occasionally get the "Disable/Enable (Risky)" dialogs. For plug-ins from known manufacturers such as GForce, I always enable the plug-ins. So far never had a problem enabling them.

wst3
So I set it to scan existing and failed and let it go - went and made a nice pot of coffee - and when I came back it was the same thing, these three synths, and only these three synths are being flagged.

Can't recall a time ever enabling both scan options. I would probably run a reset instead. Either way, I suspect the problem is not with the GForce plug-ins.

GForce plugs all fine here in both SPlat and CbB.