- You use the Secure Sockets Layer/Transport Layer Security (SSL/TLS) client certificate authentication on a computer that is running Windows 8 or Windows Server 2012.
- An operation that is seemingly unrelated to the SSL/TLS client certificate authentication is performed. However, the operation causes the Trusted Root store to exceed the 16 kilobytes (KB) limit. For example, one of the following operations is performed:
- In a remote session, an unauthenticated user probes the SSL endpoint server by using a client certificate that chains to novel trusted roots. Then, the Cryptographic Application Programming Interface (CAPI) installs the novel trusted roots automatically.
- A user logs on to the computer and browses an SSL/TLS website that is secured by a novel trusted root.
- CAPI updates an existing installed root automatically. This behavior causes the size of the root to increase or the enumeration order to change.
- A change occurs in the certificate enumeration order code (for example, you install a hotfix that changes the certificate store code or changes table sorting).
- A user switches using certificates.
- An administrator installs new certificates to the Trusted Root store.
Note This issue occurs regardless of the value of the SendTrustedIssuerList registry entry. In other words, you cannot resolve this issue by setting a value for the SendTrustedIssuerList registry entry. The SendTrustedIssuerList registry entry is located under the following registry subkey:
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesTo apply this hotfix, you must be running Windows 8 or Windows Server 2012.
Registry informationTo use the hotfix in this package, you do not have to make any changes to the registry.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
Article ID: 2880390 - Last Review: Oct 21, 2013 - Revision: 1