BUG: CHKDSK stuck at 11% for hours, but was actually working

Anonymous
2013-10-29T15:12:28+00:00

I ran CHKDSK on my Windows 8.1 Pro 64bit laptop.  The message said that it was up to 11% and then it stopped advancing for ages.  I thought that CHKDSK had stalled or crashed, but it turns out that it was working, it's just that it took several hours to complete one stage but it didn't update the progress indicator.

MORE DETAILS

I ran CHKDISK from the command prompt on my C drive and it offered to run the command on the next restart.  I answered yes and restarted, and CHKDSK ran, updating its progress, but it stopped at 11% and stayed there for ages and ages.

Note that in Windows 8.1, CHKDSK doesn't display lines of text as it goes along like in certain earlier versions of Windows.  It just displays a single line, e.g. "Scanning and repairing drive (C:): 11% complete" that gets updated from time to time.

At first I thought it was stalled or crashed, so I rebooted the laptop.  CHKDSK ran again and once again got stuck at 11%.  So I rebooted the laptop with a recovery USB and ran CHKDISK from the command prompt.  This one displayed more progress information.  It estimated that a particular stage would take 3 or 4 hours (it fluctuated from one to the other at first before settling on over 3 hours and then slowly counting down).  After several hours it completed successfully, fixing some errors and reporting its results.

I rebooted the computer again, from the hard drive.  CHKDSK ran again (since it didn't complete before) and after several hours it completed.  It warned me that Windows didn't close normally (because I interrupted the previous CHKDSK) and gave me some options.

So it looks like there's one stage in CHKDSK where the status line isn't getting updated regularly.  Could Microsoft please fix this?

EDIT: corrected spelling of subject heading.

Windows for home | Previous Windows versions | Windows update

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

66 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2017-10-15T23:50:45+00:00

    in reply to Mike Gyt  9/25.16  Quot " Just to make sure that all issues are found and dealt with, run a check disk scan first, by typing in the command

    chkdsk C: /scan

    and pressing the Enter key. As it scans, it will fix anything that it can without being offline. Once that is finished, type in the command

    chkdsk C: /spotfix

    and press the Enter key. You’ll see the command prompt tell you that it, “…cannot run because the volume is in use by another process.” It will then ask you if you, “Would… like to schedule this volume to be checked the next time the system restarts? (Y/N)” Type Y and press Enter to schedule Check Disk. Now, restart your computer.

    This time Check Disk will run and fix any problems that were identified in the scan. Because it’s only fixing those specific problems, the process only takes a few seconds to a few minutes." Unquote 

    IT ALSO  WORKS PERFECTLY IN WINDOWS 10.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2016-08-31T12:06:16+00:00

    Isn't running /f /r in same chkdsk redundant because in running /r, /f is implied?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2016-01-08T19:35:13+00:00

    When Windows 8.1 starts loading (Windows logo with loading circle below), start pressing any key or esc, It is crazy that microsoft left 1 sec to skip chkdsk. This will skip checkdisk

    It took three tries but it worked. I was using AVG's Tune up when I scheduled the chkdsk and had no problems to begin with. I'm glad it worked...thank you very much!

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2015-12-03T23:43:00+00:00

    I saw the same thing, running chkdsk /f /r in Windows 10. Stayed at 14%. I believe everyone when they say it is working, but just out of curiosity I forced a restart and then, because I conveniently have a dual boot system with XP still on another drive, I booted into XP. As it booted, it warned me that the other drive needed to run chkdsk so I let it go. XP shows verbose status which feels better, but it also seems to have run faster than it was in Windows 10. However, that could be perception and not reality as I don't think the chkdsk DOS function is any different between the two OS's.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  5. Anonymous
    2015-07-18T16:15:53+00:00

    Yes, it looked like it was running: the led was flickering, so I guess it was still working, also considering the number of files steadily increasing. Now, admittedly this was a big drive (6TB), but if my calculations are roughly correct, then for a 3TB drive it would take 16 hours and a1TB drive roughly 5-6 hours. Anyway, the message is : take this into consideration prior starting the task... :-)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments