Checking disk (chkdsk) stuck at 13% for 8-9hrs and doing nothing.

Feb 15, 2018
3
0
10
So i reinstalled windows 10, downloaded all drivers blah blah blah and i saw my disk usage was on 99-100% so i went to google it and tried to solve this problem, so there is a thing named chkdsk, when you write one command in cmd then you have to reboot computer to start checking and repairing computer, so i did it and now my computer saying: Scanning and repairing drive (C:) 13% complete. And that 13% is like 8-9 hours not moving, not doing anything. I want to ask is it normal or not?
Sorry if i made writing mistakes. :/
P.S
Windows 10 (64bit);
Intel Core i5-3210M;
nVidia 630M;
4RAM.
 
Solution
not normal. power off and try again, alternatively, you can try something like CrystalDiskInfo to see if your HDD's SMART info says anything is out of order.

I assure you that is perfectly normal. CHKDSK often freezes at a certain percentage, especially in Windows 8 and later when it doesn't tell you what it's doing because thank you Microsoft.

Also note: CHKDSK will not fix your drive being 99% full (a bigger hard drive will fix that permanently, or for a temporary fix clear your temp files, downloads etc.) All CHKDSK does is make sure all your files and folders are on the drive where Windows thinks they are, and if they're not it finds them and moves them back, which is what takes forever. Use it if you get strange errors when you try opening a few specific files on your hard drive.

CHKDSK getting stuck CERTAINLY does not mean your drive is bad.
 
So i reinstalled windows 10, downloaded all drivers blah blah blah and i saw my disk usage was on 99-100% so i went to google it and tried to solve this problem, so there is a thing named chkdsk, when you write one command in cmd then you have to reboot computer to start checking and repairing computer, so i did it and now my computer saying: Scanning and repairing drive (C:) 13% complete. And that 13% is like 8-9 hours not moving, not doing anything. I want to ask is it normal or not?
Sorry if i made writing mistakes. :/
P.S
Windows 10 (64bit);
Intel Core i5-3210M;
nVidia 630M;
4RAM.
Just had this issue on a nano SD card; reomving the card and then letting windows try to fix the drive actually worked for me.