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.

133 Comments - Write a Comment

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

Leave a Reply

Your email address will not be published. Required fields are marked *

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.