That is a possibility. I know that the CA2A install process renames the PC2ALevelingAmplifier_64.dll to PC2ALevelingAmplifier_64.old to get it out of the way. There could be some registry magic too, I am not sure. I believe the scanner looks for PC modules after your VST scan paths so it could be overlaying the CA2A entry with the PC2A (if you are seeing the PC2A in your PC list). You could try renaming the PC2A dll or just run the CA2A installer again.