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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2016-06-26T13:18:56+00:00

    The scan and repair facility on Windows 8, 8.1 and 10 is utter garbage.

    Since buying a laptop (with Win 8 installed) over 3 years ago, I've suffered endless crashes.

    I really thought Microsoft would have ironed out all the bugs by now, so I finally took the plunge and "upgraded" to the wondrous Windows 10 a month ago - following yet another terminal 8.1 failure.

    What a mistake - this carp OS has now crashed for the second time!

    I have had previous problems with the scan/repair facility. It is unreliable and takes forever. It gets to "11% complete" fairly quickly, then the spinning wheel irritatingly whirrs away for hours on end.

    I must say that the only advantage of Windows 10 is the startup time - it was taking at least 5 minutes with 8.1.

    But it is equally unstable and now I have regular blue screens, indicating all manner of drive C errors. I can't even use "system restore" (which used to work brilliantly with XP) until I've run the scan/repair - which, of course, doesn't work.

    Thank you so much, Microsoft, for wasting hours of my life. If you can propose a proper solution, please advise.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  2. Anonymous
    2016-07-28T01:36:38+00:00

    My friend's Inspiron 14, 6 month old, was booting to windows for more than 5 minutes and takes almost same amount of time to go to the desktop and the same time before you can open any program. 

    I run CHKDSK /F /R and after 11 hours it was still stuck in 11%. I click on CTRL+SHFT+DEL and it went to "Scanning and repairing drive (C:): 100% complete but stuck there now for 10 minutes. 

    Should I hard reboot it already or should I wait?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2016-07-28T07:12:59+00:00

    You might have to wait for 72 hours, according to www.win8forums.com/threads/bsod-chkdsk-f-r-stuck-at-10.1369/

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-07-28T07:18:52+00:00

    Thank you. I restarted it because I cannot wait longer and did a SFC /scannow instead when it allowed me to boot to the desktop (after 30 minutes of waiting). Now it is running faster but haven't tried rebooting again though.

    Was this answer helpful?

    0 comments
  5. 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