"Restart to repair drive errors" keep showing up after reboot

Anonymous
2012-11-21T08:24:05+00:00

Hi all,

I recently used the error checking tool on my internal hard drive on my laptop. It found errors and told me to reboot. Now everytime I boot my pc a message in the action center pops up saying "Restart to repair drive errors", and no matter how many times I try, it still tells me there are drive errors.

I can't seem to find any more details on the exact errors. I run Windows 8 Pro. Can anyone help me or point me in the right direction?

EDIT: Running Chkdsk from the command promt returns a similar error, albeit a little more wordy: "Chkdsk cannot run because the volume [the C: drive, the one that has errors -RF] in in use by another process. Would you like to schedule this volume to be checked the next time the system restarts?" Replying <y> and rebooting, gives the same errors: the action center still tells me to reboot, and Chkdsk returns the same message as before.

I also tried running sfc, just for good measure. The log created (CBS.log) shows several errors at the bottom, seemingly all pertaining to autochk.exe, in some way or another.

I wonder if this may have been caused by running drive optimization and stopping prematurely (in order to reboot for the error checking utility).

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

73 answers

Sort by: Most helpful
  1. Anonymous
    2017-12-04T01:16:26+00:00

    That is exactly the same as running rom File Explorer because when you open up This PC it brings up File Explorer. The problem is that while I can scan my Primary drive from Windows 10 using error checking, you have to reboot first. Perhaps it is because I am using a Solid State Drive as my boot drive, but who knows.

    That aside, you are doing it right. First, if there were any errors with your drive, chkdsk would give you an error message, either reporting the bad sectors as it finds them if you are watching (boring huh?) if before rebooting.

    There should be an error log stored in the event viewer, or at least that's what happens when you don't reboot when running error checking.

    To access event viewer, Right click on the Windows symbol on the lower right hand corner and select Event Viewer near the top of the list. Didn't see that coming, did you? Needed a joke at this point. Okay, after opening Event Viewer, look for Windows Logs in the left hand pane in the window and click on the arrow to the left of it to open the sublist.

    Click on Applications and look in the right hand or middle pane for an application with the source labeled as chkdsk. It will also have the time and date that it was run. If it is there, click on it and you will have all the information I have been talking about. If there is nothing labeled chkdsk, I guess the log is either not being saved when run when rebooting or it is being saved elsewhere (maybe in your Windows  folder).

    Assuming it is there, clicking on the chkdsk log will show a General list of items that you can scroll through, and a separate tab for the Detailed information. General will probably tell you enough to see if there is a problem with your drive or it is an operating system glitch. If it is a glitch, you are going to have to check other sites for this problem using Google because it is pretty obvious his thread should have a solution after so many years, but only some of us have been successful.

    I've tried. Hope you have some success. Let me know if this works out, as I'm feeling invested, and no, I don't work for Microsoft. Good luck. Don't forget, there is a freeware program called Malwarebytes that might indicate a problem if this doesn't give you a solution (other than a broken hard drive that needs replacing, which I doubt). Just Google it. The answer to all. Bye.

    The way I run/ran Error Checking, I go to This PC, right click my C drive, click Properties, click Tools then Error Checking.  I normally get, the volume is in use and it will run following a restart.  I Restart the Laptop and see that the scan is about to start giving a few seconds to by pass.  I do nothing, you see the % of completion...it gets to 100% and goes to Windows.  No report, nothing to click on that displays view report, etc

    Does window capture the Error correcting report and store it in a file that is user accessible?  Or, am I running Error Checking incorrectly and that is the reason I see nothing to view a report of findings/results?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2017-12-02T22:34:31+00:00

    You might try deallocating your paging file, then "rebooting and running the CHKDISK" a couple of times.  If the error goes away and stays away, reallocate you paging file.

    Otherwise ...

    Laptops seem to follow a standard for external size and configuration.  So you will be able to replace the questionable hard drive with something from WD (WD Black is my favorite) or another disk drive company ($60-$90).  (If it is an old 2-1/2 drive kicking around that you're reusing, check the drive height, some of the early ones were 1-2 mm higher than the newer ones.)

    I'd replace the current HDD by removing the current HDD from the laptop and hooking it and the new HDD up to a desktop to do a disk-to-disk copy using the free software off the website for the destination hard drive's manufacturer.  (Usually it is a stripped down version of Acronis.)

    Brace the drives so they'll be physically steady during the copying process.


    In my case the way I was able to are resolve the issue was to copy all the user files off my D: drive (the one with the problem) onto my E: drive.  Then remove the paging area off of my D: drive.  Then run a disk check both from the reboot and withing Windows.

    Then I allocated and formatted my D: drive.

    I've had no problems since.

    But I had the luxury of already having one SDD and two HDDs in my computer.

    In your case I think you'll need to buy an extra HDD so you can try similar solutions.


    333 people indicating here alone that they too have had this thorny problem.  So probably tens of thousands have had this problem and not sought help here. 

    You'd think MS would wake-up and fix the root cause of the problem which (since the HDDs end up working fine for years afterwards) is a coding or design error in CHKDISK.

    Instead we have to each find a bypass fix.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2014-03-16T15:28:02+00:00

    Yeah man i finally fixed it!!!

    I got this error past week...

    So here we go in order to solve it!!!

    First of all try error checkingon each drive.

    In most cases windows will repair all the drives except the C: Drive(or OS drive).

    If windows is unable to repair other drives too and asks for Restart and repair now or Restart later and repair , just hit cancel and follow the instructions below for both OS drive and other drives

    1.Run CHKDSK command for each drive from command prompt.

             #open command prompt with admin rights.

             #perform CHKDSK , example CHKDSK X: /f ('X' represents drive letter)

    2.If the CHKDSK command says CHKDSK cannot run because the volume is in use by another

       process.Would you like to schedule this volume to be checked the next time the system

       restarts? (Y/N)

    3.Hit Y

    4.Now open Run (Windows + R) type msconfig and hit enter

             #go to boot tab.

             #in the Boot options,click Safe boot and and then click Aletnative Shell in sub options

               (Alternative Shell means Safe mode with Command Prompt).

             #hit OK ,now it will ask for restart , now hit restart.

    5.Now when your computer reboots windows will automatically repair the drives you scheduled in   CHKDSK command in safe mode. After everything is done rollback everything you did it msconfig

    ( i.e uncheck Safe boot and hit ok ) and restart, now your computer will restart in normal mode. Again check Error checkingand scan drive even if there are no errors.                                                                                           

    I tried my best to help you guys from this post, if you are still facing problem contact me

    hope this will help :)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2013-11-27T16:30:10+00:00

    hardware mfr. (lenovo) says its an os issue pertaining to latest update. I am shocked. SHOCKED.

    Look - the problem is that your software gives people the impression that there is a simple fix to this issue: restarting the computer. However, in most (or nearly all) cases it is not this simple, and the error messages that come up provide no help as far as further troubleshooting.

    Then, on top of that, your official answer is useless to those of us who opted not to be charged extra for a backup DVD. Why would you sell a product that is prone to breakage, and then charge extra for the tool that you specify to fix it? That's just bad customer service, plain and simple.

    If I could cut windows and MSFT out of my life entirely, I would.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2013-09-28T11:44:43+00:00

    The problem is that the OS your company sells gives a ridiculously vague warning message.

    Currently I see the same thing: "Restart to repair drive errors."

    Really? I have 5 drives connected to my laptop. Does the warning  tell me which drive or which partition is experiencing the error? Of course not! That might actually be helpful information that would let me drill down to a solution to the specific problem.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments