This article was previously published under Q255674
This article has been archived. It is offered "as is" and will no longer be updated.
If the access rights to the HKEY_LOCAL_MACHINE\Software\Microsoft registry key are reduced so that the logged-on user no longer has the access rights to create subkeys in the registry, Drwtsn32 does not work correctly and does not update the Drwtsn32.log file or generate a User.dmp file.
When Drwtsn32.exe runs, it requests KEY_CREATE_SUB_KEY privileges when it opens its registry key to determine what configuration to use. If the logged-on user does not have these privileges, Drwtsn32 does not run correctly and no log file or user dump file is generated.
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 theMicrosoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
Windows NT 4.0
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.
To resolve this problem, 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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Date Time Size File name Platform -------------------------------------------------- 05/26/2000 05:46p 66,832 Drwtsn32.exe x86 05/26/2000 05:45p 90,384 Drwtsn32.exe Alpha
Microsoft has confirmed that this is a problem in Windows 2000. This problem was first corrected in Windows 2000 Service Pack 1.
Windows NT 4.0
Microsoft has confirmed that this is a problem in Windows NT 4.0.