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.

116 Comments - Write a Comment

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