Tip & How-To about Computers & Internet

Windows XP failed to start because of a recent hardware or software change?

You have corrupt or deleted windows files or possibly a hardware error. The first thing is to try a repair using a Windows XP CD that came with your system.
XP REPAIR INSTALL
1. Boot the computer using the XP CD. You may need to change the boot order in the system BIOS. Check your system documentation for steps to access the BIOS and change the boot order.
2. When you see the "Welcome To Setup" screen, you will see the options below. This portion of the Setup program prepares Microsoft Windows XP to run on your computer: To setup Windows XP now, press ENTER.

  • To repair a Windows XP installation using Recovery Console, press R.
  • To quit Setup without installing Windows XP, press F3.
3. Press Enter to start the Windows Setup: do not choose "To repair a Windows XP installation using the Recovery Console, press R", (you do not want to load Recovery Console). I repeat, do not choose "To repair a Windows XP installation using the Recovery Console, press R".
4. Accept the License Agreement and Windows will search for existing Windows installations.
5. Select the XP installation you want to repair from the list and press R to start the repair.
6. Setup will copy the necessary files to the hard drive and reboot. Do not press any key to boot from CD when the message appears. Setup will continue as if it were doing a clean install, but your applications and settings will remain intact.
7. You will need to apply Windows updates after this procedure.
Not a trivial task but it will work. I do this for fun & feedback so 4 thumbs would be nice.
Jim

Posted by on

Computers & Internet Logo

Related Topics:

Related Questions:

1 Answer

Ntldr is missing press ctlr+alt+ and delete to restar and i did and don't workz


First I have to assume that you are running Windows XP. This solution should work for other versions of Windows.
The "NTLDR is missing" error displays very shortly after the computer is first started, immediately after the Power On Self Test (POST) is complete. Windows XP has only initially begun to load when the NTLDR error message appears.
Causes of NTLDR Errors
There are a number of possible causes for NTLDR errors, including the most common "NTLDR is missing" error message.
The most common reason for this error is when your PC is trying to boot from a hard drive or flash drive that is not properly configured to be booted from; in other words, it's trying to boot from a non-bootable source. This also would apply to media on an optical drive or floppy drive that you're trying to boot from.
Other possible causes include corrupt and misconfigured files, hard drive and operating system upgrade issues, corrupt hard drive sectors, an outdated BIOS, and damaged or loose IDE cables.
How to Fix NTLDR Errors
1.Restart the PC. The NTLDR error could be a fluke.

2.Check your floppy and optical (CD/DVD/BD) drives for media and disconnect any external drives. Often times, the "NTLDR is Missing" error will appear if your PC is trying to boot to a non-bootable floppy disk, CD/DVD/BD, or external hard drive or flash drive.
Note: If you find that this is the cause of your problem and it's happening a lot, you might want to consider changing the boot order in BIOS so the hard drive with Windows installed is listed first.

3.Check the hard drive and other drive settings in BIOS and ensure they are correct. The BIOS configuration tells the computer how to use a drive so incorrect settings can cause problems, including NTLDR errors.
Note: There is usually an Auto setting for hard drive and optical drive configurations in BIOS which is usually a safe bet if you're not sure what to do.

4. Restore the NTLDR and ntdetect.com files from the Windows XP CD. Restoring these two important system files from the original Windows XP CD may do the trick.

5. Repair or replace the boot.ini file. This will prevent the NTLDR error if the cause of the problem is a boot.ini file that is not configured properly for your Windows XP installation.

6. Write a new partition boot sector to the Windows XP system partition. If the partition boot sector has become corrupt or isn't properly configured, you may receive the "NTLDR is Missing" error.

7. Repair the Windows XP master boot record. NTLDR error messages may also appear if the master boot record is corrupt.

8. Reseat all internal data and power cables. NTLDR error messages could be caused by loose or malfunctioning IDE cables.
Try replacing the IDE cable cable if you suspect it might be faulty.

9. Update your motherboard's BIOS. Occasionally, an outdated BIOS version can cause the "NTLDR is Missing" error.

10. Perform a repair installation of Windows XP. This type of installation should replace any missing or corrupt files. Continue troubleshooting if this does not resolve the issue.

11. Perform a clean installation of Windows XP. This type of installation will completely remove Windows XP from your PC and install it again from scratch. While this will almost certainly resolve any NTLDR errors, it is a time consuming process due to the fact that all of your data must be backed up and then later restored.
If you can't gain access to your files to back them up, understand that you will lose them all if you continue with a clean installation of Windows XP.

12. Replace the hard drive and then perform a new installation of Windows XP. If all else has failed, including the clean installation from the last step, you're most likely facing a hardware issue with your hard drive.
NTLDR Errors Apply To
This issue applies to the Windows XP operating system, including Windows XP Professional and Windows XP Home Edition.
Windows 8, Windows 7, and Windows Vista utilize BOOTMGR, not NTLDR.
Still Having NTLDR Issues?
See Get More Help for information about contacting me on social networks or via email, posting on tech support forums, and more. Be sure to let me know what steps, if any, you've already taken to fix the "NTLDR is missing" issue.

Jan 29, 2014 | Microsoft Windows XP Professional

2 Answers

what causes" ntldr"?


NTLDR fail is either corrupt files or a bad disk drive. Check my tip for how to repair software. If it is a hardware error, don't use the computer and get it to a local shop that can recover your data and replace your disk drive.
My tip: http://www.fixya.com/support/r6101870-windows_xp_failed_start_because_recent
If this answers your question, I'd appreciate 4 thumbs. I do this for fun and do not get paid.
Jim

Oct 02, 2010 | Dell Lattitude D600 Notebook

1 Answer

when my laptop is turned on, it shows, We apologize for the inconvenience, but windows did not start successfully. A recent hardware or software change might have caused this. If your computer stopped responding, restarted unexpectedly, or was automatically shut down to protect your files and folders, choose last known good configuration to revert to the most recent settings that worked. If a previous startup attempt was interrupted due to a power failure or because the power or reset button was pressed, or if you aren't sure what caused the problem, choose Start windows Normally. Safe Mode Safe mode with Networking Safe Mode with Command Prompt Last known good configuration (your most recent settings that worked) Start Windows Normally Use the up and down arrow keys to move the highlight to your choice. Once I select, Start Windows Normally or Last Known Good Configuration, it(laptop) restarts again and shows the very same message. In other words, Window XP does not load


You have corrupt or deleted windows files or possibly a hardware error. The first thing is to try a repair using a Windows XP CD that came with your system.
XP REPAIR INSTALL 1. Boot the computer using the XP CD. You may need to change the boot order in the system BIOS. Check your system documentation for steps to access the BIOS and change the boot order. 2. When you see the "Welcome To Setup" screen, you will see the options below. This portion of the Setup program prepares Microsoft Windows XP to run on your computer: To setup Windows XP now, press ENTER.
  • To repair a Windows XP installation using Recovery Console, press R.
  • To quit Setup without installing Windows XP, press F3.
3. Press Enter to start the Windows Setup: do not choose "To repair a Windows XP installation using the Recovery Console, press R", (you do not want to load Recovery Console). I repeat, do not choose "To repair a Windows XP installation using the Recovery Console, press R". 4. Accept the License Agreement and Windows will search for existing Windows installations. 5. Select the XP installation you want to repair from the list and press R to start the repair. 6. Setup will copy the necessary files to the hard drive and reboot. Do not press any key to boot from CD when the message appears. Setup will continue as if it were doing a clean install, but your applications and settings will remain intact. 7. You will need to apply Windows updates after this procedure.

Sep 21, 2010 | Dell Inspiron 1545 Notebook

1 Answer

I get the STOP: C0000218 {Registry File Failure} The registry cannot load the hive (file):System RootSystem32ConfigSECURITY or its log or alternate. It is corrupt, absent, or not writable..On my windows xp and I do not have a back up disk because it is in my d driver can anyone help?


This is one of the main reasons I prefer to do a clean installation from CD rather than simply doing a system restore. There's less chance for something to go wrong with a clean installation. Unfortunately, many computer manufacturers no longer provide a complete CD, but you still may be able to completely wipe your drive rather than using the restore option. The Stop: c0000218 error is typically associated with one of several things, depending on how far through the recovery process you made it before encountering the error.

The first possibility is simply corruption in the Windows Registry. A second option is a component of your system hardware is not compatible with Windows XP or your hard drive has some kind of issue. Since you are re-installing Windows XP using System Restore, it seems unlikely your system hardware is incompatible, although I won't rule out the possibility entirely. The third possibility, a damaged hard drive, is possible even if Windows appeared to run smoothly prior to your reinstallation. Before throwing in the towel, we'll take a closer look at each possibility
Assuming the Windows Registry is simply corrupt, the first thing to attempt is a recovery via the Automatic System Recovery for your particular installation. Since you are attempting to do a system restore, it's possible you already tried this and had it fail. If this is not the case, follow the detailed directions presented in Microsoft Knowledge Base article 307545.

If you attempted your system restore using the OEM provided restore partition or CD and received this error, make sure you don't have any hardware components connected which weren't part of the initial build of your computer. System restore disks look for specific hardware components. If the original components are missing it occasionally introduces errors in the restore process.
A third possibility is the hard drive is damaged in some way. Many disks have bad sectors and you won't know about them until you attempt to write over the sectors during a specific operation. If you can boot from your install CD, you will be presented with the option to Repair or Recover the Windows XP installation. Pressing R launches the Microsoft Recovery Console which then asks for the Administrator password. After entering the password, run chkdsk to check the drive for errors by typing chkdsk /r at the command line. If chkdsk finds errors, you may need to use chkdsk /f to repair the errors before proceeding.
Since you are attempting to revert your Windows installation back to baseline, the best option remains doing a completely fresh install because it will avoid any potential corruptions already existing in your current installation by installing a fresh copy of Windows instead of reusing existing core components that may now be corrupt.

Have this as a guide when you perform system restore in recovery console..http://www.myfixes.com/articles/system..

Hope this will help..

Feb 04, 2010 | Microsoft Windows Server Standard 2003 for...

2 Answers

windows system 32 hal.dll error after restoring e-machine


There's actually a number of reasons why these annoying little DLL errors happen, but the most common, is caused when new programs are installed over all old ones and the old ones are not completely uninstalled 100%, causing registry pile ups and of course, getting a .DLL error messages.

Another reason, is damage that's been done by malware/spyware/adware programs, attaching themselves to your PC and wrecking havoc, deleting crucial DLL files from your PC.

The hal.dll file is created during install from 5 other dlls. HAL is the Hardware Abstraction Layer and it's the interface between the system drivers and the actual hardware.

Copying hal.dll will not resolve the problem.

A lot of times the file will be reported missing due to corruption of the boot sector or of the file system

Causes of the "missing or corrupt hal.dll" error include, naturally, a damaged hal.dll file or a hal.dll file that has been deleted or moved from its intended location.

Additional causes may include a damaged or missing boot.ini file or possibly a physically damaged HDD.

Suggested remodies-

1. Restart the PC. The hal.dll error could be a fluke.

2. Check for proper boot order in BIOS. You might see the hal.dll error if the boot order in BIOS is first looking at a hard drive other than your main hard drive.
Note: If you've recently changed your boot order or recently flashed your BIOS, this may be what's causing your problem.

3. Run Windows XP System Restore from a command prompt. If this doesn't work or you're receiving the hal.dll error message before you're able to complete this process, move on to the next step.

4. Repair or replace the boot.ini file. This will work if the cause of the problem is actually Windows XP's boot.ini file and not the hal.dll file, which is often times the case.

5. Write a new partition boot sector to the Windows XP system partition. If the partition boot sector has become corrupt or isn't properly configured, you may receive the hal.dll error.

6. Restore the hal.dll file from the Windows XP CD. If the hal.dll file is truly the cause of the problem, restoring it from the original Windows XP CD may do the trick.

7. Perform a repair installation of Windows XP. This type of installation should replace any missing or corrupt files. Continue troubleshooting if this does not resolve the issue.

8. Perform a clean installation of Windows XP. This type of installation will completely remove Windows XP from your PC and install it again from scratch.

Note: While this will almost certainly resolve any hal.dll errors, it is a time consuming process due to the fact that all of your data must be backed up and then later restored.

Important: If you can't gain access to your files to back them up, understand that you will lose them all if you continue with a clean installation of Windows XP.

9. Replace the hard drive. Finally, if all else has failed, including the clean installation from the last step, you're most likely facing a hardware issue with your hard drive.

10. Perform a new installation of Windows XP after installing the new hard drive.

I have not tried it - but HERE is a free program purporting to fix the error.


Thanks for using FixYa - a FixYa rating is appreciated for taking the time to answer your FREE question.

Apr 10, 2009 | E-Machines eMachines Desktop PC

Not finding what you are looking for?

1,212 people viewed this tip

Ask a Question

Usually answered in minutes!

Top Computers & Internet Experts

Doctor PC
Doctor PC

Level 3 Expert

7733 Answers

kakima

Level 3 Expert

102366 Answers

David Payne
David Payne

Level 3 Expert

14161 Answers

Are you a Computer and Internet Expert? Answer questions, earn points and help others

Answer questions

Loading...