This article has been archived. It is offered "as is" and will no longer be updated.
When you log on to a Windows NT 4.0 computer, you may receive the followingerror in the User Environment dialog box:
The operating system was unable to load the locally stored profile. A new local profile will be created (1009).
The following message may be displayed as well:
Your profile was not successfully loaded, but you have been logged on with the default system profile. Please correct the problem and log off (18).
Your profile settings (desktop icons, application settings, and so on) are reset to the default. If you look in the %SystemRoot%\Profiles folder,you should see your profile directory has been renamed to%SystemRoot%\Profiles\Username.bak, and a new default profile has beenstored in %SystemRoot%\Profiles\Username. This is done to allow a user tolog on successfully if the profile has been corrupted or does not load forsome other reason.
If the registry size limit has been exceeded, a system pop-up messageindicating this will be presented to the user during the first logonattempt when this occurs. The following message will be displayed:
System Process - Low on Registry Quota: Your system is running low on registry quota. Start the System option in the Control Panel and choose the Virtual Memory button to increase the registry quota.
During subsequent logon attempts, profile load errors will occur and thefollowing application events will be logged:
Event ID 1000 userenv RegLoadKey failed with error 1009 for C:\WINNT\Profiles\username\ntuser.dat Event ID 1000 userenv The operating system was unable to load the locally stored profile. A new local profile will be created. (1009)
NOTE: If a user commonly locks the workstation instead of logging off, theoriginal Registry Size Limit error may have been forgotten or lost from theevent log by the time a subsequent logon attempt occurs and the profilefails to load.
Windows 2000 Terminal Server SP4 clients are not able to connect to the Terminal Server because of the following error messages:
Event Type: Error Event Source: Userenv Event ID: 1000 Date: 1/6/2004 Time: 10:33:41 AM User: NT AUTHORITY\SYSTEM Computer: SRV-TS01 Description: RegLoadKey failed. Return value Insufficient system resources exist to complete the requested service. for C:\Documents and Settings\jj35678\ntuser.dat. Event Type: Error Event Source: Userenv Event ID: 1000 Date: 1/6/2004 Time: 10:33:47 AM User: NT AUTHORITY\SYSTEM Computer: SRV-TS01 Description: Windows cannot load your profile. Please increase the registry size and restart the computer.
Event Type: Error Event Source: Userenv Event ID: 1000 Date: 1/6/2004 Time: 10:33:48 AM User: NT AUTHORITY\SYSTEM Computer: SRV-TS01 Description: Windows cannot log you on because the profile cannot be loaded. Contact your network administrator. DETAIL - Insufficient system resources exist to complete the requested service.
Although the user profile registry keys may fail to load for a number ofreasons, one status code is always returned indicating that the profile iscorrupted. The Registry Size Limit (RSL) may have been exceeded. The RSL isa user-defined quota that places a maximum upper limit on how large theregistry can grow. When this limit is approached, a message stating this inthe Application Popup dialog box will be presented to the user. Because theloading of a user profile (stored in Ntuser.dat) consumes Registry Quota,this may contribute to the exhaustion of this resource.
A User Profile does not load if the RSL has been exceeded. This is bydesign. To work around this problem, the RSL can be increased to avoid therestriction. To do this, follow these steps:
In Control Panel, double-click System.
On the Performance tab, click Change in the Virtual Memory section.
In the Virtual Memory dialog box, in the Registry Size section, the current registry size and the maximum registry size are displayed. Modify the current RSL in this section.
Microsoft recommends increasing the RSL only enough to accommodate thecurrent Registry and a small amount of growth. For additional information,please see the following article in theMicrosoft Knowledge Base:
In Windows NT 4.0, Terminal Server Edition, the RSL is based on paged pool. The maximum size of paged pool is 192 MB. RSL can consume a maximum of 80 percent of paged pool, for a maximum of 153.6 MB. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
124594 Understanding and Configuring Registry Size Limit (RSL)
Windows NT 4.0
If the profile has been renamed to Username.bak as a result of theRSL being exceeded, it is possible to restore the original profilesettings.
Log on to the computer as Administrator.
Rename or delete the %SystemRoot%\Profiles\Username profile folder.
Rename the %SystemRoot%\Profiles\Username.bak profile folder to Username.
Log off as Administrator and log on as Username.
Windows 2000 includes a UserEnv enhancement so that the user profile is not deleted if or when the profile is not corrupt. A pop-up message is provided indicating insufficient resources. The user is then logged off if the user does not have local administrative privileges or the user is logged on when administrative privileges are identified. The administrator can then increase the registry size limit and log on again. The user profile used prior to the problem is still being saved on the local computer unless it has just been copied.
Note A restart is required after RSL has been increased either by using Control Panel or by editing the registry, because this change does not happen dynamically and you may still experience the following event:
Event Type: Error Event Source: Userenv Event Category: None Event ID: 1000 Date: Date Time: Time User: NT AUTHORITY\SYSTEM Computer: ComputerName Description: RegLoadKey failed. Return value: Insufficient system resources exist to complete the requested service for C:\Documents and Settings\ntuser.dat.
Windows 2000 Terminal Server SP4 clients
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
Restart your computer. For additional information about the Recovery Console, click the following article number to view the article in the Microsoft Knowledge Base:
229716 Description of the Windows 2000 Recovery Console
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
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 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Error code 1009 is always returned as the NtStatus code for the Windows APIMyRegLoadkey. This code maps to the configuration registry database ascorrupted: ERROR_BADDB or STATUS_REGISTRY_CORRUPT. This is misleading ifthe loading of the registry hive failed because of other causes. If the RSLis exceeded, the correct NtStatus code is 1450, insufficient systemresources exist to complete the requested: ERROR_NO_SYSTEM_RESOURCES orSTATUS_INSUFFICIENT_RESOURCES.
For additional information, please see the following article in theMicrosoft Knowledge Base:
Microsoft Windows NT Server 4.0, Terminal Server Edition, Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition