The chkdsk disk scan report in Windows 10 is stored within the Windows Event Log system, specifically under the Application log category. You can access this information by opening the Event Viewer utility and navigating to the Microsoft-Windows-Chkdsk provider entries. This method allows you to view detailed logs of any file system errors detected or repaired during your last system restart without needing third-party tools.
Accessing the Event Viewer
To locate the chkdsk report, you must first open the Event Viewer application. This tool provides a centralized interface for monitoring system events, including those generated by disk checking utilities. There are several ways to launch this utility, but the most direct method involves using the Run dialog box. Press the
Windows Key + R simultaneously to open the Run window. Type
eventvwr.msc into the text field and press Enter. This command immediately launches the Event Viewer console, providing you with a hierarchical view of all system logs. Alternatively, you can right-click the Start button and select Event Viewer from the context menu, or search for "Event Viewer" in the taskbar search box. Once the application is open, you will see a tree structure on the left side containing various log categories.
Navigating to the Correct Log Category
After launching the Event Viewer, you need to navigate to the specific location where chkdsk stores its results. The default behavior of Windows is to write these reports to the Application log rather than the System log, which is a common point of confusion for users expecting to find them elsewhere. Expand the
Windows Logs folder in the left-hand navigation pane. Click on the
Application node to display its contents in the central pane. By default, this list may be crowded with thousands of entries from various applications. To filter these effectively, you should use the Actions pane located on the right side of the window. Click on
Filter Current View... to open the filtering dialog. In the field labeled "
All Event Sources", type
Microsoft-Windows-Chkdsk. This ensures that only events generated by the disk check utility are displayed. Click OK to apply the filter. You should now see a list of events related to chkdsk operations.
Interpreting the Chkdsk Events
The filtered list typically contains multiple entries corresponding to different stages of the disk check process. Look for events with an
Error level, as these indicate critical issues found during the scan. An event ID of
262 usually signifies that chkdsk has started running, while event ID
263 often indicates that it has completed successfully. If there were errors, you might see event ID
264 or higher numbers depending on the severity. Double-click any of these entries to open the event properties window. Here, you will find a detailed description of the actions taken by chkdsk, such as correcting index errors, fixing security descriptors, or recovering lost clusters. Pay close attention to the "General" tab for a summary of the findings and the "Details" tab for raw XML data if you need to parse specific error codes programmatically.
Alternative Methods for Viewing Reports
While the Event Viewer is the standard method, some users prefer command-line approaches for automation or remote management. You can use PowerShell to retrieve similar information. Open PowerShell as an administrator and run the command
Get-EventLog -LogName Application -Source Microsoft-Windows-Chkdsk. This returns a list of recent chkdsk events directly in the console output. For a more concise view, you can pipe the output to format-table to display only the TimeGenerated and Message columns. Another alternative is checking the
C:\Windows\System32\winevt\Logs directory for raw log files, though these are binary formatted and not human-readable without specialized tools. Additionally, if chkdsk was run on the system drive during boot, the results might be briefly displayed on the screen before Windows loads the desktop environment. If you missed this screen, the Event Viewer remains the definitive source for historical data.
For more information on managing system processes after a reboot, you may want to review our guide on how to
restart a Windows GUI app after system restart. If you are experiencing broader boot issues alongside disk errors, consider reading our article on
fixing Windows boot issues, which covers scenarios involving missing drives and driver conflicts.
Frequently Asked Questions
Why can't I find the chkdsk report in the System log?
Windows intentionally routes chkdsk results to the Application log by default, not the System log. This design choice separates file system metadata updates from core kernel events. Always check the Application log first when looking for disk check summaries.
What does Event ID 262 mean in the chkdsk log?
Event ID 262 indicates that the chkdsk utility has successfully started its operation on a volume. It serves as a timestamp marker for the beginning of the scan process. You will typically see this event followed by completion or error events shortly after.
Can I export the chkdsk report to a text file?
Yes, you can export events from the Event Viewer by right-clicking the filtered view and selecting "Save All Events As...". Choose the EVTX format for future reference or CSV for spreadsheet analysis. This allows you to share logs with technical support teams easily.
Does chkdsk create a separate text file like C:\Windows\System32\LogFiles\ChkDsk?
On modern versions of Windows 10, chkdsk primarily uses the Event Log system instead of creating standalone text files in the LogFiles directory. Older versions of Windows relied heavily on these text files, but the current architecture favors the structured Event Viewer approach. Check the Event Viewer for the most accurate and up-to-date records.
What should I do if the chkdsk log shows severe errors?
If the log reports severe corruption, back up your important data immediately before attempting repairs. Use the
chkdsk /f command in an elevated command prompt to allow Windows to fix logical file system errors automatically. For physical bad sectors, consider replacing the hard drive if the error count continues to rise.