It takes a long long time especially when running on a larger USB external drive...
Had to stop it as well.
Estimated it would take roughly 32 hours or so...
=
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
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.
It takes a long long time especially when running on a larger USB external drive...
Had to stop it as well.
Estimated it would take roughly 32 hours or so...
=
Is the disklamp lightning constantly, when "Running" the chkdsk /r ? If yes, I think, it's working on it! Do you remember, when checking XP? The checking of the files didn't take very long time, but checking the EMPTY space....... YAWN!
I have a 1 TB harddisk, and there is "only" about 109 GB files on it - a chkdsk /r took over 1 hour - I have 8 GB RAM. It was also "Stucked" on the 11%, but I let it "run", because of the disklamp's constantly lightning... And it restarted normally, when finiched the check.
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... :-)
Or try chkdsk /F /R!!! HA-HA......
Well,
My chkdsk on my Windows 10 machine is stuck at 11%. If it is working then this is yet another incredibly poor Microsoft software design. How does this company survive putting out such **** year in and year out???!!!