Article ID: 253341
Article Last Modified on 2/20/2007
APPLIES TO
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Professional Edition
This article was previously published under Q253341
NOTE: The information in this article applies to the French, German, Italian, Japanese, and Spanish version%3 of Windows 2000.
SYMPTOMS
When you attempt to connect to a Windows 2000-based computer to obtain access to a certificate enrollment, you may receive a warning message.
German, Spanish, Italian, or French Version of Windows 2000
You receive a warning message that states that the authenticity of the Xenroll.dll file cannot be verified, and therefore cannot be trusted.
Japanese Version of Windows 2000
You receive a warning message that states that the Xenroll.dll file content does not match the signature.
CAUSE
German, Spanish, Italian, or French Version of Windows 2000
The unsigned version of the Xenroll.dll file has been localized.
Japanese Version of Windows 2000
The signed version of the Xenroll.dll file has been localized.
RESOLUTION
French, Italian, Japanese, or Spanish Version of Windows 2000
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
The "Incorrect Signature for Xenroll.dll file" Windows 2000 Update is available on the Microsoft Windows Update Web site (http://windowsupdate.microsoft.com/). You can also download this recommended update (for installation later or on a different computer) from the following Microsoft Web sites:
French Language Version
Italian Language Version
Japanese Language Version
Japanese NEC Language Version
Spanish Language Version
To work around this problem, you can use this .dll file to obtain access to a certificate, but there is no way to determine if other changes may have been applied to this .dll file.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 1.
Keywords: kbbug kbenv kbfix kbqfe kbsecurity kbwin2000sp1fix KB253341