MPC 1.9.6 VSTi indicates must unlock stand-alone first

This punk software is steady wanting to give me problems... it's already registered/unlocked, so why would it complain the stand-alone must be unlocked before it can be run as a plugin? I've tried to load it in Sonar and FL and it does the same thing in both.

My Cousin figured it out... apparently the MPC only likes to be installed to the Steinberg VSTPlugins folder, and I allowed mine to be installed to the Cakewalk VSTPlugins folder being I use Sonar. Why the MPC is so particular, I'm not sure, but reinstalling it and sending it to Steinberg folders fixed its plugin operation.