BUG: MS Enhanced Provider Won't Load Under Windows NT 4.0 SP3

 Last reviewed: October 28, 1997
Article ID: Q171889
The information in this article applies to:
  • Microsoft Win32 Software Development Kit (SDK)

SYMPTOMS

The MS Enhanced Provider (Rsaenh.dll) will not load under Windows NT 4.0 Service Pack 3.

CAUSE

The MS Enhanced Provider requires that you load and use a signature which is stored in the registry. There is a bug in Domestic Windows NT 4.0 Service Pack 3 in that the signature for the MS Enhanced Provider is not put in the registry during setup. In addition, another required registry entry is incorrect in Service Pack 3.

RESOLUTION

The file Rsaenh.reg is used in conjunction with Regedit.exe to fix a problem with the MS Enhanced Provider (Rsaenh.dll) that does not load under Windows NT 4.0 Service Pack 3. It can be obtained via the following self- extracting executable files, Rsax86.exe (x86 platform) or Rsaalpha.exe (Alpha platform).

The following files are available for download from the Microsoft Software Library: 

 ~ Rsax86.exe (size: 23243 bytes) 
 ~ Rsaalpha.exe (size: 23244 bytes)
For more information about downloading files from the Microsoft Software Library, please see the following article in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q119591
   TITLE     : How to Obtain Microsoft Support Files from Online Services
The MS Enhanced Provider (Rsaenh.dll) is a Cryptographic Service Provider for the Crypto API that implements strong Cryptography (DES, 3DES, 128-bit RC2 and RC4, and large RSA key exchange keys). Its export is restricted to North America and, in this case, it is shipped in the Domestic (North America only) version of Windows NT 4.0 Service Pack 3.

To fix this problem, do the following:

  1. Make sure that you have downloaded the appropriate file for your platform (Rsax86.exe for the X86 platform or Rsaalpha.exe for the Alpha platform).

  2. Run the .EXE to extract the Rsaenh.reg file.

  3. Make sure that you are logged on as an administrator.

  4. Go to a DOS window. At the command line type: 

          regedit rsaenh.reg

    The command argument to regedit.exe must be the path of the rsaenh.reg file.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: enhanced csp 128-bit service provider crypto
Keywords : AXSDKWinInet BseRegistry kbfile
Platform : NT WINDOWS
Issue type : kbbug
Solution Type : kbfile

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: October 28, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.