Scanning and Repairing Drive C 100% Complete - STUCK

JFC15 · 22 Nov 2016

When my computer does a chkdsk /r, and restarts, the scan will get stuck on 100%. I've let it sit for over 16 hours and it stays stuck. If I hit the reset button, it''ll restart, the Scanning and Repairing Drive C 100% Complete momentarily comes up, but then it moves forward and boots up to my desktop. I see this is a known problem and have tried several different so called solutions I've found on the internet to no avail. Can anyone help me?

dalchina · 23 Nov 2016

CHKDSK is stuck after 48 hours. Is this a problem?
http://www.thewindowsclub.com/chkdsk...-hangs-windows

I would start panicking in a controlled manner, thinking, 'Have I got proper backups?' 'Have I got a current disk image that will let me relatively quickly and easily transfer my whole working environment to a new disk rather than clean installing?' (e.g. using Macrium Reflect (free) ).

Other ideas:
Check your SMART parameters - e.g. Crystal Diskinfo (free)
Run Macrorit Diskscanner - surface scan (free)

JFC15 · 25 Nov 2016

I've done hard drive checks and mine comes back OK. I've installed Acronis Drive Monitor and Chrystal Disk Info and both programs say that the hard drive is Good. I don't have a problem buying another hard drive if that what is necessary. I just don't want to waste my time and money to find out that replacing the hard drive wasn't the answer. I ran a Window's Recovery Environment and everything was OK. I even ran the DISM Tool and found nothing wrong. Any ideas what to do next?

dalchina · 26 Nov 2016

You can get you can get chkdsk results after a restart as follows:
How do I see the results of a CHKDSK that ran on boot? - Ask Leo!
- if that tells you any more than you know about your current attempts.

Have you tried this?
Run Macrorit Diskscanner - surface scan (free)

You could try running chkdsk offline... e.g. boot from a Win 10 install medium, navigate to a command prompt and try that way.

You'll have seen the standard recommendation is to leave it running... but...

JFC15 · 26 Nov 2016

OK... I went in and checked the results of a CHKDSK. The only thing that I could see that was puzzling was that I saw this:

WARNING! /F parameter not specified.

So I did this check...

Scanning and Repairing Drive C 100% Complete - STUCK-2016_11_26_14_50_051.png

F: is a DVD drive as is E:

You can see that they come up differently and I'm not sure why a DVD drive would come up as NTFS.

Could the CHKDSK be hanging up due to CHKDSK seeing the F: as NTFS?

My Computer shows it correctly:

Scanning and Repairing Drive C 100% Complete - STUCK-2016_11_26_15_01_472.png

I went into Computer Management and everything looks good too.

Scanning and Repairing Drive C 100% Complete - STUCK-2016_11_26_15_18_432.png

--------------------------------

I ran Macrorit Diskscanner on my c: and it came back as fine, no damage. (100% good)

The only issue that I know about my c: is that when I first purchased it, it had 1 bad block. When I contacted the manufacturer, they stated that 1 bad block is OK. I have had the SSD for a few years now and never had an issue with it. the bad block does come up in Acronis Drive Monitor under Reallocated Sectors Count as Degradation, but the health is good at 98%.

I did check the drive in CrystalDiskInfo as you requested and here is a screen shot:

Scanning and Repairing Drive C 100% Complete - STUCK-2016_11_26_15_26_151.png

BTW, I appreciate that you are trying to help me figure this out. When my computer has issues, it bugs the crap out of me until I can figure out how to resolve the issue. So, thank you.

dalchina · 26 Nov 2016

Hi, I think you're confusing option /F with drive F: - if you try
chkdsk /?

you will see the options.

Standard recommendation for C: is
chkdsk C: /F
from an admin command prompt.
=> prompt for restart.

Good that your physical drive is ok.

JFC15 · 26 Nov 2016

Hello... Yes, that was my mistake.

So, is there anything that I can do to fix this issue or will I just have to go into the registry and stop the CHKDSK from starting during boot up? I'd rather fix it so the computer is running properly.

dalchina · 26 Nov 2016

You could try running chkdsk offline... e.g. boot from a Win 10 install medium, navigate to a command prompt and try that way.

- and use the appropriate parameters.

And you could try using it in scan mode only and see if that completes.

Whether chkdsk runs or not depends on the 'dirty bit'.
Fsutil: dirty

No need to do anything in the registry.

JFC15 · 26 Nov 2016

I already ran fsutil: dirty and it came back that it was not dirty.

I'm not sure how to

You could try running chkdsk offline... e.g. boot from a Win 10 install medium, navigate to a command prompt and try that way.

- and use the appropriate parameters.

And you could try using it in scan mode only and see if that completes.

dalchina · 26 Nov 2016

If you want to get to a command prompt outside Windows (= Windows not running, permissions issues don't apply) then e.g.

SHIFT + left click Restart and work through the prompts.

Tutorial section (do have a look- many very useful and practical guides)
Command Prompt at Boot - Open in Windows 10 - Windows 10 Forums