You receive the "403.13 client certificate revoked" error message after you install the MS04-11 security update

Dichiarazione di non responsabilità per contenuto KB ritirato

Il contenuto di questo articolo è riferito a prodotti per cui Microsoft non offre più il supporto. Questo articolo viene pertanto offerto "così com'è" e non sarà più aggiornato.

We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 6.0 running on Microsoft Windows Server 2003. IIS 6.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:
BUG #: 98830 (Winse)Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry


After you apply the MS04-011 security update to a computer that is running Microsoft Windows 2000 Server and Microsoft Internet Information Services (IIS) 5.0, you may receive the following error message after you select a certificate:
403.13 Client Certificate Revoked
You may receive this error message if mutual authentication is enabled.


This problem occurs because of a certificate revocation list (CRL) retrieval timeout. MS04-011 introduces new Crypto API (CAPI) behavior with respect to network timeouts. This change was first made to address the problem of CAPI blocking for a long time during CRL retrievals when the target URL is inaccessible. The default time for Windows 2000 Server and MS04-011 is set to 15 seconds, and Windows 2000 Server and MS04-011 include a feature that retries the download on a background thread with a default timeout of 60 seconds. CRLs that reside on a Lightweight Directory Access Protocol (LDAP) URL may be particularly affected because of their lower throughput.


A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Windows 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Date Time Version Size File name
24-Mar-2004 02:17 5.0.2195.6876 388,368 Advapi32.dll
24-Mar-2004 02:17 5.0.2195.6824 42,256 Basesrv.dll
24-Mar-2004 02:17 5.0.2195.6866 69,904 Browser.dll
21-Sep-2003 00:45 5.0.2195.6824 236,304 Cmd.exe
14-Jul-2004 01:25 5.131.2195.6926 533,776 Crypt32.dll
14-Jul-2004 01:25 5.131.2195.6926 62,736 Cryptnet.dll
24-Mar-2004 02:17 5.0.2195.6868 76,048 Cryptsvc.dll
24-Mar-2004 02:17 5.0.2195.6824 134,928 Dnsapi.dll
24-Mar-2004 02:17 5.0.2195.6876 92,432 Dnsrslvr.dll
15-Nov-2001 23:27 5,149
24-Mar-2004 02:17 5.0.2195.6883 47,888 Eventlog.dll
19-Jun-2003 20:05 5.0.2195.6660 233,744 Gdi32.dll
24-Mar-2004 02:17 5.0.2195.6890 143,632 Kdcsvc.dll
11-Mar-2004 02:37 5.0.2195.6903 210,192 Kerberos.dll
24-Mar-2004 02:17 5.0.2195.6897 742,160 Kernel32.dll
21-Sep-2003 00:32 5.0.2195.6824 71,888 Ksecdd.sys
11-Mar-2004 02:37 5.0.2195.6902 520,976 Lsasrv.dll
25-Feb-2004 23:59 5.0.2195.6902 33,552 Lsass.exe
24-Mar-2004 02:17 5.0.2195.6824 54,544 Mpr.dll
14-Jul-2004 01:25 5.0.2195.6958 335,120 Msgina.dll
19-Jun-2003 20:05 5.0.2195.6680 117,520 Msv1_0.dll
24-Mar-2004 02:17 5.0.2195.6897 312,592 Netapi32.dll
19-Jun-2003 20:05 5.0.2195.6695 371,984 Netlogon.dll
24-Mar-2004 02:17 5.0.2195.6896 1,028,880 Ntdsa.dll
24-Mar-2004 02:17 5.0.2195.6824 115,984 Psbase.dll
24-Mar-2004 02:17 5.0.2195.6892 90,264 Rdpwd.sys
24-Mar-2004 02:17 5.0.2195.6897 388,368 Samsrv.dll
24-Mar-2004 02:17 5.0.2195.6893 111,376 Scecli.dll
24-Mar-2004 02:17 5.0.2195.6903 253,200 Scesrv.dll
04-Jun-2004 23:13 5.0.2195.6935 5,887,488 Sp3res.dll
05-Apr-2004 17:26 6,656 Spmsg.dll
05-Apr-2004 17:27 158,208 Spuninst.exe
24-Mar-2004 02:17 5.0.2195.6897 403,216 User32.dll
14-Jul-2004 01:25 5.0.2195.6958 393,488 Userenv.dll
24-Mar-2004 02:17 5.0.2195.6824 50,960 W32time.dll
21-Sep-2003 00:32 5.0.2195.6824 57,104 W32tm.exe
10-Jul-2004 05:36 5.0.2195.6958 1,631,760 Win32k.sys
12-Dec-2003 21:38 5.1.2600.1327 311,296 Winhttp.dll
11-Mar-2004 02:37 5.0.2195.6898 181,520 Winlogon.exe
25-Sep-2003 18:08 5.0.2195.6826 243,984 Winsrv.dll
24-Mar-2004 02:17 5.131.2195.6824 167,184 Wintrust.dll
24-Mar-2004 02:17 5.0.2195.6897 742,160 Kernel32.dll
10-Jul-2004 05:36 5.0.2195.6958 1,631,760 Win32k.sys
25-Sep-2003 18:08 5.0.2195.6826 243,984 Winsrv.dll
19-Sep-2003 22:09 4,092 Eula.txt
14-Jul-2004 01:56 19,262
05-Apr-2004 17:27 22,016 Spcustom.dll
05-Apr-2004 17:26 616,960 Update.exe
14-Jul-2004 01:11 44,156 Update.inf
14-Jul-2004 01:53 2,882 Update.ver
Note If services must retrieve a CRL, you must restart the computer. For example, LSASS must retrieve a CRL to verify smart card logon. If you do not restart the computer, these types of services do not recognize the registry change.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

After you apply this hotfix, you can configure the following URL retrieval time-out values:
  • ChainUrlRetrievalTimeoutMilliseconds
  • ChainRevAccumulativeUrlRetrievalTimeoutMilliseconds
You can configure these values under the following registry key value:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\OID\EncodingType 0\CertDllCreateCertificateChainEngine\Config
Name: ChainUrlRetrievalTimeoutMilliseconds
Value: This value is the time-out in milliseconds. If this value is set to 0 or does not exist, a default value of 15000 milliseconds is used.
ChainUrlRetrievalTimeoutMilliseconds is the default URL time-out for authority information access (AIA) retrievals and for non-accumulative CRL retrievals.
Name: ChainRevAccumulativeUrlRetrievalTimeoutMilliseconds :

Values: This value is the time-out in milliseconds. If this value is set to 0 or does not exist, a default value of 20000 milliseconds is used.
ChainRevAccumulativeUrlRetrievalTimeoutMilliseconds is the default revocation accumulative URL time-out. The first revocation URL retrieval uses half of this time-out.


For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

841641 IIS returns a "403.13 Client Certificate Revoked" error message after you install MS04-011 because of Wininet proxy settings

841642 Errors with client certificates occur after you install the MS04-011 security update on an IIS 5.0 computer


ID articolo: 841632 - Ultima revisione: 20 giu 2014 - Revisione: 1