Windows 10: In run as administer I ran chkdsk /r This is what iI found . Did it correct anything?

Should I have run chkdsk /f/r/x ?Is there any risk in disconnecting the drive with /X ?When it disconnects the drive, how long is it disconnected.Will the computer start up without having to do anything else.I'm doing this now before I copy to a new SSD.Does this screenshot tell you anything

:)

 

Problem running chkdsk /R

I have been having problems with installing some updates on my laptop so I tried to run a system restore. The system restore was not successful, it said my drive might be corrupt and suggested that I run chkdsk /R. I ran it from Command Prompt Administration
but it hung up at 12 percent complete. Can I stop the scan or ? Thank you.

 

Windows 10 hangs at 13% after running CHKDSK /R

I've tried some additional things but still not able to get past 13%.

I entered wmic, and ran "diskdrive get status" and received the reply that the diskdrive was ok

I ran Dism /Online /Cleanup-Image /RestoreHealth and this completed successfully

I ran a complete Spybot scan on my computer and found no malware.

Then I ran Chkdsk /R again and it still stops at 13%, and never gets past that no matter how many hours I wait.

Does anyone have any other suggestions, short of replacing the hard drive?

 

Windows 10 hangs at 13% after running CHKDSK /R

The computer IS almost 5 years old, first of all. Running the chkdsk repair was kind of a last resort. When the problems started (system getting slower and slower, freezing), I first did all standard stuff (checked for viruses/malware, defragged, got rid of bloatware, removed almost everything from startup, ran SFC /scannow, took it back to a previous restore point, DISM /Online /Cleanup-image /RestoreHealth), and finally did a complete reset of Windows taking it back to when Windows 10 was first installed. The problems continued. I ran wmic/diskdrive get status and was told the drive was OK. I ran tests on the battery, was told it was OK, and ran the laptop with no battery. I ran complete tests on the RAM (which was bought new 5 months ago) and it passed all the tests. I ran chkdsk /scan and it did not find any issues, then ran chkdsk /spotfix which breezed thorugh quickly. Ran sfc /scannow again, and it did find 20 bad sectors on the drive, but detected no other problems. Ran tests on the processor, no problems. Updated the bios. So I was trying to run chkdsk /r as a last resort.... The fact that it stops at 13% seems telling that there is indeed a problem, but for the life of me I can't figure out what the problem could be.