As you already know Component Download Fail is related to failing definition download for one of ours SE Engines to be more specific this error is related to BP (Behavioral Protection). There can be several issues that can cause this if this is something that you see in your portal and will not clear out on its own. With out diagnostic bundle its hard to tell, but there is one that has been around which is related to old and unsupported way of connector update.
On older systems that has been in service for a while and with updates pushed through SCCM or any other 3rd party automation along with using command line switch overridepolicy 0 you will for sure face this issue.
This is due to overridepolicy 0 flag which back in the days allowed business with hundreds different policies to update with single installer. With this flag you bypassing certain files from overriding which was OK back in the days with single certification dependency. Since then and based on continuous demand to harden our product that changed and now we have secondary cert dependencies and here is where things are getting broken. With the overridepolicy 0 flag you are not allowing certain certificates to update making those obsolete and no longer valid.
If you do using this flag and facing this issue you can verify this by opening local.xml and extracting the certificate that you will find inside. Just simply copy the entire certificate including
-----BEGIN CERTIFICATE-----
-----END CERTIFICATE-----
paste in text editor and save it with .crt extension. Then open with crypto shell which is built in to the windows.
If you see your cert looks like those on this picture highlighted in red which are missing .amp extension in the Issued to: filed and are valid for 10yrs then you are using the old outdated and no longer valid certificate.
Example: The one in red are updates deployed with overridepolicy 0 the rest are just updates through policy update or fresh install. Please note that initial fresh deployments are OK and you can still use your preferred automation tool however updates should always be done via secure endpoint console.
If this is your issue, your only option now is completely uninstall secure endpoint and deploy fresh new install on the affected endpoint(s)
If yours looks similar to those highlighted in green, yellow or blue those are the newer certificates formats that are used now. If you see the newer format then the issue must be somewhere else and in that case please open a TAC case so we can look in to the issue.
Hope this help...
Cheers Roman
