I was able to open the CSV file with Excel. There’s an option in the File menu to output the currently-filtered list to a CSV file. When we’re troubleshooting performance, however, we need to simplify the output for our consumption. This is extremely helpful for identifying where a Serial Number is being stored in the Registry or where User Settings are being read from disk.
a program that fails to load might have “NAME NOT FOUND” or “PATH NOT FOUND” results when opening a file. Additionally, I add two columns: Duration and Event Class.įrom here, you may be able to deduce a lot of information, e.g. The Process Monitor window will scroll through all of the actions that xtop performs, with details on file names and registry locations. When troubleshooting an application, add a new “Include” entry for the process name – in this case, if “Process Name” contains “xtop.exe” then “Include” it in the display. The filter allows you to reduce the data to find what is relevant. (Older versions of Procmon require you to use the Filter->Filter menu, or the Filter button on the toolbar.)
The first thing you’ll be prompted for is the “Process Monitor Filter”. It displays all system calls made by every application running in Windows allowing you to see which files are being opened, what network calls are made, and what registry entries are being read.Īfter you download the file, you’ll be able to run it without any installation. It’s a little bit old, but it still works great, even in Windows 8. It’s a free tool written by a Microsoft-owned studio.
One of the best tools to have available is the Microsoft Sysinternals Process Monitor – procmon.exe. Although replacing hardware and buying more expensive computers can help resolve the issue, there are ways to troubleshoot deeper that you may not have considered.
Everyone knows that troubleshooting “slow performance” is one of the most challenging tasks we have as IT services providers, but is also one of the best ways to improve productivity (and morale!).
0 kommentar(er)
