I've ran chkdsk /r /f, it also was stuck at 11%. I just let it ran over night and the computer is back operational this morning.
BUG: CHKDSK stuck at 11% for hours, but was actually working
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.
66 answers
Sort by: Oldest
-
Anonymous
2014-12-07T14:35:33+00:00 -
Anonymous
2015-01-18T18:01:04+00:00 I've ran chkdsk /r /f, it also was stuck at 11%. I just let it ran over night and the computer is back operational this morning.
Lucky guy. My system has been running very slowly lately, typically a sign of a corrupt file or database on the drive and running chkdsk /f sometimes fixes it. I've noticed that if chkds /f doesn't fix it, chkdsk /r will. I currently have no "bad" sectors on my drive therefore this is either a software issue or at times a power (a/c or batter) loss issue if power runs out before a hibernate feature completes.
Anyway I my system has been running slowly lately and I ran a chkdsk /r command and let the system run over night. The next morning I awoke to the system reporting 11% complete. I went about my day and left the house until 10 p.m. The system was still at 11%. over 24 hours on a 1 TB drive? I'm certain something is wrong with the coding of chkdsk if it remains at the same percent complete for close to 24 hours. After waiting that long, I forced a power down and restarted the system. After about 5 minutes it was back at 11% and appeared to stand still. After waiting another hour I forced another power down, used the boots option menu and booted into Windows 8.1. The OS is running smoother as expected after a completed chkdsk, so something was apparently fixed but why literally over a day? I feel as LironL pointed out that either the status isn't updating correctly and that having a detailed screen would be reassuring if not helpful.
-
Anonymous
2015-02-14T22:48:32+00:00 I am using chkdsk \r and it keeps getting stuck on ll% will it go on or is is stalled kr corrupt
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more