Windows file check log

A quick Find in notepad will take you to every occurrence and will display the path and file name of the one in question.

Repairing is very old school, go to another computer of the same version that's working and copy the file from there : make backups of the originals before you replace anything as usual. Home How-tos. System File Check - reading the logs. Mac Mad This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. Last Updated: Oct 18, 3 Minute Read. Reply 0.

Facebook Twitter Reddit LinkedIn. Kevin Billington This person is a verified professional. Main Areas of Contribution:. In the Event Viewer , navigate through the various categories called Views in the left-hand navigation pane in order to inspect the various events in the main section of the screen. You can adjust your filter criteria until you find what you were looking for. For quicker access to particular types of logs, click or tap on Create Custom View.

Enter your criteria and confirm. In order to export some of the logs for external diagnostics, make your selection in the list, then hit Save selected events….

If your computer is giving you a hard time with persistent crashes and the like, you may need to perform some repairs. Start by repairing the file system see below. If that fails to resolve the issue, you can try and restore the boot directory. A major cause of persistent crashes, BSoD incidents and other malfunctions comes down to hardware defects due to faulty manufacturing, overheating or rough handling.

The system or its individual components may overheat during prolonged use, particularly when overclocking. Before the iron melts on you, adding or replacing case fans and coolers can save you real money. Adding fans to cool memory banks or fitting the system with liquid cooling can not only prevent damage—it can also improve performance. Hardware damage due to overheating tends to be pretty irreversible so that no amount of passive or active cooling will make the crashes go away.

To do this, run the following command instead:. The scan results will be shown after this process is finished. This means that you do not have any missing or corrupted system files. Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS. To view the detail information about the system file scan and restoration, go to How to view details of the System File Checker process.

Windows Resource Protection found corrupt files but was unable to fix some of them. To repair the corrupted files manually, view details of the System File Checker process to find the corrupted file, and then manually replace the corrupted file with a known good copy of the file. Swipe in from the right edge of the screen, and then tap Search.

Or, if you are using a mouse, point to the lower-right corner of the screen, and then click Search. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow. To do this, click Start , type Command Prompt or cmd in the Search box, right-click Command Prompt , and then click Run as administrator.

To view the details that included in the CBS. Log file, you can copy the information to the Sfcdetails. To do this, follow these steps:. Note The Sfcdetails.

The file includes information about files that were not repaired by the System File Checker tool. Verify the date and time entries to determine the problem files that were found the last time that you ran the System File Checker tool. How to manually replace a corrupted system file with a known good copy of the file.