Microsoft KB Archive/249321
Article ID: 249321
Article Last Modified on 10/11/2007
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Standard x64 Edition
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Datacenter x64 Edition
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
- Microsoft Windows Server 2003 R2 Standard Edition (32-bit x86)
- Microsoft Windows Server 2003 R2 Enterprise Edition (32-Bit x86)
- Microsoft Windows Server 2003 R2 Datacenter Edition (32-Bit x86)
- Microsoft Windows Server 2003 R2 Standard x64 Edition
- Microsoft Windows Server 2003 R2 Enterprise x64 Edition
- Microsoft Windows Server 2003 R2 Datacenter x64 Edition
- Microsoft Windows 2000 Professional Edition
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Datacenter Server
This article was previously published under Q249321
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
After you try to log on to your Windows 2000-based computer by using a valid user name and password, the Loading your personal settings dialog box is displayed, followed by the Saving your settings dialog box. However, the desktop does not appear, and the Welcome to Windows logon screen is displayed again.
Note If the paging file is located on the system or boot partition, you may also receive the following warning message before returning to the "Welcome to Windows" logon screen:
[Limited Virtual Memory]
Your system has no paging file, or the paging file is too small.
This problem can occur if your Windows 2000 boot partition drive letter does not match the drive letter assigned during the initial Windows 2000 Setup. Windows 2000 maintains a record of drive letters in a registry based database and re-assigns drive letters based on Globally Unique Identifiers (GUID) recorded for each volume. Should the volume GUID change or be duplicated (by hard drive cloning software), the original drive letter may not be re-assigned to the boot volume.
This may also occur if you break a system/boot mirror, and then attempt to boot to the old shadow drive if the original primary drive is missing or inaccessible. This is because the volume GUID for the shadow drive is different than that of the original primary drive and does not get the same drive letter assigned.
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.
Note If the computer is networked but not part of a domain, you may need to map a connection to the machines IPC$ share using that computer's local administrator credentials before being able to attach using Regedit.exe or Regedt32.exe as described below to make changes.
To permit a logon and/or change the boot volume drive letter back to its originally assigned letter, use any of the following methods:
net use \\remote_machine_name\IPC$ /user:administrator *
Use one of the following procedures to facilitate repairs:
- Remove any cloned hard disks added to your computer since the time the logon failures occurred, restart your computer, and then try to log on.
- If the computer is networked, run Regedit.exe on another computer to open and modify the registry of the computer that is experiencing the logon failure. Use the information in the following Microsoft Knowledge Base article to change the drive letter back to the original letter assigned to the boot partition:
- If the computer is networked, run Regedt32.exe or Regedit.exe on another computer to open and modify the registry of the computer that is experiencing the logon failure. Change the following entry to remove the full path to the Userinit.exe entry as follows:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Winlogon\Userinit:Reg_SZ:C:\WINNT\system32\userinit.exe
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Winlogon\Userinit:Reg_SZ:userinit.exe
After you change the preceding registry entry and are able to logon, perform the steps in the following Microsoft Knowledge Base article to re-assign the proper drive letter to your boot partition and reboot:
- Create a "fake" Winnt\System32 folder structure on the drive that is suspected as being assigned the original boot partition drive letter, and then expand and copy the Userinit.exe file from the Windows 2000 CD-ROM into the Winnt\System32 folder on that drive.
You can use the Recovery Console to perform this procedure provided the local security policy\security option "Recovery Console: Allow floppy copy and access to all drives and all folders" is enabled. This will permit the following Recovery Console command to work so you can gain unlimited access to all drives and paths: SET allowallpaths = TRUE This can be implemented as a policy on a domain controller to be applied to the local computer by using the information contained in the following Microsoft Knowledge Base article:
235364 Description of the SET Command in Recovery Console
After you perform the preceding procedure and you are able to log on, perform the steps in the following Microsoft Knowledge Base article to re-assign the proper drive letter to your boot partition and reboot:
- With only the system/boot drive in the system, or powered on, boot to a DOS or Windows 9X Start-up diskette that contains fdisk.exe and run the following command:
This re-writes the Master Boot Record and erase the disk signature associated with volume GUID. Windows 2000 should assign default drive letters and allow you logon. Click the article number below for more information about FDISK:
69013 FDISK /MBR rewrites the Master Boot Record
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:
234048 How Windows 2000 assigns, reserves, and stores drive letters
Additional query words: reoccurring secedit blank desktop login repeats "Control Alt Delete" "CTRL DEL" loop MountedDevices
Keywords: kbenv kbprb KB249321