Fix a Disk Read Error in Windows 10

A disk read error in Windows 10 can come from a loose connection, damaged boot files, incorrect boot settings, or a failing drive; the message alone does not identify which. Start with low-risk checks and protect important files first: if the disk is making unusual noises or intermittently disappears, stop repeated repair attempts and seek data-recovery help before changing it.

What the disk read error means

Windows may show “A disk read error occurred” during startup, often before the sign-in screen. The computer has failed to read information it needs to continue booting. This can involve the drive itself, its connection, the firmware’s choice of boot device, or Windows’ boot configuration. It does not automatically mean that every file is lost, nor does it prove that a particular repair command will work.

First note exactly when the message appears and whether anything changed beforehand: a power loss, dropped computer, new drive, firmware setting change, Windows update, or connection of a USB device can provide useful clues. If you can reach Windows, copy irreplaceable files to another device or a trusted backup before troubleshooting. If Windows will not start, use another computer and appropriate recovery or backup tools only if you understand the risks; avoid writing to a drive that may be failing.

Start with safe hardware and boot checks

Turn the computer off fully. Disconnect nonessential USB storage, memory cards, docks, and external drives, then try starting again. A computer may attempt to boot from removable media instead of its Windows drive.
If the error remains, shut down and unplug the computer before checking connections. On a desktop, a loose SATA data or power cable can prevent a drive from being read. On a laptop, opening the case may be difficult or may affect support coverage; consult its service instructions or a qualified technician. Do not open a powered computer.
Enter the firmware setup or one-time boot menu using the key shown by the computer maker during startup. Check whether the internal drive is detected and whether Windows Boot Manager or the intended system drive is first in the boot order. Menu names and keys vary by manufacturer.
If the drive is absent, repeatedly disconnects, or produces clicking, grinding, or other unusual mechanical sounds, stop trying to boot from it. These signs can point to hardware trouble. Repeated starts and intensive scans can worsen the situation or reduce recovery options.

Do not change firmware settings at random. In particular, switching storage-controller modes can make an existing Windows installation unbootable. If you know a setting was changed, restoring its previous value may help; otherwise, record current settings and check the computer or motherboard documentation first.

Use Windows Recovery Environment

If the drive is detected and there are no warning signs of physical failure, try Windows Recovery Environment (WinRE). When Windows fails to start, it may enter recovery automatically after repeated unsuccessful starts. You can also start from Windows installation or recovery media and choose the repair option rather than installing Windows. The labels can vary slightly, but the usual path is Troubleshoot > Advanced options.

Select Startup Repair and choose the Windows installation if prompted. This tool attempts to diagnose and repair some startup problems. It may not fix hardware failures, and it is not a substitute for a backup.
If Startup Repair does not work, try System Restore only if a suitable restore point is available. It can undo certain system changes while generally leaving personal files alone, but applications, drivers, and settings added after the restore point may be affected.
Use Uninstall Updates only when the problem began after a recent update and the option is offered. Follow the recovery prompts and avoid interrupting the process.

If the drive is encrypted with BitLocker, recovery tools may ask for its recovery key. Find the key through the account or organization that manages the device before proceeding; do not assume recovery will bypass encryption.

Check the file system and boot configuration carefully

Advanced users can open Command Prompt from WinRE, but first confirm the correct drive letter. Drive letters in the recovery environment may differ from those in normal Windows, so the Windows installation that is usually C: might have another letter. A command aimed at the wrong volume can inspect or change the wrong disk.

To identify volumes, use diskpart, then list volume, and exit DiskPart with exit. Match the likely Windows volume by its contents and size; do not run modifying commands until you are certain. The command chkdsk X: /f (replace X with the verified letter) checks file-system structures and attempts repairs. It can take a long time, and repairs write changes to the disk. If hardware failure is possible or the data is valuable and not backed up, prioritize copying or professional recovery over CHKDSK.

Boot repair commands found online are not universal fixes. The right procedure depends on whether the computer boots in UEFI or legacy BIOS mode, how its system partitions are arranged, and whether the Windows boot files are damaged. Incorrect commands can make recovery harder. Prefer Startup Repair first, and follow instructions specific to the device and installation rather than copying a command sequence without checking its assumptions.

When the drive may be failing

A drive that is not detected, repeatedly vanishes, reports errors, or cannot complete reads may be physically failing. Software repair cannot restore a damaged mechanism or failing flash storage. If your files matter and you have no backup, power the computer down and consider a reputable data-recovery specialist. Recovery can be uncertain, and attempting repairs first may reduce the chance of recovering some data.

If the files are already backed up, replace a confirmed failing drive and reinstall or restore Windows. For an SSD or hard drive that remains accessible, the computer manufacturer’s built-in diagnostics or the drive maker’s diagnostic utility may help assess its condition. A clean bill from a short test does not guarantee that a drive will never fail, so keep regular backups.

Common mistakes and next steps

Assuming the message means a bad drive: Check removable media, boot order, cables, and recovery options before drawing that conclusion.
Running every repair command: More commands are not necessarily safer. Some write to the disk or target the wrong partition.
Reinstalling Windows too soon: Installation can overwrite data or complicate recovery. Back up first when possible, and confirm the target disk and partitions before any reinstall.
Ignoring recurrence: A successful restart is not proof the underlying problem is fixed. Back up files and investigate if the error returns.

If hardware checks and WinRE do not resolve the issue, record the exact message, what changed before it began, whether firmware detects the drive, and which recovery steps you tried. That information helps a repair technician distinguish a boot-file issue from a connection or drive fault.

Frequently Asked Questions

Can I fix a disk read error without losing files?
Often, yes, if the cause is boot order, a loose connection, or a repairable startup problem. No repair is guaranteed to preserve data, so back up first whenever the files are accessible and avoid write-heavy repairs if the drive may be failing.

Does CHKDSK fix a disk read error?
It can repair certain file-system problems, but it cannot fix a failing drive or every boot problem. It changes disk data when run with repair options, so confirm the correct volume and consider data recovery first if files are important.

Why does my computer say a disk read error occurred?
Possible causes include a drive that cannot be read, a loose connection, the wrong boot device, damaged file-system data, or Windows boot-file problems. The message by itself does not reveal which cause applies.

Should I reinstall Windows to fix the error?
Not as a first step. Reinstallation may affect files and will not repair faulty hardware. Try safe checks and recovery tools first, and back up or recover important data before reinstalling.

What if the hard drive is not showing in BIOS or UEFI?
Shut down and check connections only if you can do so safely and according to the device instructions. If it remains undetected or makes unusual noises, stop repeated attempts and seek hardware or data-recovery help.

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 →