How to disable CHKDSK completely on startup

Hi, anyone knows how to disable CHKDSK completely on startup? it's driving me nuts, trying to scan all of my drives, even the system reserved partition! I don't know why this is happening.

You could try using the /x "kill" command from an elevated command prompt.

Elevated Command Prompt

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

chkntfs /x c:

If you have 2 drives, let's say C and D, you can disable chkdsk like so:

chkntfs /x c: d:

then go ahead and reboot.

thanks for the reply, i can disable those drives with letters, but chkdsk is requesting to check system reserved partition too. what the hell is wrong with windows? why isn't there a way to fully disable that chkdsk program?

Here's an MS article I found that may help you.
It seems update KB2823324 causes this for some Win 7 x64 systems.
CHKDSK Running on every boot

"Claude1777" has a suggested fix in this Microsoft thread (second post) that seems to have worked for several people:

System File Checker wants to run every time I boot Windows but it - Microsoft Community

And "keggers" found one in this Microsoft thread (near the bottom):

chkdsk error (766f6c756d652e63 3f1) on windows 7 system reserved partition

Just a reminder, it might be advisable to make a System Restore Point just in case.

- - - - - - - - - - - - - - - - - - - -

Computers are great ... computers are great ... computers are great ...

DavidW7ncus said:

Here's an MS article I found that may help you.
It seems update KB2823324 causes this for some Win 7 x64 systems.
CHKDSK Running on every boot

marsmimar said:

"Claude1777" has a suggested fix in this Microsoft thread (second post) that seems to have worked for several people:

System File Checker wants to run every time I boot Windows but it - Microsoft Community

And "keggers" found one in this Microsoft thread (near the bottom):

chkdsk error (766f6c756d652e63 3f1) on windows 7 system reserved partition

Just a reminder, it might be advisable to make a System Restore Point just in case.

- - - - - - - - - - - - - - - - - - - -

Computers are great ... computers are great ... computers are great ...

Thank you guys, i gave the system reserved partition a drive letter and it solved the problem :)

lala1990 said:

Thank you guys, i gave the system reserved partition a drive letter and it solved the problem :)

Be real careful. I would, now that you've solved the issue, go back and unassign the drive letter to prevent losing any files in that reserved partition.

lala1990 said:

Thank you guys, i gave the system reserved partition a drive letter and it solved the problem :)

PeaB4YouGo said:

Be real careful. I would, now that you've solved the issue, go back and unassign the drive letter to prevent losing any files in that reserved partition.

Glad to hear assigning a drive letter solved the problem. And that's excellent advice by Pea.

I joined to say "this worked for me" but I'm bumping up this post because I actually settled on marking the partition as hidden instead of assigning a drive letter, which is safer.

Re-assigning the drive letter did eliminate the problem I had where Windows 7 would always want to run chkdsk on the system partition every start-up after a drive clone. First I re-assigned the letter, but then I canceled that and tried hiding the partition instead, which also worked. So, the system partition is now marked as primary, active, boot, and hidden.

The problem started only after I cloned from a drive with a SMART imminent failure warning. There seems to have been damaged files, but I don't know which ones, and there were damaged sectors on the drive that were repaired. I also had to run the windows update fix-it application, which took something like 12 hours to get to where I could do windows updates, and then another 12 hours of the actual updates. The system is now running at a reasonable speed, and I'm hoping the BSDs are done with.

I then was able to re-enable chkdsk, and I am guessing everything will finally have been fixed after that long saga of repairs.