Something odd with Platinum Plug-in Manager 2017.04 exclude plugin function

So I upgraded my Melda plugins today and for reasons only they could understand they forced the install of MTurboReverbMB along with the MTurboReverb (even though I don't get/have a license for it and it will only run as a demo).  So I figure, no problem I'll just exclude it in the Plug-in Manager.  Now it's important to note, I install all 4 versions of every plugin -- VST2 32 and 64bit and VST3 32 and 64bit.  So I should have 4 plugins, but SONAR only reports finding 3.  Which is odd, but OK, I can work with that. 
 
So I exclude the VST2 and VST3 versions.  But inside SONAR I still see the 64bit VST2 plugin, even though it is listed in the Plug-in Manager exclude list.  The VST3 version is correctly excluded. 
 
So I go digging.  The way the Plug-in Manager exclude feature works is it has a list of clsids that have been excluded.  So I expect to find two entries in HKEY_CURRENT_USER\Software\Cakewalk Music Software\ExcludedPlugIns for MTurboReverbMB and I do.  But here's the weird part, the VST3 version is for the correct clsid.  But the VST2 entry is wrong, instead of using the clsidPlug value it is using the clsidPlugMD5 value.  (Which SONAR uses to tell if a plugin has changed I guess)  Like the Plugin manager chose the wrong clsid when it added it to the exclude list.
 
I changed the entry to the correct clsidPlug value and now MTurboReverbMB is completely gone.
 
This seems like it may be bug in the plugin manager's exclude functionality.  Or maybe I just need to eat lunch and quit upgrading software.
 
I also seem to have a bunch of excluded plugins in the reigstry that may or may not even exist anymore.  I guess it doesn't do any housekeeping either.  Because if it had, it would have removed the bad entry it made since no plugin with that clsid exists.