After the. Net2.0 WinFom program is digitally signed, the program starts slowly.

When I met a customer before the festival, the program opened slowly. I checked that many http requests were made when the program opened, and they concentrated on accessing Microsoft's digital certificate website. The program is. Net2.0. To avoid being killed by 360 by mistake with a digital signature, check the system logs and find a large number of errors. Later, the check found that in the following two cases

When I met a customer before the festival, the program opened slowly. I checked that many http requests were made when the program opened, and they concentrated on accessing Microsoft's digital certificate website. The program is. Net2.0. To avoid being killed by 360 by mistake with a digital signature, check the system logs and find a large number of errors. Later, the check found that in the following two cases

When I met a customer before the festival, the program opened slowly. I checked that many http requests were made when the program opened, and they concentrated on accessing Microsoft's digital certificate website. The program is. Net2.0. To avoid being killed by 360 by mistake with a digital signature, check the system logs and find a large number of errors. Later, the check found that the program will be slow in the following two cases:

1. Access to a digital website is very difficult or even inaccessible

2. Incorrect local system time

I don't know what Microsoft has done ,. after adding a digital signature to a program of Net 2.0, you must check whether the current certificate is in the revocation list, and regularly update the revocation certificate list, if it is not updated for two days, it will be updated every time it is started. After the check is passed, the program can be started. Once there is a problem in this process or when there are too many loaded programs and dll, the program will be slow to start.

Microsoft official description: http://support.microsoft.com/kb/941990/zh-cn

Symptom

When you try to start a digitally signed Microsoft. NET Framework 2.0 Windows application or Windows service, the application starts very slowly. When a digitally signed Windows service is started, it may time out. you receive the following error message from the Service Control Manager:

Error 1053: the service did not respond to requests for timely start or control.

Back to Top | provide feedback

Cause

This problem occurs because the application must download the Certificate Revocation List (CRL) for identity authentication ). However, the lack of network connectivity will lead to a timeout caused by a failed download. For example, the firewall may block download. When Windows is started for the first time, the network connection is not initialized yet.