Win 10 2004 chkdsk stuck on 100%

I have run chkdsk as admin as I thought I may have some network file errors.

It ran OK and now is stuck displaying "scanning and repairing drive (C:): 100%

How should this be fixed please

|

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Hi Phil

I am Dave, an Independent Advisor, I will help you with this . . .

if that disk checking has completed to 100%, then if you cannot interact with your PC, press and hold the power button on your PC for 5 - 10 seconds to perform a hard shut down

Wait a few seconds, then start your PC again . . .
___________________________________________________________________

Power to the Developer!

MSI GV72 - 17.3", i7-8750H (Hex Core), 32GB DDR4, 4GB GeForce GTX 1050 Ti, 256GB NVMe M2, 2TB HDD

4 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I've the same problem.

My O.S. is Windows 10 PRO version 2004 build 19041.508.
From "Windows PowerShell (administrator)" I ran the command: chkdsk c: /f /r /spotfix
Since this is unit "C", the check is performed on restart.
So, I restart my computer, but the disk check process, after phase 5, remains in the "Scanning and repairing drive (C:) 100% complete" state.
I found the same problem in two different computers, however, both having Samsung SSD disks (although different models).

Any suggestions?

Thanks!

"Facesti come quei che va di notte, che porta il lume dietro e sé non giova, ma dopo sé fa le persone dotte"
Dante (Purgatorio, Canto XXII)

5 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

(correction) Try run chkdsk /f from Command prompt mode (Shift+restart).

In my opinion, due to some error, it is not possible to end the command correctly, therefore it stuck on 100%.


1. Go to safe mode: 

https://support.microsoft.com/en-us/help/12376/windows-10-start-your-pc-in-safe-mode

1. (correction) Go to Command prompt mode through Shift+restart

2. (correction) Check the correct letter of your system boot HDD, because in this Command prompt mode the letters of the HDD are different ( c: Enter , dir Enter, d: Enter, dir Enter, e: Enter, dir Enter ...etc.)

3. Run the command for correct letter of your system boot HDD , for example chkdsk e: /f

4. Make sure the command doesn't end with an error message. If it reports an error, search it on google, microsoft...etc.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi, thanks for your reply!
My two SSD drives seem to have no problems anyway.
I try to explain myself.
When the process stuck at 100%, I have to reboot (or shut down) the computer brutally (= manually). Once restarted, I check the Windows Event Viewer, in particular under Wininit, to verify anyway the results of the chkdsk: everything is regular and no problem is detected or needs corrections.
I'll try from safe mode anyway.
Even after the
October monthly update the problem persists in two of the three computers at my disposal ... (both having Samsung SSD disks).

Cheers!

"Facesti come quei che va di notte, che porta il lume dietro e sé non giova, ma dopo sé fa le persone dotte"
Dante (Purgatorio, Canto XXII)

4 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

(correction) Try it from Command prompt mode and attach the results list. I have experience that we will learn more about the problem.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Sorry for delay!

Here is the result from scanning in safe mode:

>

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.                        

Stage 1: Examining basic file system structure ...
  873216 file records processed.                                                        
File verification completed.
 Phase duration (File record verification): 13.42 seconds.
  13324 large file records processed.                                   
 Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.                                     
 Phase duration (Bad file record checking): 1.53 milliseconds.

Stage 2: Examining file name linkage ...
  377 reparse records processed.                                      
  1088956 index entries processed.                                                       
Index verification completed.
 Phase duration (Index verification): 31.93 seconds.
  0 unindexed files scanned.                                        
 Phase duration (Orphan reconnection): 6.02 seconds.
  0 unindexed files recovered to lost and found.                    
 Phase duration (Orphan recovery to lost and found): 3.43 milliseconds.
  377 reparse records processed.                                      
 Phase duration (Reparse point and Object ID verification): 31.25 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 15 unused index entries from index $SII of file 0x9.
Cleaning up 15 unused index entries from index $SDH of file 0x9.
Cleaning up 15 unused security descriptors.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 74.02 milliseconds.
  107871 data files processed.                                           
 Phase duration (Data attribute verification): 1.77 milliseconds.
CHKDSK is verifying Usn Journal...
  36408016 USN bytes processed.                                                           
Usn Journal verification completed.
 Phase duration (USN journal verification): 255.20 milliseconds.

Stage 4: Looking for bad clusters in user file data ...
  873200 files processed.                                                               
File data verification completed.
 Phase duration (User file recovery): 8.76 minutes.

Stage 5: Looking for bad, free clusters ...
  13644285 free clusters processed.                                                       
Free space verification is complete.
 Phase duration (Free space recovery): 0.00 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

 157291489 KB total disk space.
 101382380 KB in 515149 files.
    347656 KB in 107872 indexes.
         0 KB in bad sectors.
    984313 KB in use by the system.
     65536 KB occupied by the log file.
  54577140 KB available on disk.

      4096 bytes in each allocation unit.
  39322872 total allocation units on disk.
  13644285 allocation units available on disk.
Total duration: 9.63 minutes (577950 ms).

Internal Info:
00 53 0d 00 a9 80 09 00 3b 1d 12 00 00 00 00 00  .S......;.......
06 01 00 00 73 00 00 00 00 00 00 00 00 00 00 00  ....s...........

Windows has finished checking your disk.
Please wait while your computer restarts.

<

"Facesti come quei che va di notte, che porta il lume dietro e sé non giova, ma dopo sé fa le persone dotte"
Dante (Purgatorio, Canto XXII)

2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Try it from Safe mode and attach the results list. I have experience that we will learn more about the problem.
Hi I'm experiencing the same issue. Samnsung SSD + October update.
Running chkdsk from safe mode ask anyway to reboot, and stuck at the end to 100%. THe only way is brutaly shutdown and restart

4 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

ATTENTION, I wrote it wrong, not through Safe Mode but through Command prompt! It is not the same.

Forgive me everyone.  I send the photo....You get there via Shift + restart.

Keep in mind, drive C: in this Command prompt mode not the same as normal boot drive C: ! After restarting into this Command prompt, the letters of the drives are usually shifted.  The right normal booting system drive letter C: is one of these ->  D: E: F: G: H: I: or X: Y: Z: , it depends on how many disks and partitions are created in the system.
Try running chkdsk / f in Command prompt mode for all possible drives sequentially .. for example chkdsk d: / f, chkdsk e: / f, chkdsk f: / f, chkdsk g: / f, chkdsk h: / f, chkdsk i: / f,  chkdsk x: / f, chkdsk y: / f, chkdsk z: / f. Feel free to go through the whole alphabet, because various hidden partitions will behave like drives in this Command prompt mode.

Look for the error at the end of the listing. If you find an error message ("not possible", "warning"...etc.), attach the print screen. I hope, You can find the bug.

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

ATTENTION, I wrote it wrong, not through Safe Mode but through Command prompt! It is not the same.

Forgive me everyone.  I send the photo....You get there via Shift + restart.

Keep in mind, drive C: in this Command prompt mode not the same as normal boot drive C: ! After restarting into this Command prompt, the letters of the drives are usually shifted.  The right normal booting system drive letter C: is one of these ->  D: E: F: G: H: I: or X: Y: Z: , it depends on how many disks and partitions are created in the system.
Try running chkdsk / f in Command prompt mode for all possible drives sequentially .. for example chkdsk d: / f, chkdsk e: / f, chkdsk f: / f, chkdsk g: / f, chkdsk h: / f, chkdsk i: / f,  chkdsk x: / f, chkdsk y: / f, chkdsk z: / f. Feel free to go through the whole alphabet, because various hidden partitions will behave like drives in this Command prompt mode.

Look for the error at the end of the listing. If you find an error message ("not possible", "warning"...etc.), attach the print screen. I hope, You can find the bug.

Thank for the details.
I confirm that from command prompt chkdsk /f worked properly, no error found on the partition, the last message is:

" Failed to transfer logged messages to the event log with status 6."

Do you have any other suggestion?


Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

"Failed" is error. 

Congratulations!  You found a Bug ... exactly as I expected.

Therefore, the Windows can't restart the system after 100% of chkdsk command,  because it didn't end by normal status, but with this error.

Confirm all of you, who has this problem, that chkdsk /f (procedure as described above!!!) reports the same error:

" Failed to transfer logged messages to the event log with status 6."

...and when that is true, send this error to Microsoft to have it resolved as soon as possible.

Nice to meet you and have a nice day ! :)


2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated July 24, 2021 Views 10,054 Applies to: