Windows 10: Chkdsk /f /r 100% complete, but on still state 12+hours

Hello Community, After a Q-code A5 on my Mainboard I use the Chkdsk/f /r on Cmd to check my SSD. After the command I restarted my system and the Check up started automatically. The control phase1-5 took around 25-30min and after that I got the "Harddrive C: check and repair: 100%" completed, which is on a still state for 12 hours plus loading sign moving normal all the time Note: Keyboard and mouse don't work cause the system isn't booting, only after the check up, which means I can't use any shortkeysIs this normal or should I start worrying and if yes what solutions can you suggest to sol

:)

 

failure chkdsk /f /r

Early this AM I attempted to update windows version 1607 to version 1703 using the windows update

Good news! The Windows 10 Creators Update is on its way. Want to be one of the first to get it?

Get the Windows 10 May 2021 Update

Download Windows 10

The windows 1703 update failed.

It displayed error code: 0xc19001200

A google search indicated that may be related to an inadequate partition size?

I am a novice with diskpart and entered some commands to view the partition information.

When I was done I typed exit.

Then I typed chkdsk and it displayed errors.

Just a few days earlier I had placed the computer into clean boot.

sfc /scannow and dism restorehealth completed successfully.

chkdsk had displayed no errors.

A chkdsk /f /r scan was ran anyway.

I did not know how to check the log files for each of the chkdsk results in the event viewer.

How could that be done to to provide that information on this post?

After the windows update failure and assessing the diskpart information I again ran chkdsk and it displayed errors.

Chkdsk /f /r was run just now and after it completed it went to the desktop.

Administrative command prompt was opened and chkdsk was run. It is now displaying errors that were not fixed by chkdsk /f /r.

How do you troubleshoot this?

Also earlier this week I had been working with HP on another issue. They sent to me a file to run on my pc. It generated a cab and txt file that I then sent to them for analysis. They found no hardware problems.

The files are not backed up and I have other computers to use but the files are critical on this computer.

This computer had a clean install just a few weeks ago in a Microsoft store. There they had saved the files in a windows pe environment. They formatted the internal hard drive, reinstalled windows 10 version 1607, drivers, files and some applications.
They also had checked the hardware.

These were the diskpart commands and chkdsk earlier in the day (before the chkdsk /f /r repair): Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

This is a onedrive link to the chkdsk after the chkdsk /f /r and reboot to desktop: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

What is happening?

How do you troubleshoot failure of chkdsk /f /r?

How do you upgrade from version 1607 to 1703 with the above error code?

 

chkdsk c: /F

We appreciate the response. I'm referring to Check Disk (chkdsk) utility tool. If you haven't tried yet, we suggest that you run a chkdsk by:

• Press Windows Key + X button to bring up the power user menu.
• In the power user menu, select the Command Prompt (Admin) option.Click Yes when you are presented with a UAC window requesting permission to launch the Command Prompt as Administrator.
• In the new Command Prompt window, type chkdsk E: /f /r /x. Here you should replace E with your drive letter.

This option will run chkdsk to check and repair disk errors in Windows 10. The “/f” parameter tells CHKDSK to fix any errors it finds; “/r” tells it to locate the bad sectors on the drive and recover readable information; “/x” forces the drive to dismount
before the process starts.

Keep us updated with the result.

 

I STILL CANT OPEN MY DRIVE AFTER CHKDSK /R AND /F

before i ask a question about to fix sudden lag occur to my laptop and try every step they suggest. at that time my drive still can be open but taking time.

i chkdsk d: /r and chkdsk d: /f

on command eta say 999:00:00 but i think almost 20-22 hours

it say anything accept this thing:

file verification completed.

deleting orphan file record segment 892E8

deleting orphan file record segment 8BB88

deleting orphan file record segment 8BB89

deleting orphan file record segment 8BB8A

i hope my file can be save , almost has 1 tera of file in there