Are you saying the Automate software had an update that breaks CCM, but when the update is rolled back/uninstalled the CCM works normally?
If this is the case I'd say that the update to Automate is overwriting a supporting DLL that is needed by the CCM. My first course of action would be to contact whomever puts out Automate and ask them what the update package is doing -- what files and DLL libraries are they replacing.
But just to clarify, if you install the Automated update the CCM fails, but if you uninstall it then it works again?
If this is true, you really are going to have to reach out to Automate to find out just what they are changing. Some DLL is more than likely being overwritten (bad practice, btw).