A-Z List


Chkntfs

Updated: April 17, 2012

Applies To: Windows Server 2008, Windows Vista

Displays or modifies automatic disk checking when the computer is started. If used without options, chkntfs displays the file system of the specified volume. If automatic file checking is scheduled to run, chkntfs displays whether the specified volume is dirty or is scheduled to be checked the next time the computer is started.

noteNote
To run chkntfs, you must be a member of the Administrators group.

For examples of how to use this command, see Examples.

Syntax
chkntfs <Volume> [...]
chkntfs [/d]
chkntfs [/t[:<Time>]]
chkntfs [/x <Volume> [...]]
chkntfs [/c <Volume> [...]]
Parameters

 

Parameter Description

<Volume> [...]

Specifies one or more volumes to check when the computer starts. Valid volumes include drive letters (followed by a colon), mount points, or volume names.

/d

Restores all chkntfs default settings, except the countdown time for automatic file checking. By default, all volumes are checked when the computer is started, and chkdsk runs on those that are dirty.

/t [:<Time>]

Changes the Autochk.exe initiation countdown time to the amount of time specified in seconds. If you do not enter a time, /t displays the current countdown time.

/x <Volume> [...]

Specifies one or more volumes to exclude from checking when the computer is started, even if the volume is marked as requiring chkdsk.

/c <Volume> [...]

Schedules one or more volumes to be checked when the computer is started, and runs chkdsk on those that are dirty.

/?

Displays help at the command prompt.
Examples

To display the type of file system for drive C, type:

chkntfs c:

The following output indicates an NTFS file system:

The type of the file system is NTFS.
noteNote
If automatic file checking is scheduled to run, additional output will display, indicating whether the drive is dirty or has been manually scheduled to be checked the next time the computer is started.

To display the Autochk.exe initiation countdown time, type:

chkntfs /t

For example, if the countdown time is set to 10 seconds, the following output displays:

The AUTOCHK initiation countdown time is set to 10 second(s).

To change the Autochk.exe initiation countdown time to 30 seconds, type:

chkntfs /t:30
noteNote
Although you can set the Autochk.exe initiation countdown time to zero, doing so will prevent you from canceling a potentially time-consuming automatic file check.

The /x command-line option is not accumulative. If you type it more than once, the most recent entry overrides the previous entry. To exclude multiple volumes from being checked, you must list each of them in a single command. For example, to exclude both the D and E volumes, type:

chkntfs /x d: e:

The /c command-line option is accumulative. If you type /c more than once, each entry remains. To ensure that only a particular volume is checked, reset the defaults to clear all previous commands, exclude all volumes from being checked, and then schedule automatic file checking on the desired volume.

For example, to schedule automatic file checking on the D volume but not the C or E volumes, type the following commands in order:

chkntfs /d
chkntfs /x c: d: e:
chkntfs /c d:
Additional references

Command-Line Syntax Key

Tags :


Community Content

BezantSoft
Where to find results of Chkntfs operations
You can find the results in the Application Event Log, one entry per repaired NTFS volume. I found the results question when I was looking at the Chkntfs, to see what had been changed with Windows 7.&nbsp; My Chkntfs log entry has the following text:<br /><blockquote><pre>Log Name: Application<br />Source: Microsoft-Windows-Wininit<br />Date: 2011-06-13 10:09:40<br />Event ID: 1001<br />Task Category: None<br />Level: Information<br />Keywords: Classic<br />User: N/A<br />Computer: Full Computer Name.here<br />Description: [no description here in my logs]<br /><br />Checking file system on C:<br />The type of the file system is NTFS.<br />Volume label is VolumeLabel.<br /><br />One of your disks needs to be checked for consistency. You<br />may cancel the disk check, but it is strongly recommended<br />that you continue.<br />Windows will now check the disk. <br /><br />CHKDSK is verifying files (stage 1 of 3)...<br /> 276736 file records processed. <br />File verification completed.<br /> 500 large file records processed. <br /> 0 bad file records processed. <br /> 2 EA records processed. <br /> 111 reparse records processed. <br />CHKDSK is verifying indexes (stage 2 of 3)...<br /> 349910 index entries processed. <br />Index verification completed.<br /> 0 unindexed files scanned. <br /> 0 unindexed files recovered. <br />CHKDSK is verifying security descriptors (stage 3 of 3)...<br /> 276736 file SDs/SIDs processed. <br />Cleaning up 173 unused index entries from index $SII of file 0x9.<br />Cleaning up 173 unused index entries from index $SDH of file 0x9.<br />Cleaning up 173 unused security descriptors.<br />Security descriptor verification completed.<br /> 36588 data files processed. <br />CHKDSK is verifying Usn Journal...<br />The USN Journal length 0x31d1309c8 in file 0xa227 is less the<br />largest USN encountered, 0x31d1313b0, plus eight in file 0x69fd.<br />Repairing Usn Journal $J data stream.<br />Usn Journal verification completed.<br />CHKDSK discovered free space marked as allocated in the<br />master file table (MFT) bitmap.<br />CHKDSK discovered free space marked as allocated in the volume bitmap.<br />Windows has made corrections to the file system.<br /> 488384511 KB total disk space.<br /> 120433076 KB in 220344 files.<br /> 105088 KB in 36589 indexes.<br /> 0 KB in bad sectors.<br /> 358835 KB in use by the system.<br /> 65536 KB occupied by the log file.<br /> 367487512 KB available on disk.<br /> 4096 bytes in each allocation unit.<br /> 122096127 total allocation units on disk.<br /> 91871878 allocation units available on disk.<br />Internal Info:<br />[3 hex info lines here]<br />Windows has finished checking your disk.<br />Please wait while your computer restarts.<br /><br />Event Xml:<br />[Balance of "Copy Details as Text" has the xml of the above information in the eventlog format]<br /></pre></blockquote><p>I seem to remember that much the same data has been in the event log at least back to NT v4.</p><p /><blockquote><pre /></blockquote>
Tags :

Drewfus
Dirty status and exit codes?
<p>The command<br /><br /></p> <pre>chkntfs c:</pre> <p> <br />not only returns something like<br /><br /></p> <pre>The type of the file system is NTFS.<br /></pre> <p> <br />but also the dirty status of the volume.<br /><br /></p> <pre>C: is not dirty.</pre> <p>or<br /></p> <pre>C: is dirty. You may use the /C option to schedule chkdsk for this drive.<br /></pre> <p> <br />In the first case an exit code of 0 is returned (%errorlevel%==0).<br />In the second case an exit code of 1 is returned.<br /><br />This is useful info for batch files:<br />Ex1:<br /></p> <pre>chkntfs c:<br />if errorlevel 1 chkntfs /C c:<br /></pre> <p> <br />Ex2:<br /></p> <pre>chkntfs d:<br />if errorlevel 1 chkdsk d: /X</pre> <p> <br />Btw, you can test this scenario by setting the dirty flag on a volume using the fsutil command.<br /><br /></p> <pre>&gt; fsutil dirty set c:<br />Volume - c: is now marked dirty</pre>
Tags : contentbug

RainerXXL
Where is the report stored after execute chkntfs?
Looking for my expecting report from my execute chkntfs, because the execution went as quick that it was impossible to watch where a possible report has been gone.
Tags : report expect;

Page view tracker