Need to make sure about chkdsk issue


Jul 18, 2016

As you can see, i ran chkdsk /r on hard drive which got some bad sectors and this is screenshot for last moment before i stopped chkdsk. i canceled chkdsk after ran some minutes because i heard run chkdsk /r on hard drive with bad sectors can lose data.

So according to this chkdsk prompt window screenshot, was that possible about that data was removed/fixed or anything changed by chkdsk? i am asking about that chkdsk could do something to data even no errors are found on prompt window.

Actually i already posted same issue about another drive on here and took answer already, and MS support engineer gave same answer.

"From the above description I understand that you were able to cancel the chkdsk program within 3%. usually chkdsk command examine all the files and then start the fixes. However in this case you wouldn’t have lost any data."

So, i thought i need verify that answers i got, so i have additional question now.

My question is...

"If chkdsk finds error/corrupted/any kind of problem while running, is it strictly + immediately shows messages on prompt window? or possible to miss to show messages on window about what chkdsk did to data?"

I think answer should be like yes or no - simply, please help. thanks.


Oct 16, 2014
When chkdsk finds a bad sector, it momentarily flashes a message like "recovering sector xxxx" while in stage 4. Did you see a message like this? If not, then your data has not been altered. If yes, then:
1> if chkdsk managed to somehow read the data from the bad block then again your data is safe. chkdsk moved the data to a spare sector and marked the failing sector as BAD to prevent future access.
2> if chkdsk could not read the data in the failing sector even after multiple attempts, it will give up and simply mark the sector as BAD without copying the data to somewhere else. In this case, your data is lost.

It's not a bright idea to try to find bad sectors with chkdsk (my personal opinion). If you suspect bad sectors, the FIRST thing you do is backup your data over to an external drive or some cloud storage solution. Next you install the drive manufacturer's test tool (if it's a WD drive you install WD data lifeguard. If it's a Seagate drive, you install SeaTools for Windows, etc), and run an extended test on the drive.


Jul 18, 2016

I just found these messages about stage 4 on chkdsk from somebody's log.

Stage 4: Looking for bad clusters in user file data ...
Windows replaced bad clusters in file 2813
of name $PATH1.MKV.
Windows replaced bad clusters in file 2863
of name $PATH2.MKV.
Windows replaced bad clusters in file 2881
of name $PATH3.MKV.
Windows replaced bad clusters in file 2891
of name $PATH4.MKV.


Stage 4: Looking for bad clusters in user file data ...
Read failure with status 0xc0000185 at offset 0xb2b4000 for 0x10000 bytes.
A disk read error occurredc0000185
The disk does not have enough space to replace bad clusters
detected in file 73702 of name \PROGRA~1\WI7DB9~1\MIE81F~1.0_X\MRT100~1.DLL.

These messages are not about my case, i wonder these messages are messages that you mean "recovering sector xxxx" or you mean another kind of messages?

Any messages like these are not written on my chkdsk prompt window but i do not remember some message was 'momentarily flashes' on chkdsk prompt window while chkdsk was running.

Then is it impossible to know about that - was data already touched by chkdsk or it is not happened in my case?