When I rest and scan my plugins, I get 2 notices about a Main Call Failure Point for Rapture x64 and 2 notices for Rapture LE.  It wants me to disable the plugin or enable it (risky).  Why is this happening?  How do uninstall the LE version?  Do I need to reinstall Rapture x64?
 
Thanks for your help!

Good question. I'm being told that some problems including CTD's are bridge issues and the break to 64b as required is problematic for all those 32b VSTs we might have actually figured out and like to use. Some might discard them, others - not so much.
 
I've already installed my DP,Z3/2,Rap, etc twice in the last two months and it's getting a bit tedious. Silly me, I installed 32b versions which had all worked OK expecting to bring up a 32b Sonar before even looking into the limited options of 64b vst's which will merely do the same things as 32b versions anyway.
 
Do you have any other VST x64's to confirm ? If not, I'll 'put it on the list' .
 
I'm real gun-shy about CW VST updates as they generally have lost all the additional banks/presets, etc. It's a big deal for me and takes about a week to sort out usually. Not fun.

I occasionally see this error with different plug-ins and ignore them when I know the plug-in works properly. I would not reinstall if Rapture works.

My Rap_32_VST seems to work in SPro and FLS. I'm just uncertain about how a another install, of say Rap, as a 64b will impact the other dirs where I have my stuff and expansion packs. It shouldn't mess with them, but that was not my experience with the install of SPro. I'm not rushing into that mess again. I've just recently posted about issues with the Sound Center as 32b not loading even from CW provided templates. 

Did it go through the proper registration process, after Dim Pro was installed?
 
I always ran Sonar installs with explicit Run As Administrator option set, and upon first launch subsequent to an install, also did so with explicit Run As Administrator, THEN would complete the Dim Pro and Rapture registration processes.  Sometimes, I did the completion of Dim Pro and Rapture registrations completely outside of Sonar - launching Dim Pro and Rapture each as stand-alone versions, again setting Run As Administrator for both - and registration that way also always worked.
 
If the above is not the issue for you, then I would think an uninstall of Dim Pro and another install of it should work (If it were me I would also set it to launch with Run As Administrator to complete registration).
 
I hope any of the above helps get things fixed up for you.
 
Bob Bone