This delay may occur when starting a LoadRunner component as the .NET Framework attempts to perform a verification check that requires Internet access. If the system where LoadRunner is installed is isolated from the Internet then the component startup is delayed while the client attempts to connect to the Internet, but times-out. The check that is performed is part of code access security (CAS) where signed code assemblies need to be verified, or provide evidence of their publisher, using a Certificate Authority.
To speed up the launch time, disable the generation of publisher evidence. This may improve the startup time of LoadRunner product components. To modify this setting within the .NET Framework configuration of the system where LoadRunner is installed, open the file: ''C:WindowsMicrosoft.NETFrameworkv2.0.50727CONFIGmachine.config'' (using Notepad or a similar text editor) and change the line:
![Text from the config file][1]
Save this file and start/launch LoadRunner again.
[1]: /storage/temp/41-text.png