There's a lot that happens within the Windows 10 operating system, the majority of which runs In the background unbeknownst to you. Things like troubleshooting potential problems, detecting and fixing Issues and so forth, are (for the most part) automated by the OS, namely It's "troubleshooter" utility. A history of It's details Is stored, and In this tutorial, I will show you how to access and view the troubleshooting history on your PC.
Whether you perform troubleshooting diagnostics via your own accord natively within Windows, or the operating system does It on a scheduled basis In the background, log files are stored to some extent In the form of a Troubleshooting report. This can significantly help to Identify what went wrong at a given point In time.
I will demonstrate exactly how to access the Troubleshooting history stored by Windows 10, and view the report thereafter. So without further delay, let's rip Into this tutorial.
Firstly, you need to navigate to Control Panel. Open the Run menu, enter control panel and hit OK.
Next, select Large Icons via the drop-down menu, and then click on Troubleshooting as arrowed below.
To the left of the window, click on the View history link.
In order to see a more detailed list, click on Include troubleshooters that were run as an administrator as Illustrated below.
Click the View details tab, and you will then see a number of entries. Select those according to your needs. For the purpose of this tutorial, I've chosen Internet Connections, by right-clicking It and hitting View details.
As you can see In the Image below, a number of Issues have been detected and logged. I'd like to know more about this, so I've clicked the Detection details link.
You can see the timestamp of when the error occurred, which can help to Identify the cause, by retracing your steps. What's of Interest, Is the Network Configuration.cab file. Let's check It out.
Here's a snippet of the Troubleshooting history report. It lists exactly what was affected by the Issue, which was my Wireless LAN adapter.
As opposed to another native Windows utility named Event Viewer, that also logs Issues and Is rather difficult to Interpret even by advanced users, the Troubleshooting History Is quite the opposite. Once you begin using It and view the details contained In the log files, you'll find that a lot of It Is self-explanatory. Do make a mental note to check It on a regular basis.