sodcalculator

10 Tech How-To

Disk Read Error Occurred in Windows 10: Fixes

Guide 10-47735 · Updated · Step by step

A “Disk Read Error Occurred” in Windows 10 usually means the system cannot read data from your hard drive or SSD during startup, and the fix typically involves checking cable connections, running startup repair, or checking the disk for errors. This error appears as a black screen with white text, often before the Windows logo, and can be caused by faulty hardware, corrupted boot files, or incorrect BIOS settings. Below is a practical guide to diagnosing and resolving the issue, with steps you can try in order from least to most invasive.

What Causes a Disk Read Error in Windows 10?

The error message itself is generic—it tells you the computer tried to read from the boot drive and failed, but not why. Common causes include:

  • Loose or damaged cables – SATA data or power cables can work loose over time, especially in desktops.
  • Failing hard drive or SSD – Bad sectors, worn-out NAND flash, or mechanical failure can make sectors unreadable.
  • Corrupted boot configuration data (BCD) – Windows needs this file to locate the operating system; if it’s damaged, the boot process fails.
  • Incorrect boot order in BIOS/UEFI – The system might be trying to boot from a USB drive, another disk, or a network device.
  • Outdated or faulty storage drivers – Especially after a major Windows update.
  • Recent hardware changes – Adding a new drive or changing SATA ports can confuse the boot manager.

Understanding the cause helps you choose the right fix. For example, if you just installed a second hard drive, the boot order is more likely the culprit than a failing SSD.

Before You Start: Check the Obvious

These quick checks take two minutes and can save you hours:

  1. Remove any USB drives, SD cards, or external disks – The system may be trying to boot from them.
  2. Enter BIOS/UEFI – Restart and press the key shown on screen (usually Del, F2, F12, or Esc). Look for the Boot menu and set your Windows drive (the one with the OS) as the first boot option.
  3. If you have a desktop, open the case and reseat the SATA and power cables – Unplug and firmly reconnect both ends. If you have a spare SATA cable, try swapping it.
  4. For laptops, reseat the RAM – Sometimes a loose RAM module can cause a similar error, though it usually shows a different message.

If the error persists after these checks, move on to software-based repairs.

How to Run Startup Repair from Windows Recovery Environment

Windows 10 includes a built-in startup repair tool that can fix boot problems automatically. To access it:

  1. Insert a Windows 10 installation USB or DVD (you can create one on another computer using Microsoft’s Media Creation Tool).
  2. Boot from the media – you may need to change the boot order in BIOS to do this.
  3. On the first screen, select your language and click Next.
  4. Click Repair your computer in the bottom-left corner.
  5. Choose Troubleshoot → Advanced options → Startup Repair.
  6. Select your operating system and let the tool run. It will scan and attempt to fix boot issues.

Startup Repair works best when the problem is with boot files (like BCD or the Master Boot Record). If it says it couldn’t repair, don’t give up—there are more targeted commands you can run manually.

Use Command Prompt to Rebuild Boot Files and Check Disk

If Startup Repair fails, you can use the Command Prompt from the same Advanced options menu. Select Command Prompt and run the following commands in order, pressing Enter after each:

  1. bootrec /fixmbr – Repairs the Master Boot Record (for legacy BIOS) or the GPT header (for UEFI).
  2. bootrec /fixboot – Writes a new boot sector.
  3. bootrec /scanos – Scans for Windows installations.
  4. bootrec /rebuildbcd – Rebuilds the Boot Configuration Data. It will ask if you want to add the installation to the boot list – type Y and press Enter.

After these, also run a disk check to look for bad sectors:

  • chkdsk C: /f /r – This checks the file system and scans for bad sectors. Note: the drive letter might not be C: in the recovery environment. To find it, type diskpart, then list volume, and note the letter assigned to your Windows partition (often D: or E:). Type exit to leave diskpart, then run chkdsk with the correct letter.

If chkdsk finds and fixes errors, restart normally. If it reports many bad sectors, the drive is likely failing and should be replaced soon.

Check Hard Drive Health with SMART and Manufacturer Tools

If the error keeps coming back, the drive itself may be dying. Most drives support SMART (Self-Monitoring, Analysis and Reporting Technology), which tracks indicators like reallocated sectors and spin-up time. You can view SMART data in the BIOS (look for “SMART status” or “Hard Drive Self Test”) or by using a free tool like CrystalDiskInfo from within Windows (if you can boot).

If SMART shows a failing status, or if chkdsk found physical bad sectors, back up your data immediately and replace the drive. For SSDs, check the manufacturer’s utility (e.g., Samsung Magician, Crucial Storage Executive) for a health report—they often show a “percentage used” or “remaining life” figure.

Note: A SMART warning is not a guarantee of imminent failure, but it’s a strong signal. Do not ignore it.

What to Do If the Drive Is Fine but the Error Persists

If the disk passes health checks and boot files are rebuilt, the issue may be elsewhere:

  • Update BIOS/UEFI – Check your motherboard manufacturer’s website for a newer version. Sometimes a BIOS update fixes compatibility issues with SSDs or new hardware.
  • Reset BIOS to default settings – In BIOS, look for “Load Optimized Defaults” or “Reset to Default” and save. This can fix incorrect SATA mode settings (e.g., IDE vs AHCI).
  • Disable Fast Boot – In Windows, Fast Boot can sometimes cause issues with external drives or after updates. Turn it off in Control Panel → Power Options → Choose what the power buttons do → Change settings that are currently unavailable → uncheck “Turn on fast startup.”
  • Check for a second drive – If you have more than one drive, try disconnecting all except the Windows drive. If the error disappears, the problem is with the other drive or the cable.

If none of these work, the problem might be with the motherboard’s SATA controller or the drive itself in a way that SMART doesn’t catch. Testing the drive in another computer is the best way to isolate the hardware.

Frequently Asked Questions

Will I lose my files if I run Startup Repair?

No, Startup Repair only attempts to fix boot files; it should not delete personal files. However, if the drive has serious corruption, there’s always a small risk. It’s wise to back up important data before running any repair, but if you can’t boot, you may need to remove the drive and connect it to another computer to copy files.

What does “Disk Read Error Occurred” mean on a laptop?

On a laptop, the same error usually points to a failing internal drive, a loose connection (less common since drives are often soldered or in a fixed bay), or a corrupted boot sector. The same fixes apply: check BIOS boot order, run Startup Repair, and check drive health. If the laptop has a removable battery, try a hard reset (remove battery and AC power, hold power button for 15 seconds) before anything else.

Can a disk read error be caused by a virus?

Yes, though it’s rare. Some malware can alter the Master Boot Record or boot configuration, causing a similar error. If you suspect malware, boot from a clean USB with an antivirus rescue disk and scan the drive. But first, try the standard boot repairs—they’re faster and more likely to work.

How do I fix a disk read error without a Windows installation disc?

You can create a recovery drive on another Windows 10 PC: go to Control Panel → Recovery → Create a recovery drive. This creates a bootable USB that includes Startup Repair and Command Prompt. Alternatively, you can download the Windows 10 Media Creation Tool from Microsoft’s official site and create an installation USB—it works the same way.

Is a disk read error always a sign of hardware failure?

No. Software issues like corrupted boot files, incorrect BIOS settings, or a bad Windows update can cause it. However, if the error persists after trying all software fixes, hardware failure becomes more likely. If you hear clicking or grinding sounds from a mechanical drive, stop using it immediately and seek data recovery help.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →