Internet Explorer Administration Kit Builds Replace 128-Bit Encryption in Windows 2000

After you install a version of the Microsoft Internet Explorer 5 browser that was created by using the Microsoft Internet Explorer Administration Kit (IEAK) version 5 that includes the 128-bit encryption component (Ie5dom.exe), you may receive the following error message where Computer_name is the name of the local computer you are trying to log on to.

NOTE: This error message occurs the first time you restart the computer after you install Internet Explorer.

This issue can occur if you are using an earlier version of the Rsaenh.dll and Schannel.dll files.

To resolve this issue:

• Do not install Internet Explorer 5 on a computer running Windows 2000. Windows 2000 includes Internet Explorer 5.01.
• Use the IEAK to create a separate build of Internet Explorer that includes the latest 128-bit encryption update for Windows 2000 (Encpack.exe).
• Do not include the /n:v switch if you use the Ie5dom.exe component to create a separate build of Internet Explorer.

NOTE: This issue does not occur if you include the Ie501dom.exe component in your Internet Explorer 5.01 package.

Internet Explorer Administration Kit allows administrators and Internet service providers to create custom installations of Internet Explorer 5. To include 128-bit encryption in the browser, you need to include the custom 128-bit encryption component (Ie5dom.exe). The files that are distributed with these builds are Rsaenh.dll and Schannel.dll. The instructions included with the component instruct you how to perform a silent installation using the following switches: The /n:v switch suppresses the version check, and if you use this switch you can install an earlier version of the Schannel.dll and Rsaenh.dll files on the computer running Windows 2000.

To correctly install the 128-bit encryption on a computer running Windows 2000, install the appropriate 128-bit encryption component (Encpack.exe), which only updates the Rsaneh.dll file. For additional information about how to recover from this issue, click the article number below to view the article in the Microsoft Knowledge Base: