Article ID: 241042 - View products that this article applies to.
This article was previously published under Q241042
The following symptoms may occur:
This behavior occurs in Windows NT 4.0 because the registry key listed below grants the SetValue permission to the Everyone group by default, so that any user (even guests) can edit the information in the ProfileList registry key and its subkeys:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\ProfileListEditing these keys can be performed locally or remotely, and setting permissions in the Access Control List (ACL) on the Winreg key (HKEY_LOCAL_MACHINE\System) does not limit remote access because the path to the CurrentVersion key is an allowed path and can be edited regardless of the permissions assigned to the Winreg key.
Windows NT Server or Workstation 4.0To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMSWhen you apply Windows NT 4.0 Service Pack 6 (SP6), the default permission on the Everyone group is set to read access only. Also, the process created by Winlogon.exe creates the user's Security Identifier (SID) subkey in the System account, instead of under the CurrentVersion key, and then writes the necessary values to the ProfileList key.
Windows NT Server 4.0, Terminal Server EditionTo resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/152734/ )How to obtain the latest Windows NT 4.0 service pack
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition.
This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.
For more information about making your Windows NT 4.0 installation secure, see the "Securing Microsoft Windows NT Installation" white paper at the following Microsoft Web site: