Normally, the extension load order in ePO is deterministic. But, certain workflows exist that can trigger extensions to load in a non-deterministic order. For example, suppose that you try to log on to the ePO console when extensions are still loading. This action triggers ePO to load its Bouncy Castle implementation before the DLP Endpoint extension loads. The reason is because ePO uses the Bouncy Castle library to encrypt and decrypt the password provided by the user. This example is just one of many for how this problem might occur.