IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone 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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
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:
311512 Problems Reading Schema Information from Third-Party LDAP Servers If You Are Using ADSI
: If you use Registry Editor incorrectly, you may cause serious problems that may
require you to reinstall your operating system. Microsoft cannot guarantee that you can solve
problems that result from using Registry Editor incorrectly. Use Registry Editor at your own
risk.
After you install Windows 2000 SP3 or the hotfix described in Microsoft Knowledge Base Article Q311512, you must manually add the following registry key.
To turn off EFS, follow these steps:
- Start Registry Editor (Regedt32.exe).
- Locate and then click the EfsConfiguration value under the following key in the registry:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\EFS
- On the Edit menu, click new, click DWORD Value, and then type EfsConfiguration.
- Double-click EfsConfiguration value and>, change the value to 1, and then click OK.
A zero (0) turns on EFS, and a one (1) turns off EFS. - Quit Registry Editor, and then restart the computer.
NOTE: If you try to encrypt a file after you install the hotfix to turn off EFS, you receive the following error message:
An error occurred applying attributes to the file: <X:\filename>. The
required encryption driver is not loaded for this system.
If you apply this hotfix to a stand-alone computer, and the computer is added later to a domain, EFS remains turned off even if the domain has an Encrypted Data Recovery Agent specified.
If you turn off EFS by using this hotfix and the associated change in the registry, you cannot change the EFS setting by using Group Policy on the domain.
Users cannot copy or decrypt any files that were encrypted before you turned off EFS by using the registry key. If you try to access the files, you may receive the following error message:
Access is denied. The source file may be in use