XP installation startup failure

Fault 1. Installation Prompts unknown hardware error

"Symptom" After you install Windows XP SP3, restart your computer, prompting the C0000135 unknown hard error message, and Windows Installer cannot continue.

"Fault analysis", according to English prompts, is an unknown hardware error caused the system to not install properly. Normally, we generally consider that a hardware device is not compatible with Windows XP SP3, but in fact, if some hardware drivers or software in the original Windows system conflict with the SP3, it may cause setup to not work properly or blue screen.

Troubleshooting format system disk C disk, first install Windows XP SP2, note that the hardware driver is not installed at this time, SP2 install SP3 program to upgrade Windows XP from SP2 to SP3 after installation completes.

Master Dong prompts: Before upgrading SP3, make a system backup to the current system with ghost.

Fault 2. Boot.ini File Error

"Symptom" Boot to Windows XP, pop-up dialog box prompts "Boot.ini file illegal", unable to enter the system.

Failure analysis causes the Boot.ini file to be illegal because of Boot.ini file loss or incorrect file format. You can resolve the problem simply by restoring a Boot.ini file or by rewriting the correct Boot.ini file.

"Troubleshooting" first, in other computers that have Windows XP systems installed, click the "start → run" command and enter "C:/boot.ini" and enter the Boot.ini file, save the Boot.ini file as a file with the same name and copy to Boot.ini file damaged computer, overwriting the damaged Boot.ini file. If you can't find another computer that has Windows XP installed, you can open Notepad and enter the following:

[boot loader]

Timeout=30

Default=multi (0) disk (0) rdisk (0) partition (1)/windows

[Operating Systems]

multi (0) disk (0) rdisk (0) partition (1)/windows= "Microsoft WINDOWS xp Professional"/noexecute=optin/fastdetect

When you are finished, save the file as "boot.ini" and save it to the C disk, overwrite the original Boot.ini file, and restart the computer.

If you are unable to access the system, you can use Windows PE startup to modify the Boot.ini file in the C disk in Windows PE. Or use the boot disk to boot into the DOS or Recovery Console, enter the "Copy Con c:/boot.ini" carriage return, according to the above Boot.ini file content and format, line-by-row input, enter a line of carriage return once, all finished, press the shortcut key "Ctrl+z", this time will appear ^ Z's prompt, then returns, prompts "1 file (s) copied", the Boot.ini file establishes successfully, restarts the system namely automatically normal entry.

Master Dong Tip: If the system is prompted to not find the Hal.dll file at startup and cannot access the desktop and Safe mode, this failure is mainly due to Boot.ini file errors. In the way described above, using normal boot.ini to overwrite problematic Boot.ini files or rewrite Boot.ini files can also solve the problem.

Fault 3. System login User Password Forget

"Symptom" Some people in the use of computers, often yesterday changed Windows XP system login password, today forgot the password, locked himself in the "door outside."

"Troubleshooting" Restarts the computer, pressing the F8 key to bring up the advanced Startup Options menu, select "Safe Mode with command line", click "Administrator" to enter command line mode. Enter command: "NET user system logon username 123456/add" to force the password of the system logged-on user to "123456". or enter the command "NET user aaaa 123456/add" Create a new user aaaa (password is 123456), then enter "net localgroup Administrators Abcdef/add" command to promote user AAAA to a system administrator. Restart your computer and you can log on to the system with the changed password "123456".

Note: The above method can not retrieve the password, can only modify the password. If your hard disk uses EFS encryption, it can disrupt EFS encryption and cause data loss.

Fault 4. Windows XP reboots when it enters the system

"Symptom" because the Kernel32.dll file is lost or corrupted, causing Windows XP to reboot in half, there is no way to enter the system.

"Fault analysis" for this type of situation, as long as the use of normal files replaced or back to solve the problem.

Troubleshooting puts the Windows XP CD-ROM on the CD, starts the Recovery Console, enters the CD system32 and returns at the command prompt, enters Ren kernel32.dll kernel32.old and returns, and then enters map and returns; The final input expand X:i386kernel32.dl_ and enter ("x:" is the optical drive letter), the Kernel32.dl_ file from the CD-ROM to the hard drive to replace the damaged Kernel32.dll files. You can start Windows XP normally by entering "exit" and restarting your computer.

Fault 5. The registry is corrupted causing the system to not start properly

"Symptom" for various reasons, the registry of Windows XP is corrupted and Windows XP does not start properly. Failure Analysis Registry Damage is a very common situation. Whenever you start the Recovery Console, delete the original registry file with the Delete command, and then copy the registry files from the Windows XP installation CD-ROM/windows/repair directory to the System32/config folder. After you complete this procedure, a new registry will be created and Windows XP will start using this new registry. In the ointment, the new registry was created and saved during the initial Windows XP installation, so any changes and settings that were made after the installation of Windows XP are lost.

Troubleshooting enters the Recovery Console, puts the Windows XP installation CD in the optical drive (x:), types The following lines, and presses Enter after each line:

Delete C:/windows/system32/config/system

Delete C:/windows/system32/config/software

Delete C:/windows/system32/config/sam

Delete C:/windows/system32/config/security

Delete C:/windows/system32/config/default

Copy X:/windows/repair/system C:/windows/system32/config/system

Copy X:/windows/repair/software C:/windows/system32/config/software

Copy X:/windows/repair/sam C:/windows/system32/config/sam

Copy x:/windows/repair/security c:/windows/system32/config/security

Copy X:/windows/repair/default C:/windows/system32/config/default

Fault 6. "Last Known Good Configuration" went wrong

"Symptom and Analysis" in Windows XP occurred some faults such as blue screen, at this time restart the computer, press F8 to pull up the advanced Startup Options menu, choose "Last correct configuration" can generally solve a lot of problems. However, if you cannot use the last Known Good configuration, you receive an error message "Windows NT could not start because the following file is missing or corrupt:/windows/system 32/config/system/hardware profile/last Known Good menu ", that's trouble, this problem is usually caused by the registry damage.

"Troubleshooting" Enters the Recovery Console, uses the CD command to enter the C:/windows/repair directory, runs the "copy *.* c:/windows/system32/config" command, and invokes the first installation of WINDOWS XP when the registry file overwrites the corrupted registry file. This registry was created and saved during the initial installation of Windows XP, so any changes and settings that are made after Setup is complete will be lost.

Fault 7. Windows XP cannot be started in Windows 2000/XP dual system

"Symptom" installed Windows 2000 through D on the original Windows XP on C disk, Windows 2000 installation is complete, Windows XP cannot be found after reboot, Windows XP is inaccessible, and only Windows 2000 can be entered.

Failure analysis failed to start Windows XP because after Windows 2000 was installed, its Windows 2000 boot program loaded Windows XP in its original mode of operation, and Windows XP was modified at boot time, windows 2000 no changes were found at boot time and natural Windows XP failed to start.

Troubleshooting can be resolved by copying Windows XP modified files to your hard disk. What to do: Start your computer with Windows 2000, and then copy the Ntldr, Bootfont.bin, and Ntdetect.com files under the I386 folder in the Windows XP installation CD to the root of system disk C, and restart Windows XP.

Fault 8. Windows XP does not start when Vista is installed

"Symptom" a computer that originally installed Windows XP, and then installed Windows Vista to make up a dual system, results in the Windows XP system not starting.

Failure analysis Windows XP cannot be started because Windows Vista overwrites the Windows XP startup files under the root of the system boot partition after installation, and Windows XP does not start.

Troubleshooting uses the Windows XP installation CD to start the computer, when the ScreenTip "Welcome to Setup", press the "R" key to start the Recovery Console, enter the "Bootcfg/add" command and return, and start automatically scanning all the operating systems installed on the computer and displaying it. Enter the "bootcfg/rebuild" command after the scan completes and press the Y key when the prompt is complete. Finally, you can find the multiple system menu by entering the missing Startup menu item After "Enter the load qualifier" and entering "fastdetect" after "Enter OS load Options".

Fault 9. Prompt for "IEXPLORE error" When update patch is updated

"Symptom" Windows XP prompts "IEXPLORE error" When using Windows XP update patches.

Failure analysis may be the result of a failure caused by a wuv3is.dll error in the Windows Update update-related file.

"Troubleshooting" click "Start → run", enter "regsvr32/u wuv3is.dll" Uninstall Wuv3is.dll, and then enter C:/Program files/windows Update directory to delete wuv3is.dll files. Finally, you can rerun the Windows Update operation without worrying that Windows XP will regenerate the Wuv3is.dll file and the error message will not pop up again.