This is normal, expected behavior. Occasionally another service may start ahead of the CBC sensor and not be blocked/denied/terminated until the sensor is fully up and running.
One obvious solution is to delete the undesired executable file from the machine since it's meant to be blocked from running.
Another possible workaround is to delay the Windows service for that executable to be invoked until the CBC sensor is fully up.
For example, with MS Windows OS's services can be delayed at boot time as so:
Delay start programs