Windows may run CHKDSK at startup when it detects filesystem problems or when a disk check was scheduled. Repeatedly canceling it can hide a failing drive or unresolved corruption, so first determine why the check keeps returning.
Let a legitimate check finish when possible
If Windows scheduled CHKDSK after an improper shutdown or disk error, allow it to complete with reliable power connected. Interrupting a repair pass can leave filesystem problems unresolved.
See whether a volume is marked dirty
Open an elevated Command Prompt and use fsutil dirty query C: for the relevant volume. A dirty flag indicates Windows believes the filesystem needs checking.
Review scheduled disk checks
The chkntfs command can display or modify startup checking behavior. Do not exclude a drive merely to suppress warnings; investigate SMART/drive health and back up important data first.
Check the drive itself
Repeated filesystem errors, slow reads, clicking, I/O errors, or recurring bad sectors can indicate hardware trouble. Back up immediately and use the drive or PC manufacturer’s diagnostics.
Windows 10 standard support ended in 2025. On compatible hardware, plan a move to Windows 11 after resolving storage health problems rather than carrying a questionable disk into an upgrade.
Check the result after Windows starts
Event Viewer can record Wininit/Chkdsk results for checks performed during startup. Review the reported filesystem status instead of assuming that reaching the desktop means the disk is healthy.
Kermit Matthews is a freelance writer based in Philadelphia, Pennsylvania with more than a decade of experience writing technology guides. He has a Bachelor’s and Master’s degree in Computer Science and has spent much of his professional career in IT management.
He specializes in writing content about iPhones, Android devices, Microsoft Office, and many other popular applications and devices.