Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

If I have a clean volume and execute the following command to prevent CHKDSK from occurring,

chkntfs /x c:

If a situation occurred after that and caused the need for a chkdsk on the volume, will the dirty bit still be set in the future or does that command (chkntfs /x c:) also prevent it from being set?

share|improve this question

According to this Knowledge Base article from Microsoft it only prevents Autochk.exe from including the drive for a chkdsk /f during start-up.

Every time Windows restarts, Autochk.exe is called by the Kernel to scan all volumes to check if the volume dirty bit is set. If the dirty bit is set, autochk performs an immediate chkdsk /f on that volume.


The chkntfs /x commands are not cumulative, the command overwrites any previous drive exclusions that have been established. In the above example, chkntfs only disables the chkdsk checking on drives D and E, drive C is not checked for the presence of a dirty bit.

So it shouldn't prevent the dirty bit from being set when there is a problem. You should however check the drive regularly for this dirty bit if you exclude it because you don't get a warning at start-up anymore.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.