Helping people with computers... one answer at a time.
CHKDSK is sometimes required to run at boot time, and its display messages disappear when complete. I'll show you where to find them again in Windows.
OK, so CHKDSK ran when my machine rebooted, and displayed some stuff. Problem is I have no idea what it displayed, since it then proceeded to reboot the machine when it was done. How do I get it to stop, pause or otherwise let me see what it did?
•
It's not obvious, I can tell you that.
For a recent article on CHKDSK, I actually carefully timed a few screen shots of CHKDSK running in a virtual machine so as to get the results.
Besides not being useful to the average user, it turns out that's overkill.
Way overkill.
•
As I mention in What does "chkdsk cannot run because the volume is in use by another process" mean?, CHKDSK needs exclusive access to the disk that it's checking if it's been instructed to attempt fixes or repairs. If that disk is your Windows drive (C:), then CHKDSK can't, because Windows will be using that drive simply to run your system.
The solution is to indicate that CHKDSK should run automatically before Windows runs, the next time you reboot your machine.

CHKDSK runs as it normally does, and when it completes it reboots the system.
Which of course causes any progress or results information that had been displayed on-screen to disappear.
While it's not the absolute best of news, there is good news nonetheless.
CHKDSK on boot up saves its results to the Event Log.
Now, as I've also mentioned before the event log is a mess. It's full of random and exceptionally geeky entries that barely have meaning to the people that put them there. (Yes, it's that obscure at times.)
That's not to say it's a waste, it's not - sometimes that obscure and geeky information can be incredibly valuable, as we're about to see.
It's just that most of the time it's so much noise.
After CHKDSK has run, and your machine has rebooted, run the event viewer: hold down the Windows key and press "R", type eventvwr into the resulting Run dialog, and click on OK.

This will fire up the Event Viewer:

This is the Windows 7 Event Viewer; Windows Vista's is similar, while Windows XP's is actually much simpler. While the screen shots may be different the general idea will apply to all three.
Expand the "Windows Logs" on the left (by clicking on the triangle to its left), and click on "Application" below it:

In the event log list that then appears to the right, click on the first item, and then one at a time down-arrow to see each successive event. You're viewing them in reverse-chronological order, most recent first. There will be many that are basically incomprehensible - don't worry about them.
Eventually you'll come to an event who's "Source" is Wininit (Windows Initialization), and whose information displayed in the window below will look very familiar (there may be many other events from Wininit, we're looking for the one that has CHKDSK information in the event information below the list):

The text box within the "General" tab of that information below the event log listing is scroll-able, and contains the entire text of the CHKDSK run that happened at boot time:

You scan scroll up and down in that to view the entire CHKDSK session. If you like you can also select text using your mouse and then type CTRL+C to copy it to the clipboard. (There's surprisingly no right-click option to Copy.) The formatting can be a little odd, but the results you expect - the text that flew by as CHKDSK did its thing on boot, is all there for you to view at your leisure.
Article C4534 - November 7, 2010
I tried this, but I do not find any entry under Source called Wininit in Event Viewer to get to the log file. I'm using Windows XP.
Posted by: James Mowrey at November 11, 2010 7:27 AMUnder Windows XP (I'm using Pro, can't speak for other flavors of XP) the info for CHKDSK is stored in a file called "bootex.log" which is written (and, thereafter, appended to) on the main drive, normally "C:\". All you've gotta do is locate this file and open 'er up in Notepad.
(N.B.: Certain third-party text editors won't open this file properly -- I've found TxEdit v5.5 by Gregory Braun to be notorious for this. Always use Notepad; it's guaranteed to work.)
Posted by: Glenn P. at November 16, 2010 3:16 AM
Posted by: MaxIp at November 19, 2010 7:10 AMRe James. In Windows XP, instead of Wininit look for Winlogon in Event Viewer.
Hi leo; i just want to thank you for the excellent service you and your team run, i'm a novice, but i'm learning your articles are fantastic, well thought out and easy for the novice to begin the bootable journey and many other apps,that no doubt i shall be reading about in the coming months, these thanks i seriously send from a nation of on line users.please keep up the good work team as you are all most definitely needed
Posted by: Patrick at January 11, 2012 5:08 AMI have just run chkdsk but am unable to find wininit. Have MS pulled it or moved/renamed it?
15-Jan-2012