Disable or Stop Auto CHKDSK During Windows Startup

One of Windows annoying so called “features” is the Windows disk checker (Chkdsk) being automatically executed whenever you don’t shut down your computer properly. The blue colored screen appears on Windows XP or black colored screen for Windows Vista and 7 during boot that says:

Checking file system on C:
The type of the file system is NTFS.
One of your disks needs to be checked for consistency. You may cancel the disk check, but it is strongly recommended that you continue.
To skip disk checking, press any key within 10 seconds(s).

Simply pressing any key would stop Check disk from running but when you restart your computer, you’ll get this prompt again because Windows still thinks the drive needs scanning and will keep reminding you until it is checked. Sometimes, even after letting Check disk scan the drive that it wants to, the checking process would still automatically run at next boot and it wants to check the drives again.

Disable CHKDSK at startup

What we have found out is that when Windows detects there has been an improper shutdown or a drive such as a USB flash drive has been ejected before the system has finished with it, a secret value is stored on the drive to let Windows know about the issue and force a Check disk request. This value is known as a “Dirty bit” and is a single hex value (2 values for Windows 8) that Windows looks at on boot for system drives or when the the external device is inserted.

One easy way to determine if a drive letter is marked as dirty and will require auto chkkdsk on boot is to run the command fsutil dirty query C: in Command Prompt. If the fsutil tool reports that the drive letter is not dirty, the disk checking process will not want to run for that drive. However, when a drive letter is being marked as dirty, we discovered the location of the hex values on the drive that are being modified and resetting the dirty bit hex value to default will magically stop the auto disk check on boot.

fsutil dirty query

While resetting the dirty bit manually would be the best solution for many situations, it is more difficult to do on system drives such as C because they will be locked and not allow editing from within Windows to change the bit value. Another option for these drives is to simply instruct Windows not to bother checking whether they have been marked as dirty on boot, so you’ll never get a request to auto check them again. Here’s how to disable or stop Check disk from scanning your drives in Windows boot for Windows XP, Vista, 7 and Windows 8.

There are people who suggest editing the registry to do this which works if done properly, but the recommended and safer way to disable auto Check disk from starting up is using the /x switch via the chkntfs command in Command Prompt. This switch will exclude a drive from the default boot time check. To get to the Command Prompt, go to:

Start -> Run (or Win key+R) -> type cmd and press enter

If you have drive C: as the drive you want exclude, then the command to disable chkdsk from scanning the C: drive would be:

chkntfs /x c:

chkntfs switch

If you have a second drive to exclude, C: and D: for example, you can disable Check disk with the command below. Simply add all the drives you want to exclude in this way, separating them with a space.

chkntfs /x c: d:

exclude 2 drives from chkdsk

Sometimes users don’t like editing the registry or using the command prompt, which is why for your convenience, we have created a simple batch file to run the command for you. Download and run the .bat file, then enter the drive letter(s) to exclude from autocheck when prompted, the rest is automatic. Make sure to right click and “Run as Administrator”.

Download Autocheck Boot Exclude.bat

autocheck boot exclude

There are some experts who believe that it’s better not to disable Check disk from scanning your hard drive. But sometimes it makes sense if you don’t want it to scan your hard drive because if it finds anything bad, damaged files will be changed to File00001.CHK. When that happens, you will have to use data recovery software or some third party tools to recognize and recover the CHK files.

There are other important functions the Windows chkntfs command performs you should know about, which are discussed in more detail on page 2.

The chkntfs utility itself works by modifying the BootExecute value in the system registry which is what Windows looks at during boot. For the curious and those who like to see how it works, the BootExecute value is located in the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager

The default value for the BootExecute entry is “autocheck autochk *“. When you use the /x switch in chkntfs, it will add a /k: parameter and drive letter before the asterisk. This parameter excludes volumes from being checked for the presence of a dirty bit. For example, if you run the command “chkntfs /x c:” in a Command Prompt, this would modify the registry entry to “autocheck autochk /k:C *”.

Remove chkdsk


You can also use the chkntfs command to reset the BootExecute registry value back to the default of “autocheck autochk *” if you need to for any reason. This command is quite useful in some circumstances because there’s another well known and common error you might see on boot which is:

autochk program not found – skipping autocheck

If the autocheck entry has become corrupted by software or the settings for it are incorrect, you will see the error. Although it isn’t a vitally important error and won’t stop your computer from booting unless there are serious errors on the C drive, it can be annoying to see on every boot none-the-less. You can use this command to restore the Windows default value of “autocheck autochk *”:

chkntfs /d

This small batch file will make the reset procedure automatic, download and run the file as administrator.

Download Autocheck Reset.bat

Autocheck Reset


There is also a command to schedule a specific drive to be checked at boot. Autochk will run only if the drive is marked as dirty. Simply supply the drive letter(s) after the command.

chkntfs /c c:

The batch script below makes the scheduling automatic, and runs the same as the exclude script. Download, run and supply a drive letter.

Download Autocheck Boot Schedule.bat

Autocheck Boot Schedule

If any of the above methods still don’t work for you, the other option could be to reset the dirty bit on the drive which will force it not to be marked for checking. The drive will have to be edited offline and not through Windows, for more details on how to perform offline dirty bit editing with the minimum of fuss, refer to our article on clearing the dirty bit manually.

135 Comments - Write a Comment

  1. col 1 year ago
  2. Nazi 1 year ago
  3. ann 1 year ago
  4. Jack 1 year ago
  5. [Name} 2 years ago
  6. kevin 2 years ago
  7. Vladimir 2 years ago
  8. Zerry 2 years ago
  9. dale 3 years ago
    • HAL9000 3 years ago
  10. Michael Charles 3 years ago
  11. Andrei 3 years ago
  12. nikos3194 4 years ago
  13. Matt 4 years ago
  14. Paul 5 years ago
  15. Sean 6 years ago
  16. ame 6 years ago
  17. Vikas Chaturvedi 6 years ago
  18. Peter - UK 6 years ago
  19. Bead 6 years ago
  20. Sop 6 years ago
    • MCTomkat 5 months ago
  21. Graham Ansell 6 years ago
  22. Hector Ayala 6 years ago
  23. donny 6 years ago
  24. Ronnie 7 years ago
  25. Liv 7 years ago
  26. Alan 8 years ago
  27. shubham 8 years ago
  28. Jack 8 years ago
    • nath bagde 8 years ago
  29. Chris 8 years ago
  30. C Kalana 8 years ago
  31. rocky 8 years ago
  32. suresh 8 years ago
  33. ricohflex 9 years ago
    • Teduardo Martinique 8 years ago
  34. sailesh 9 years ago
  35. siraj 9 years ago
  36. AS 9 years ago
  37. vishal joshi 9 years ago
  38. sir simon 9 years ago
  39. John 9 years ago
  40. kiran 9 years ago
  41. Thony 9 years ago
  42. Trevor 9 years ago
  43. James 9 years ago
  44. Dodko 10 years ago
  45. L 10 years ago
  46. Endriago 10 years ago
  47. Joe 10 years ago
  48. acatatease 10 years ago
  49. manoj 10 years ago
  50. Rave 10 years ago
  51. متوكل عبدالله 10 years ago
  52. Chris 10 years ago
  53. Sukanta 10 years ago
  54. Paranoid 10 years ago
  55. Hawkeye 10 years ago
  56. sher2011 10 years ago
  57. majid 10 years ago
  58. Cu 10 years ago
  59. nash 10 years ago
  60. Károly Molnár 11 years ago
  61. Leo Masagca 11 years ago
  62. Marc Lester C 12 years ago
  63. justshootme 12 years ago
  64. dimuthu 12 years ago
  65. yasir 12 years ago
  66. Rap Music Guide 12 years ago
  67. Anil G. Gajera 12 years ago
  68. mario0ne 12 years ago
  69. Rudra 12 years ago
  70. Atish 12 years ago
  71. Bharath 12 years ago
  72. vinay chavan 12 years ago
  73. voltsky 12 years ago
  74. Jacques Bouchard 12 years ago
  75. Kirykiry 12 years ago
  76. Grace 12 years ago
  77. n3o 12 years ago
  78. Brahim 12 years ago
  79. sanjay shaw 12 years ago
  80. kryshna 12 years ago
  81. cris69 12 years ago
  82. Hyns 12 years ago
  83. adol 12 years ago
  84. notts 12 years ago
  85. hehe 12 years ago
  86. Joseph 12 years ago
  87. gautam 12 years ago
  88. Franz Capones 12 years ago
  89. Richard 12 years ago
  90. P 12 years ago
  91. Brummie from UK 12 years ago
  92. bob parrish 13 years ago
  93. jeremiah 13 years ago
  94. Cary 13 years ago
  95. Aryan 13 years ago
  96. wez 13 years ago
  97. alkita 13 years ago
  98. Satyaranjan Chongtham 13 years ago
  99. Gre 13 years ago
  100. Kent 13 years ago
  101. Alternal 13 years ago
  102. woross 13 years ago
  103. Barbara Stebbins 13 years ago
  104. Jag 13 years ago
  105. jp 13 years ago
  106. Shivam 13 years ago
  107. ajithkumar.r 13 years ago
  108. ROb 14 years ago
  109. Jim 14 years ago
  110. Krishnan 14 years ago
  111. Naqqash 14 years ago
  112. spunker88 14 years ago
  113. baohp 14 years ago
  114. Rex Aguillon 14 years ago
  115. bashka 14 years ago
  116. arvelle 14 years ago
  117. red 14 years ago
  118. kristijan 14 years ago
  119. Eriek Haelnx 14 years ago
  120. Jagdish 14 years ago
  121. Horace 14 years ago
  122. Chris 14 years ago
  123. Charlie 14 years ago
  124. Chief_runningwater 14 years ago
  125. Nishant 15 years ago
  126. Ryu 15 years ago
  127. John C 15 years ago
  128. Elvis 15 years ago
  129. irjan 15 years ago
  130. bugtea 15 years ago
  131. Nelson 15 years ago

Leave a Reply

Your email address will not be published.

Note: Your comment is subject to approval. Read our Terms of Use. If you are seeking additional information on this article, please contact us directly.