Win 10 2004 chkdsk stuck on 100%

Anonymous
2020-09-09T18:19:27+00:00

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

Windows for home | Windows 10 | Performance and system failures

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.

0 comments
Answer accepted by question author
DaveM121 936.3K Reputation points Independent Advisor
2020-09-09T18:22:40+00:00

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 . . .

Was this answer helpful?

20+ people found this answer helpful.
0 comments

40 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2021-07-15T18:31:32+00:00

    chkntfs /T0

    chkdsk /f c:

    shutdown -r -t 0 or shutdown -s -t 0 no difference all are stuck at 100%, though no error detected.

    Eventvwr.msc shows no error on chkdsk results.

    sfc /scannow returns no error all are fine

    DISKPART> sel disk 0

    DISKPART> list disk

    Disk ### Status Size Free Dyn Gpt

    * Disk 0 Online 465 GB 0 B *

    DISKPART> list part

    Partition ### Type Size Offset

    Partition 1 System 260 MB 1024 KB

    Partition 2 Reserved 16 MB 261 MB

    Partition 3 Primary 464 GB 277 MB

    Partition 4 Recovery 1000 MB 464 GB

    DISKPART> list vol

    Volume ### Ltr Label Fs Type Size Status Info

    Volume 0 C Windows NTFS Partition 464 GB Healthy Boot

    Volume 1 SYSTEM FAT32 Partition 260 MB Healthy System

    Volume 2 WinRE_DRV NTFS Partition 1000 MB Healthy Hidden

    System: Lenovo Thinkpad X260

    SSD Samsung 850 EVO 500GB (SATA/AHCI)

    GPT partition no MBR.

    Boot EFI only/Secureboot enabled.

    CMDver: 10.0.19043.1110

    Winver: 21H1/19043.1110

    Windows 10 PRO x64 (64 bit)

    Windows Feature Experience Pack 120.2212.3530.0

    RAM: 16,0 GB (15,9 GB usable)

    CPU: Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz 2.81 GHz

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-09-02T13:01:59+00:00

    "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 ! :)

    I experience the same symptoms when running chkdsk on boot/reboot and receive the same error on my system (which is definitely not a Lenovo laptop). I'm running Windows 10 Pro - 64-bit (21H1).

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  3. Anonymous
    2021-09-14T03:40:57+00:00

    Same problem on:

    • Beelink AP34 mini PC (Win 10 Home 20H2)
    • Beelink Gemini T45 mini PC (Win 10 Home 20H2)

    When will Microsoft take care of this problem?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2021-09-26T08:20:03+00:00

    Still happening to me on a Lenovo thinkpad T460 running windows 10 pro 64 with everything up to date (21H1) on an Intel SSD 520 series.

    The main reason I chose to run chkdsk command is just to retry deleting the stubborn folder “windows.old”

    Although ZB1973’s method ended up with a successful scan yet with the same error message reported by Runner973:

    “Failed to transfer logged messages to the event log with status 6”

    This is getting a bit longer than expected!

    Was this answer helpful?

    0 comments