Windows Could Not Start. Could Not Read From the Selected Boot Disk

Windows could not start. Hardware configuration problem: Fix for Windows XP

/Knowledgebase /Windows could not start. Hardware configuration problem: Fix for Windows XP

Get the set to the Windows could non start boot error message affecting Windows XP .

Contents

• ane Nigh the "Windows could not start" error
  • ane.one Clarification and Symptoms
    • ane.1.i Symptom one: Windows could not first error screen on startup
  • 1.2 Causes of this Fault
    • 1.2.ane Cause 1: An entry in Kick.ini file points to a nonexisting drive or partition
• two Fixing "Windows could non start" on Windows
  • 2.1 Fix #1: Rebuild Boot.ini via Easy Recovery Essentials
  • 2.2 Set up #2: Rebuild kick.ini file
• 3 More Information
  • 3.i Linked Entries
  • 3.ii Support Links
  • 3.three Applicable Systems

About the "Windows could not start" error

The following information on this error has been compiled past NeoSmart Technologies, based on the data gathered and reported by our global network of engineers, developers, and technicians or partner organizations.

Description and Symptoms

The error messages, alerts, warnings, and symptoms below are tied to this error.

Symptom i: Windows could not start fault screen on startup

When a calculator is turned on, the BIOS picks an eligible, bootable hard drive and so calls lawmaking stored in the MBR at the start of that hard drive. That MBR lawmaking in plough loads the bootsector from the agile partition. On Windows XP, this bootsector code is tasked with loading NTLDR (the Windows XP bootloader) and its dependencies, which are used to load the operating system kernel and start up Windows. The NTLDR file then loads the Kicking.ini file that contains the list of operating systems. However, if an entry in the Kicking.ini file points to a nonexisting bulldoze or partition, then the system loading process is halted and the "Windows could not get-go" error screen is displayed.

For more information on how computers commencement up and how the Windows XP boot procedure works, please refer to the respective pages in our all-encompassing wiki and knowledgebase.

Windows could not showtime because of a computer deejay hardware configuration trouble.  Could non read from the selected kick deejay. Bank check boot path and disk hardware.  Please cheque the Windows documentation about hardware disk configuration and your hardware reference manuals for additional information.

Causes of this Fault

This mistake has been known to occur as a outcome of the post-obit cause:

Cause 1: An entry in Kick.ini file points to a nonexisting bulldoze or partition

On Windows XP, this fault may appear if the Boot.ini file becomes misconfigured or decadent because of user errors, power outages or virus attacks. If NTLDR tries to access an inaccessbile drive or partition, then the whole boot procedure is halted.

Fixing "Windows could not start" on Windows

Windows Setup CD/DVD Required!
Some of the solutions below require the use of the Microsoft Windows setup CD or DVD. If your PC did not come with a Windows installation disc or if you lot no longer accept your Windows setup media, you can use Easy Recovery Essentials for Windows instead. EasyRE will automatically find and fix many problems, and can likewise be used to solve this problem with the directions below.

Fix #i: Rebuild Boot.ini via Easy Recovery Essentials

Easy Recovery Essentials' one-click automatic system repair corrects issues acquired by misconfigured Boot.ini file past recreating ot from scratch on the active bootable partition for Windows XP. This is done automatically as part of the automated repair procedure, and requires no transmission action or user intervention.

Easy Recovery Essentials is guaranteed to set up the "Windows could not get-go" fault automatically using its built-in Automatic Repair option. EasyRE is currently available for Windows XP, Vista, 7 and 8 and can be downloaded and created on any PC.

1. Download Easy Recovery Essentials. Make certain to note your Windows version (XP, Vista, 7 or 8) before you lot download EasyRE. This guide tin assist you identify what version of Windows you take installed.
2. Burn down the prototype. Follow these instructions on how to burn the bootable ISO prototype very advisedly, as making a bootable CD tin can be catchy! Alternatively, these instructions explain how to create a bootable EasyRE recovery USB stick/drive.
3. Boot up your PC from the Like shooting fish in a barrel Recovery Essentials CD or USB you lot created.
4. Once EasyRE is running, choose the "Automated Repair" option and click Proceed.

   

   Choose "Automated Repair" in Easy Recovery Essentials

5. After EasyRE scans your computer's drives, identify and select the bulldoze letter for your Windows installation from the listing, and then click on the Automatic Repair button to begin.

   

   Choose the drive associated with the Windows installation you're trying to repair.

6. Easy Recovery Essentials will showtime analyzing the selected drive for problems. EasyRE volition test for and endeavor to automatically correct errors with the disk, partition, bootsector, filesystem, bootloader, and registry. No intervention is required, as EasyRE'south repair is fully automated:

   

   Easy Recovery Essentials searches for errors and makes corrections to the selected Windows installation.

7. Once the process is consummate, EasyRE volition report its findings. Click on the Restart button to reboot your PC and examination the changes.
8. The "Windows could not kickoff" error should now exist fixed as your PC begins to load:

   

   Windows, booting up successfully.

Y'all can download Easy Recovery Essentials from here.

Fix #2: Rebuild kicking.ini file

Follow these steps to rebuild the boot.ini file manually:

1. Insert the Windows XP install CD in your CD drive
2. Restart the PC and boot from the CD
3. Press any key to kick from the CD
4. Press R after the Windows Options menu is done loading to access Repair Console
5. Afterwards this step, log into Windows past pressing one using the Administrator password
6. Enter the following command when Command Prompt appears:

   bootcfg /rebuild

7. When the systems prompts virtually whether it should add an identified Windows installation to the kicking list, answer "Y"(Yes)
8. Enter "Windows XP" as Load Identifier and "/fastdetect" as OS Load Options.
9. Remove the install CD
10. Restart the PC

Hither is an instance of what the PC'south console output should look like once the kick.ini file is properly restored:

Fixing Boot.ini file

More Information

Linked Entries

• MBR boot process
• Windows XP boot process
• Bootsect
• Bootcfg

Support Links

• Easy Recovery Essentials for Windows – our repair and recovery disk.

  It's an easy-to-utilise and automated diagnostics disk. It'south available for Windows 8, Windows vii and Windows Vista. It'southward too available for Windows XP and Windows Server.

  Read more at Windows Recovery Disks.

• The NeoSmart Back up Forums, member-to-member technical back up and troubleshooting.
• Get a discounted price on replacement setup and installation discs: Windows XP.

Applicable Systems

This Windows-related knowledgebase commodity applies to the following operating systems:

• Windows XP (all editions)

Propose an edit

thompsonscame1964.blogspot.com

Source: https://neosmart.net/wiki/windows-could-not-start-hardware-problem/

Share this post