ChkDsk or Check Disk will not run at startup in Windows 10

Whenever we need to detect and fix file system or disk corruption, we run the built-in Windows Check Disk tool. The Check Disk utility or ChkDsk.exe checks file system errors, bad sectors, lost clusters, and so on. If the disk is not in use, the tool runs immediately. But if any of the files on that drive are in use – like say the system drive, then we are required to schedule its scan at boot-time.

Check Disk will not run at startup

If in spite of your having scheduled chkdsk to run at startup, in Windows 10, Windows 8, Windows 7 or Windows Vista, it does not run, it could be because some kernel-mode component may be locking up the drive and preventing chkdsk autochk from running.  It is quite possible that the BootExecute data value in the Registry has been changed or got corrupted. Here are a few troubleshooting steps you can try.

To check it, open regedit and navigate to the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager

ChkDsk will not run

Ensure that the default value of BootExecute in the right side, has been set at:

autocheck autochk *

If not, right-click on BootExecute and choose Modify.

Change the value to its Default, and click OK.

Now try again and see if Check Disk will run.

There is also a possibility that your autochk.exe file situated in the system32 folder may have got corrupted. Run System File Checker or restore your system to a prior good point and check if it helps. This can help you replace the corrupted autochk.exe file with a good one.

Hope this works for you!

See these posts if your ChkDsk or Check Disk Utility runs at every startup in Windows or if ChkDsk is stuck or hangs.

Post from WVC updated and ported here.

Posted by on , in Category Windows with Tags
Anand Khanse is the Admin of, a 10-year Microsoft MVP Awardee in Windows (2006-16) & a Windows Insider MVP. Please read the entire post & the comments first, create a System Restore Point before making any changes to your system & be careful about any 3rd-party offers while installing freeware.


  1. User

    all this did was render my system unbootable. THANKS!!

  2. See if you can boot into safe mode and restore the system.


    It just says “Cannot Edit BootExcute, Error writing the value’s new contents”

    This is what the value is set to: “autocheck autochk /r ??C:

    autocheck autochk *”

  4. Windows7User

    I got exactly the same problem:

    It just says “Cannot Edit BootExcute, Error writing the value’s new contents”

    This is what the value is set to: “autocheck autochk /r ??C:

    autocheck autochk *”

  5. Windows7User

    Solved after running chkdsk from a Windows 7 install DVD

  6. Dorian Gray

    Isn’t “lsdelete” a line needed for LavaSoft programs that wouldn’t be present otherwise? That might be why your commenters are having difficulties. If you don’t have Ad-Aware or another LavaSoft program installed on your machine, that “lsdelete” line is going to call something that doesn’t exist. The rest of it is fine.

  7. peterq

    boot into safe mode with command prompt and run chkdsk

  8. Thanks. Updating the post.

  9. Jawad Shah

    I have tried that and I still get a msg saying that disk C: is in use, would you like to chckdsk at restart? plus the registry values are correct. How can I tell if the chkdsk is ACTUALLY running in the background?

  10. Bob

    ckhdsk would not be running in the background. If it runs at startup, you will know because the system will not boot into the OS until it is done.

  11. Jawad Shah

    after “scheduling” it run at boot, it always booted the OS and never did actually ran. I had to create a boot disk, boot from the disk and had to launch cmd line utility from there – i was then able to run it. Thanks for the help.

  12. Nam

    It’s in autochk*. I have also tried sfc/ scan now and at 68% it stops. I have tried several times setting error checking in from c drive tool as well as cmd prompt. But it not starts the file check

  13. FiddleSticks

    This doesn’t do you much good if you can’t boot to windows in the first place..

  14. Novice guy 123

    I was having similar issue on dell latitude laptop, It would not run chkdsk on reboot. The solution I found was during start up, tabbing F8 key. This brings up repair and restore option. Use top option “Repair your Computer”. Be sure when prompted to log in with profile that has administrator rights. A menu pops up, first use “Startup Repair” it clear up and correct start up issues. Then use the command prompt and run your chkdsk /f or whatever chkdsk command you like.

  15. Novice guy 123

    May be a better option then messing around with registry or other complex and multiple steps

  16. Sanu

    when i chkdsk c: in win7 it stops at 9% says file record segment 220974 is an orphan…regedit bootexecute value is autocheck autochk*…what to do?…

  17. Bflu

    Good morning… My chkdsk doesn’t show up anymore. When I schedule it and reboot, it just goes right
    back to my desktop and chkdsk doesn’t run at all. I have disk errors I can’t fix. System restore won’t work because there are disk errors and it says to fix them before trying system restore? But I can”t find chkdsk and I tried running as admin, but nothing happens. I don’t know how to go to run system checker

  18. Chris

    No posted solutions I could find worked for my paradox> couldn’t run chkdsk because of so called recently installed software package, which prompted me to do a system restore, and system restore prompted me to run chkdsk. I pulled my hard drive and plugged it as a secondary in my friends PC, and ran chkdsk from there. It fixed everything.

  19. Victor Rosez

    Happens when “No GUI boot” in msconfig is checked to gain boottime. Uncheck and try run chdisk again: see

  20. Victor Rosez

    Gui boot or no Gui boot can make the boot a little bit faster but sometimes chdsk schedule will not work by start up after you checked the better uncheck “no Gui boot” in msconfig

  21. When this problem caused, I also cannot be able to run the chkdsk command. Then I called the online tech support department of AskPCTechies and they had resolved all the issues successfully.

  22. Convert

    This fixed it for me. Thanks.

  23. Parnell Perry

    This may help some of you reading this older thread. It worked for me on an old xp machine. Open:

    My Computer>c:drive>Windows>system32.

    Locate and delete the autochk.exe file.

    Refresh the system32 window. A new autochk.exe file will appear.

    Run chkdsk again and see if it works. If it
    does, the old file was corrupt and has now been replaced with a new one by the Operating System.

  24. Michael Hill

    My BootExecute is set to autocheck autochk * and it is does still chdsk every boot. I am running windows 10 off another hard drive and have to go into bios to tell it to boot Windows 10. When it does the default Widnows chdsk is what I get. Can I set the BootExecute it to something else? What can I set it to so that it never does a chdsk.

Leave a Reply

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

3 + 6 =