![]() How to Stop CHKDSK from Running on Every Boot Up. Recently, my Windows 7 computer started running a CHKDSK each and every time that it booted up. For those that don’t know, the CHKDSK utility is a way that Windows validates the system file structure and integrity of your computer’s hard drive. You can scan your hard drive with it or run it with a fix (/f) flag to correct issues on your local hard drive. But, when time is critical, many of us don’t want to wait around while the system is scanned, especially if for some reason, it is happening each and every time you start up. CHKDSK stands for CHECK DISK. In Windows 8/Windows 8.1, with the help of CHKDSK command, you can scan your entire hard disk drive (or each volume of the drive. CHKDSK (short for "check disk") is a system tool in DOS, OS/2 and Windows. It verifies the file system integrity of a volume and fixes logical file system errors. If ChkDsk or Check Disk does not or will not run or finish or complete, on startup or boot in Windows 10 / 8 / 7 or Vista, this article will help you fix the issue. Try the Disk Check from the Command Prompt; In the search bar or Start\Run command, type: CMD.exe, next type: "chkdsk c: /r" (no quotes) and hit Enter. When that happens, you either have a serious problem with your computer, or somehow your system has been automatically set to do this scan. CHKDSK starting. While I don’t condone stopping these scans, especially if your system does indeed have problems, having this run every single time you start up borders on maddening! ![]() So after some digging, research and testing, I have found the way to prevent this from happening. Just a little disclaimer, while I did test this on my machine and it, thus far, did work, if something goes horribly wrong while you do the steps below, I’m not responsible for any data loss or corruption or any issues in general. As I mentioned, I tested this on Windows 7 but I believe this will work on Windows XP as well. I do not know for sure about Windows 8.“Dirty” Hard Drive Check. The first step is to see if you have a “dirty” hard drive. If this test does say that you do, it could be the reason why you continually see a CHKDSK running on every restart. To test this, you need to launch a Command prompt as the Administrator of your computer. Go to Windows Button, and type in “CMD” in the “Search for Programs and Files” box. When the application shows, right- click on it and choose “Run as Administrator.”Run CHKDSK as administrator. Next you will type in the following command to check to see if your hard drive is “dirty” or not: fsutil dirty query x: Where “x: ” is actually the drive letter of your hard drive. For me it was “c: ” but in this article, I will refer to it as “x: ”. ![]() ![]() Backup Disk Image. A copy of hard drives or disk partitions containing occupied sectors only; May contain any set of hard drives & partitions as well as an exact copy. Run the command and if your hard drive is indeed “dirty,” you will see something like this: Hard drive is “dirty”If your drive is “not dirty,” then you may have something else going on. You might still want to go through the following steps though. Tell Windows NOT to Scan at Next Reboot. The next thing that you will do is instruct Windows to not execute the CHKDSK command at the next reboot using the CHKNTFS command. To do this, in the command prompt, type in: chkntfs /x x: Again, be sure to change the “x: ” to whatever drive you are checking. ![]() Disable CHKDSK at next reboot. Now reboot your computer. Hopefully, CHKDSK will not run this time. But you need to go on with the following instructions to ensure your hard drive is ok. Optional: you might want to run the “dirty” check again. When I did, it still said that my drive was dirty. Tell Windows to do a DEEP CHKDSK Scan at Next Reboot. I will preface this set of instructions with a warning. This deep CHKDSK scan will take several hours to run. ![]() On my 5. 00 GB hard drive, it took over 3 hours to complete. If you already have your command prompt open (running as Administrator), issue the following command: chkdsk x: /f /r. Remember to replace the “x: ” with the drive letter of your hard drive. Run CHKDSK at next boot. ![]() ![]() You may have to schedule the chkdsk at reboot, if the drive to be checked, is in use. Command Line Check Disk. And then there is this command line version of chkdsk. UNFORMAT Active@ UNERASER Active@ UNDELETE Active@ File Recovery Active@ Partition Recovery Active@ Password Changer Active@ Boot Disk(Live CD) Active@ Partition Manager. ![]() The /f flag tells windows to fix any issues and the /r flag tells it to do a deep scan. It locates bad sectors and recovers whatever information is readable. Now, restart your system. When it reboots, it will start the CHKDSK process: CHKDSK starting. Head off to do something else, hopefully fun, during this time. It will take a long time for this to complete. CHKDSK finished. Your computer will automatically restart when it is completed. If there are issues, you will see a message on the screen and you may have to do something else or run CHKDSK again. Advertisement. Once you boot back up into Windows, launch the Command prompt again (as Administrator) and check to see if your hard drive is dirty or not. Here is the result of my check: Hard drive is clean! Yay! My hard drive is NOT dirty! I did some more reboots just to be sure that the CHKDSK didn’t pop up again and as of this writing, everything seems to be running as expected. So there you have it. Hopefully this worked for you. Please leave a message to let me know if this fixed your CHKDSK issues on reboot. HTD says: With tech issues, when there is a desire to fix something, there always is some sort of solution. Chk. Dsk or Check Disk will not run at startup in Windows 1. 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 Chk. Dsk. 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. If in spite of your having scheduled chkdsk to run at startup, in Windows 1. 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 chkdskautochk from running. Here are a few troubleshooting steps you can try. To check it, open regedit and navigate to the following registry key: HKEY. 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. Hope this works for you! See these posts if your Chk. Dsk or Check Disk Utility runs at every startup in Windows or if Chk. Dsk is stuck or hangs. Post from WVC updated and ported here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |