Windows 10: chkdsk report cut off mid-way?

I'm having disc problems and I ran a chhdsk report. The report listed up to "Record 68 of 238: Corrupt File" and then the report cut off half-way through. So I can't see the rest of the 238 files that were affected. It says it repaired the files but in my experience the files are not repaired - they will still be corrupted. So I need to know which files are affected so I can look into this further. Is there any way of me seeing the rest of the report? Why did it cut off?

:)

 

Reviews cut off

Why are reviews cut off in mid-sentence?

The Marketplace (phone version, not PC) doesn't display the full text allowed in writing a review. That means they are often cut off in mid sentence, which makes them pretty worthless and also looks horrible.

How hard is it for Microsoft to be consistent and not truncate the reviews?

 

Windows 10 Mobile Search Is Broken

Some searchs will work. Others it cuts off mid word. The ones it cuts off it does everytime. Batman gets shortened to bat for me too

 

Hello rivre, *Smile

You might see if the complete chkdsk log may be available in Event Viewer.

https://www.tenforums.com/tutorials/4...dows-10-a.html

 

I'm already in the event viewer. A popup came up and says "Your Drive was successfully repaired. The drive is ready to use". And there's a link to "Show Details" That link opens the event viewer for that file. So I'm looking at it and it's cut off where I mentioned. How is this possible? I checked the files it did list and sure enough repair means nothing to Windows. They are all corrupted. So I need to know what these other 170 corrupted files are. They could be anything. Ridiculous.

 

Any reason chkdsk cut off mid-way through the report? Is this normal when there's lots of corrupted files? Whats the point of a report if it's cut off mid-way? It starts listing the files one by one then cuts off mid-way through the list.

 

Does it do it if you run it again?

 

I concur with rivre. My laptop shut itself down while sleeping and on power up was doing chkdsk. Processed few EA records, and then muddled through over 28 thousand reparse records. Good thing I watched the screen - the event log got shut off someplace and therefore could not even show me the subsequent steps such as indexes or sectors which did occur but the screen cleared to quickly to read what it said.
Event log is cut short as well. Useless.

 

If run in a command prompt, it probably got cut off due to the buffer size of the command prompt. Chkdsk does write everything to the Application log in event viewer so everything should be in there.