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:
Your system has no paging file, or the paging file is too small.
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.
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:
- 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:
Change from:HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Winlogon\Userinit:Reg_SZ:C:\WINNT\system32\userinit.exeChange to:HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Winlogon\Userinit:Reg_SZ:userinit.exeAfter 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 = TRUEThis 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 ConsoleAfter 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:FDISK /MBRThis 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
รหัสบทความ: 249321 - การตรวจสอบครั้งสุดท้าย: 16 ก.ค. 2008 - ฉบับแก้ไข: 1