The first time a code signed assembly is loaded by the .NET Common Language Runtime (CLR) the Certificate Revocation List (CRL) is downloaded from the certificate provider’s server and cached on the system. This is causing problems in various scenarios as Windows will check the certificate revocation status at install and run time if the machine thinks it has internet access but if it then fails to get access to http://crl.microsoft.com/ it causes big performance problems