Overview
The "dirty bit" is a flag Windows sets on a volume when it suspects the file system may be inconsistent — for example after an improper shutdown. When set, Windows runs CHKDSK on that volume at the next boot. This guide explains how to check, clear, and manage the dirty bit.
The volume dirty bit triggers a disk check at the next boot.
Key Takeaways
- The dirty bit flags a volume as possibly inconsistent.
- When set, Windows schedules CHKDSK at boot for that drive.
- Check it with: fsutil dirty query C:
- Running CHKDSK (and fixing errors) clears the dirty bit.
What Is the Dirty Bit?
It is a per-volume flag in the NTFS file system. Windows sets it when a volume is mounted for writing and clears it on a clean dismount. If the system crashes or loses power, the bit stays set, signalling that the volume should be checked.
How to Check the Dirty Bit
1. Open Command Prompt as administrator.
2. Run: fsutil dirty query C: (replace C: with the drive).
3. It reports whether the volume is dirty or not.
How to Clear the Dirty Bit
1. The correct way is to let Windows check the disk: run chkdsk C: /f and allow it to schedule a scan at restart.
2. Restart — CHKDSK repairs errors and clears the dirty bit if the file system is healthy.
3. Re-check with fsutil dirty query C: to confirm it is no longer dirty.
Warning: Avoid forcibly clearing the dirty bit (e.g. with a hex editor) without running CHKDSK — it can hide real file-system corruption and risk data loss.
Stop Unnecessary Disk Checks at Boot
1. If CHKDSK keeps running at every boot despite a healthy disk, you can exclude the drive: run chkntfs /x C:
2. To restore the default behaviour later: run chkntfs /d
3. Use this only if you are sure the disk is healthy.
Troubleshooting
Problem: CHKDSK runs at every startup.
Solution: Run chkdsk C: /f /r once to fully repair the volume; if it persists on a healthy disk, exclude it with chkntfs /x C:.
Problem: The dirty bit will not clear.
Solution: The volume has unresolved errors. Run a full chkdsk /f /r; if errors remain, the drive may be failing — back up and test it.
Problem: fsutil says access denied.
Solution: Run Command Prompt as administrator.
Problem: You want to keep your data safe.
Solution: Never bypass CHKDSK with a hex editor; always let the disk check run so real corruption is repaired.
Conclusion
The dirty bit is Windows’ way of flagging a volume for checking. Query it with fsutil dirty query, clear it the safe way by running CHKDSK, and only suppress boot-time scans on a drive you know is healthy.
</w:pBdr><w:spacing w:before="220" w:after="40"/></w:pPr><w:r><w:rPr><w:b/><w:bCs/><w:color w:val="0B5394"/><w:sz w:val="21"/><w:szCs w:val="21"/><w:rFonts w:ascii="Calibri" w:cs="Calibri" w:eastAsia="Calibri" w:hAnsi="Calibri"/></w:rPr><w:t xml:space="preserve">About TechHub
This guide is part of the TechHub Knowledge Base. For more step-by-step IT guides and support, visit techhub.com.lk.
