Datacrash.net - Enabling user environment debug logging (Source http://support.microsoft.com/kb/221833)

Enabling user environment debug logging (Source http://support.microsoft.com/kb/221833)

Written by Richard Thompson, Tuesday, 10 October 2006

Often you are contacted by the helpdesk reporting that a specific user or a group of users is having a problem logging in. More often than not they will give you very little information regarding the problem and you will need to do some digging.

One of the things to do is enabling user environment debugging. Microsoft Article 221833 refers to a document on how to do this in retail builds of Microsoft Windows.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Use Registry Editor to add the following registry value (or modify it, if the value already exists):

Key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
Value: UserEnvDebugLevel
Value Type: REG_DWORD
Value Data: 10002 (Hexadecimal)

UserEnvDebugLevel can have the following values:

NONE 0x00000000
NORMAL 0x00000001
VERBOSE 0x00000002
LOGFILE 0x00010000
DEBUGGER 0x00020000

The default value is NORMAL|LOGFILE (0x00010001).

Note To disable logging, select NONE (where the value is 0X00000000).

You can also combine the values. For example, you can combine VERBOSE 0x00000002 and LOGFILE 0x00010000 to get 0x00010002. So if UserEnvDebugLevel is set with a value of 0x00010002, this turns on both LOGFILE and VERBOSE. Combining these values is the same as using an OR statement:

0x00010000 OR 0x00000002 = 0x00010002

Note If you set UserEnvDebugLevel = 0x00030002, the most verbose details are logged in the Userenv.log file.

The log file is written to the %Systemroot%\Debug\UserMode\Userenv.log file. If the Userenv.log exists and is greater than 300 KB, the existing file will be renamed to Userenv.bak, and a new log file created.

Datacrash cannot be held responsible for any problems arising from modifying the registry.

Comments

Add New

RSS