# Troubleshooting your computer


This utility scans the system for issues with the Windows Component Store and WinSxS folder. When there is a file that needs repair, it uses Windows Update to download clean versions of those files.

To scan and repair those files, run DISM /Online /Cleanup-Image /RestoreHealth from an elevated command prompt.

For more information about running DISM check this page (opens new window)


This utility scans the system for corruption in the system files which may be responsible for irregular operating system behaviour.

To run SFC, from am elevated command prompt run sfc /scannow. It is recommend to do this after running DISM, to correct any issue with the Component Store before trying to repair the System32 folder.

For more information about SFC, check this page (opens new window)


This utility returns the IP configuration of your machine. If the IPv4 address begins with 169.254 it is considered as an APIPA address, and the network card is unable to retrieve an IP address from the DHCP server. Use ipconfig /release and ipconfig /renew in a command prompt to attempt retrieval of an IP address, otherwise check the DNS settings and drivers in Device Manager.

# Device Manager

When troubleshooting problems with your audio, video outputs or a device you connect into your system you should make sure to check that the drivers for them are properly installed on your system. If your system has recently updated them and they no longer function as desired, you can always roll back the drivers by right clicking the device in Device Manager, going to its Properties > Drivers tab and then clicking Roll Back Driver. If this still does not work well, you may wish to uninstall the drivers and then reboot the system. If you do not see drivers for your device in this utility (e.g. Unknown Device and your system does not register your device), you may wish to install them from the manufacturer's website or the CD provided along with the product.

See this guide for a list of common graphic manufacturer websites.

Be sure to follow the manufacturer's instructions for installing the drivers as some require you to have the device plugged (or unplugged) during the installation.

In a driver's properties you may find it useful to know the driver revision date, and can check for drivers older than that date:

In some cases you may not be able to find the appropriate drivers from the manufacturer's website, but on a third party website instead. Sometimes it doesn't have the correct name. It is strongly not recommended to do this, so proceed at your own risk:

  1. Go on the Details tab and change the Property drop down menu contents to Hardware IDs.
  2. Right click on the topmost result, copy it and paste it into your desired search engine.
  3. If you find anything related to your device, proceed to the website with caution and get the drivers from there.

# System Restore

This utility can be game-saving when it comes to reverting your system back to a better known configuration where the operating system was last stable and applications had run fine. It is usually made whenever you install new drivers and updates, but is turned off by default in Windows 10. If you want to enable it:

  1. Open the Start menu and type in "System Restore". From there it should open up a window like this:

  2. Click "Configure" then "Turn on system protection"

  3. After you click OK, you may choose to create restore points by yourself or let Windows create the restore points for you.

If you want to revert to a known restore point, click "System Restore" and the wizard will load up. Be very careful which restore point you pick, as any programs you've installed after the restore point will be removed, and any programs you've uninstalled will be restored.

# Reliability history

In some cases where you're experiencing operating system instability or application errors, you can always check Reliability history and Event Viewer to get a better idea of the problem. Uploading a screenshot of a related log in #tech-support may also give the people who are assisting you a better idea of how to approach the problem.

To find the reliability history, search "View reliability history" in the Start menu and click the first result. It will bring up a window similar to this:

Note that inside the red square there are 3 different categories: informational events, warnings and critical events. They would also show the source (or application) that resulted the event in the history, and clicking "View technical details" would take you to a window like this example, giving you further information on the event and why it happened. It may also help you find solutions if you copied the Problem Event Name.

You can also navigate events that happened in the past which may have led to your current problem.

# Event Viewer

Event viewer is slightly more complex, but has further information on the operating system if it is more than one application that is misbehaving. To find this utility, right click the Start menu, click "Event Viewer". Once it opens, notice there are different categories of event logs on the top left corner. Usually you would want to check Application logs, just expand "Windows Logs" then click on "Applications". It would bring up a similar window to this:

To look for specific types of logs like critical events, warnings or errors, simply click "Filter Current Log" from the top-right corner, and tick the "Critical", "Warning", and "Error" checkboxes.

After applying the filter, you may get a window like this. Press down and inspect the logs that were created at the exact time you begun to experience the problems.

In the general pane, you may copy the first few sentences and paste it in #tech-support or search for a solution on a search engine.

Last Updated: 8/10/2020, 6:10:30 PM