Windows 10 Drive-Corruption Bug: What Microsoft Fixed

Microsoft has addressed a Windows 10 issue involving the Windows file system command chkdsk that could damage a drive’s file system in a narrow set of circumstances. The bug was not a general flaw that made hard drives easy to corrupt, and Microsoft’s published workaround and update applied to affected Windows 10 versions.

What the Windows 10 bug did

The issue concerned chkdsk, short for Check Disk, a built-in utility for checking a volume’s file system and, depending on the options used, attempting repairs. In the affected case, running the utility with its repair option could leave the file system damaged rather than fixed. A damaged file system can make files or a volume inaccessible, but that is not the same as physically damaging the disk hardware.

The headline description that the bug could “corrupt a hard drive easily” needs qualification. Microsoft’s documentation described a specific software problem associated with particular Windows 10 builds and a particular repair operation—not a routine consequence of using Windows, opening files, or running every disk check. The risk was serious for someone whose computer was affected, but it should not be read as evidence that all Windows 10 PCs or storage devices were at immediate risk.

Which computers were affected

Microsoft reported the issue in Windows 10 version 2004, also known as the May 2020 Update, and version 20H2, the October 2020 Update. Its Windows release-health information identified the affected builds and documented the resolution. The relevant details can vary by update history, so the most reliable way to determine a PC’s status is to check its installed Windows version and latest updates rather than relying on a headline or an old forum post.

Windows 10 version 2004 and 20H2 are no longer supported versions. Windows 10 Home and Pro support ended on October 14, 2025; some other editions and eligible devices may have different support arrangements. A PC still running an old build should not assume it is protected simply because Microsoft fixed the issue years ago. It should be moved to a currently supported operating system or supported edition where possible, using Windows Update or an administrator’s approved update process.

How the issue worked

chkdsk checks structures that Windows uses to organize files on a volume. Its /f option asks it to fix file-system errors. On a system volume—the one Windows is running from—Windows may schedule the check for the next restart because it cannot freely repair a volume that is in use.

Microsoft’s report concerned a problem in that repair path. It was not a claim that the utility’s ordinary read-only inspection always caused damage, nor that all types of disk errors were caused by the Windows bug. File-system corruption can also result from power loss during writes, failing storage hardware, defective cables, or other software faults. Those causes require different investigation.

It is useful to distinguish three things:

File-system damage: Windows’ records of folders and files become inconsistent or unreadable.
Data loss: Some files become unavailable or are overwritten; recovery is not guaranteed.
Physical drive failure: The storage device itself has a hardware problem. A Windows update cannot repair failing hardware.

What Microsoft did and what users should do

Microsoft documented a workaround and later a resolution through Windows updates for the affected releases. The precise advice depended on the build and the state of the computer. For that reason, users should consult Microsoft’s Windows release-health documentation for the applicable version instead of applying an old command-line workaround from an unrelated article.

If you are maintaining a Windows 10 PC now, take these sensible steps:

Check the version: Open Settings > System > About and review the Windows specifications. You can also type winver in Start to see version information.
Install available updates: Open Settings > Update & Security > Windows Update and select Check for updates. On managed computers, follow the organization’s instructions.
Back up important files: Keep a current copy on a separate device or a trusted backup service. A backup is important because neither a repair utility nor a Windows update guarantees recovery from existing corruption.
Do not repeatedly run repair commands on a suspect drive: If files have disappeared, Windows reports disk errors, or the device makes unusual noises, prioritize preserving data and diagnosing the drive. Repeated writes can complicate recovery, particularly if hardware is failing.
Use current support guidance: If an old machine cannot update, check its support options and hardware compatibility. Avoid treating a years-old workaround as a substitute for security and servicing updates.

What to do if files or a volume are inaccessible

First, avoid saving new data to the affected volume. If the files matter, make a separate copy of anything still accessible and consider professional data-recovery help when the drive appears to be failing or the data is irreplaceable. Recovery tools may help in some cases, but installing or running them on the affected drive can overwrite data.

If the device is stable and the problem appears limited to file-system errors, use Microsoft’s current instructions for the exact Windows version and the relevant volume. Do not interrupt a repair that is already in progress unless the computer is clearly unresponsive and you have considered the risks. For a system drive, Windows may request a restart to perform a check before loading the desktop.

After the data is safe, investigate whether the cause is software or hardware. Windows’ built-in error checks can report issues, but a clean result does not prove that a drive is healthy. Repeated errors, disappearing volumes, or read failures warrant further diagnosis and replacement planning rather than repeated repair attempts.

Common misconceptions and prevention

A common misconception is that any use of chkdsk will wipe a disk. That is not what Microsoft reported. The utility is designed to check and repair file-system structures, but repairs alter data structures and can have consequences when corruption is already present. It should be used for a reason and with a backup—not as a routine cure-all.

Another misconception is that an update can restore files that were already lost. A fix prevents or resolves a software defect; it does not necessarily reverse damage that has happened. Backups remain the most dependable protection against accidental deletion, corruption, and hardware failure. For Windows 10 computers that remain in use, keeping the operating system supported and the backup current are more useful safeguards than avoiding every disk-check utility.

Frequently Asked Questions

Did Microsoft fix the Windows 10 chkdsk bug?
Microsoft documented a resolution through updates for the affected Windows 10 releases. The fix does not make unsupported installations current; check the installed version and update status.

Could the bug physically break my hard drive?
The reported issue involved file-system corruption, not physical damage to the drive’s hardware. Physical failure can cause similar symptoms but has different causes.

Is it safe to run chkdsk now?
Use it when troubleshooting a relevant file-system problem and follow current Microsoft guidance for your Windows version. Back up important data first, especially if the drive is showing signs of failure.

How do I check which Windows 10 version I have?
Open Settings > System > About, or type winver in the Start menu and press Enter.

Can a Windows update recover files already lost?
Usually, an update addresses the software issue; it does not guarantee recovery of data already made inaccessible. Avoid writing to the affected drive and seek appropriate recovery help if the files are important.

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 →