In this first part of our Process Monitor series, we’ll walk you through the essential steps to download, launch, and navigate the interface. Our focus is on creating effective filters to pinpoint permissions issues—whether that’s a misconfigured ACL on a registry key, DLL, data file, or folder. These problems often lead to application failures, and learning how to filter events in Process Monitor is key to catching them early. If you’re an IT admin or a programmer looking to sharpen your troubleshooting skills, this introduction will give you a solid foundation for using Process Monitor to diagnose and fix permission-related errors in your applications.
"Everybody can be great... because anybody can serve. You don't have to have a college degree to serve. You don't have to make your subject and verb agree to serve. You only need a heart full of grace. A soul generated by love." Martin Luther King Jr.
DISCLAIMER: DISCLAIMER: All scripts are provided "as is" without any warranties or guarantees of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, and non-infringement. Use of this script is at your own risk. The author shall not be held responsible or liable for any damages, data loss, or other issues that arise from the use or misuse of these scripts. You are solely responsible for ensuring that the script is suitable for your specific requirements and for any consequences that result from its execution. Before running these scripts, thoroughly test them in a controlled environment to ensure they function as expected. It is also recommended that you back up any critical data before use. By using the script provided, you agree to these terms and acknowledge that you have read and understood this disclaimer. By using these scripts provided, you agree to these terms and acknowledge that you have read and understood this disclaimer.
Process Monitor is the tool that you're looking at right now. This tool allows admins and especially
developers to analyze and investigate applications and services, especially applications that they're
developing, in the case of a developer, or for the IT pro, it allows us to use this tool to analyze
what is causing problems with an application that we're investigating. Process Monitor allows us to
capture a lot of data quickly, so we have to be careful and make sure that we have enough
hard drive space. If we can put the data that we capture somewhere else besides C drive,
say you're using a laptop, you probably want to be very careful about putting that data
on the C drive because you're going to overwhelm and use all the free space on that hard drive
and Windows is going to crash and burn. It's important to understand that Process Monitor
captures threads and processes, registry events, file and folder events, and network traffic
events. So those are the items that it really looks at and monitors and helps you analyze
how is an application failing or generating errors by looking at all that information.
We're not looking at the kernel, we're looking at user space. So that's where applications,
where our services reside, which is typically where most of our problems reside, is in those spaces.
So I'm going to show you how to use Process Monitor to solve some of the most common
application problems. In order to use Process Monitor, you must understand this diagram.
And if you don't, it's just a part of your learning process. You need to look at some of
the resources I'm going to show you so that you can better understand this diagram because this
is Windows. Notice there are two red lines. You have user mode above and that is where Process
Monitor is going to help us troubleshoot. That is where application developers work. They work in
user mode. Then we have kernel mode and that's where Microsoft's engineers develop the kernel.
And then at the very bottom, you see one more red line and that's where Hypervisor exists.
Microsoft gives us some tools to look at kernel mode, debug tools, things like that. Very few
tools to look at Hypervisor, but there is some ways to investigate possible problems in the
Hypervisor. But in most cases, Microsoft's engineers and talented support people are
going to take care of kernel mode and Hypervisor, where developers and IT pros work is primarily
user mode. So applications, services, system processes, environmental subsystems,
that's where we work at. That's where we troubleshoot. That's where we install. That is
our space. One of the great resources to better understand Windows and how it works, and in this
case, this book, which you can get on Amazon, really helps you understand Process Monitor and
how to use it. It's called Troubleshooting with Windows System Tools. It is done by Mark
and other secondary authors. This is a great book to get started with to better understand
how to use Process Monitor to troubleshoot that user mode area of Windows applications
and other things that you may have problems with. If you're still struggling with
understanding Windows, Win Internals Part 1, this is a 7th edition. Again, it's available on
Amazon. There is also a Part 2. This was again written by Mark Russinovich, David Solomon,
and some other authors. This is another great resource to help you understand how Windows
really works. Then as you use tools like Process Explorer, Process Monitor,
you really understand what's going on. Let's step back for a second and ask the question,
how do I get the Process Monitor on my system? If you're a developer and you're going to install it
so that you really can use it extensively, I would encourage you to get the System Internals Suite
from the Microsoft Store. That way, the Microsoft Store actually updates and maintains your software
because you've downloaded it from the Microsoft Store. So that takes care of updates. If you're
going to use it only for a one-time event, you're troubleshooting someone's laptop,
you're troubleshooting someone's desktop, you're going to do it one time and you're going to be
out of there, then I recommend you go to the live.systeminternals.com. And at this site is a
list of all the system internal tools. And you can just find the one you want, in this case,
Process Monitor, ProcMon, and simply download that. Now, it has two versions, 32-bit and 64-bit.
If you download the 64-bit, it has procmon.exe and procmon64.exe. So one is 32-bit, one is 64-bit.
So you can download whichever executable you want. And that way, you only download the tool
when you need it. These are all portable apps. They don't install. They simply prompt you for
the legal rights to run the software. And that's it. Now, I have done a previous video on ProcMon,
and you can find it if you go to Tech Savvy Productions. Once you get to the Tech Savvy
Productions channel, you can go to the search and just type in ProcMon. And it should pull up
the older video that I did on this topic. If you'd like to watch more than one video,
go back and take a look at my older video. I'll cover things on that video that I probably won't
cover in this one. Let's get started with Process Monitor. I'm going to quickly go over some of the
ones in the menu so that you can better understand what those are about. Now, the forward arrow
button either starts the capture, or I can hit it again, and it stops the capture. If I want to
remove what's on the display, I can come over here to the eraser, and that's Ctrl-X, and it
clears the display. One of the most powerful features of Process Monitor is the ability to
see the process tree along with the data that we're capturing. So if you're familiar with
Process Explorer, then this little icon that looks like a hierarchical-type tree, you click on it,
and this allows me to see the relationship between parent and child processes, and it gives me a lot
of great information. It's like a Process Explorer view at the same time I'm capturing all this data
in Process Monitor. This, for me, is one of the most powerful features that I'm going to be using
when I troubleshoot with Process Monitor. Now, there are four important buttons up here. Let me
go ahead and turn on my capture. This one is Registry Activity, and if I click it, it's going
to filter out all registry information and not display it on the screen. I don't lose it, but I
don't display it. If I click the folder, then all the folder and file events that Process Monitor is
capturing are, again, going to be removed from the display, and I don't see that information
displayed right now. This is called noise because it's information that's not helpful for me in
solving my problem. So, although I need to capture all this stuff, it's just noise in terms of
enormous amount of data that's not helping me solve my problem. I'm going to click off the next
button, which is Network, and that's, again, remove all of that information from my display,
and I'm finally left with processes and threads, which is what I want to see in my case. If I need
quick categories of events to be removed because they're really noise, they're not helping me solve
my problem because I know in my situation, threads and the events that are taking place
are what I'm looking for. Number one problem with applications is file access or permission
problems. They show up as missing or misplaced files. If an application fails to start or crashes
because it can't find a specific DLL or a configuration file, Procman can show the exact
file path the application is trying to load and which file system call failed. Often, a application
needs to read or write to a directory or a file that lacks sufficient permissions. Procman logs
access denied errors so you can know which permissions to fix. Let's take a look at this
problem and how to analyze it with Procman. All right, let's set the stage for this demonstration.
Now, I know you're saying when you watch this demo, Mr. Vanderpool, this is so simple, so easy,
and the application problems that I experience are so much more complex. That is true,
but understand that the basic problems with applications, no matter what the problem is,
fall into just a few categories. So, if we understand those categories and how to filter,
build our filters in Procman, we can tackle just about any application problem. Now, listen
carefully. I have never seen an application pop up an error message and say, Mr. V, I'm
having a problem. I'm application XYZ and this is the error message and this is what you can do
to fix the problem. I've never seen an error message like that. In fact, I can say in 30 years
of seeing application error messages, I don't remember a one that gave me any insight to what
the real problem was. So, let's forget the error messages and it doesn't matter how complex the
application is. Let's focus on those basic application and how to tackle them. All right.
So, we have a folder called testprocman folder and in it, I'm going to open it. I have a file
called hello world.txt. Now, I've removed everyone from the NTFS permissions of this file. So,
no one in the whole world can open, change, do anything with this particular file. But we're
going to attempt with an application called notepad. Let's do it. I'm going to try to open
and I'm just going to choose it. So, you can see I'm deliberately choosing notepad as my option
and that's exactly what we get is some kind of error message. Now, because it's simple
and because I'm using notepad, I'm getting an error message that's basically telling me what
the problem is. I don't ever get those. Okay. Neither do you. Let's use procman to find out
what the problem is and I'll show you how to build our filter so we can go after access denied
problems. Anytime the application can't open a DLL or a configuration file, it's generally because
of permissions. So, let's go look at how to do this. I want to set up my process monitor with
special filtering so that I can quickly identify because error messages are not helpful. I want to
quickly identify is potentially the application problem crashing, refusing to open, refusing to
install related to a file or folder permission issue. Let's set up our filter to capture that.
I'm going to go to filter and you can see one of the things that I've done is I said anywhere in
the events, the result contains access denied then included in my report. I also included in my case
because I know that the name of the developers call this the image of the application. It's the
executable that starts that application. In our case, it's going to be notepad. So,
I've created process name contains notepad and I've included that in our filter.
Then in this case, I have a path. You may not know at all what the path is. You could leave
that out. That's not as critical as the two that I've just done before because what it's going to
do is look for and filter out any time notepad is in the events and access denied is a result.
We can quickly try to determine is this application failing due to file permissions or folder
permissions or possibly registry key permissions. Let's check it out. I've got these in my filter
and I'm going to go ahead and apply. Those are there. I'm going to start the capture
and notice nothing shows up. We don't want all that information. We know that it can
collect a lot of information, but that's just noise. It's not helping us at all.
So, now we're going to go to our folder. In this case, an application that you're running
and I'm going to go ahead and open it with whatever application you're trying to troubleshoot.
And I'm going to get the error message, even though our error message is helpful.
And we do get an event that was captured and notice the result was access denied.
And I can see that the operation was attempting to open this file. That's what create file
operation means. With this information, I want to check the path. I want to check the directory
to see the permissions are correct. And I want to check this file to see that its permissions
are correct. Let's go take a look because what I'm getting is an access denied when I try to
open that file. That could be true with opening a registry, opening up a DLL or whatever.
That's going to be a red flag. You've got a permissions issue.
Here you see I've opened up the folder and I went to the permissions of the file and you can see
no user group is in the access entry. So, it's not going to allow anyone to open,
change or do anything with this file because no one has rights to it.
Now, this is real simple, but the principle is the same no matter how complex the application
or confusing the error messages. First, try to discover is the application crashing,
not opening, whatever the problem is due to permissions. So, we're going to create filters
that are going to be looking at access denied. Below in my filter, I'm going to choose
result contains and then I'm going to type in access denied. And I'm going to then add that
to my filter. It will capture a registry key that's got a permission that's awkward,
file, folder, anything. With this filter in place, you can rule out or rule in that permissions are
potentially a problem with this application failure. Notice in the filtering, I have
chose, let me click this one so you can see it. I've chose process name. I could put anything
in there, but because I know the name of the file that launches the application,
I'm going to put that in. And you would want to be very careful. You can't make mistakes here.
You have to be accurate in your information. So, I'm going to put in notepad.exe. I know
that's the file that launches notepad. And then I'm going to add that into my filter.
So, there it is. And if I knew path information, put it in. The error message could have given you
some path information or file information. Add that into your ProcMon filter.
Now, I know what you're thinking. You're thinking, Mr. Vanderpool, this was such an easy problem.
My help desk, first day on the job could have solved this problem. You're missing the point.
Applications failure, whatever type of failure you experience, fall under basically seven
categories. Now, we know that applications are complex and there's always a few exceptions,
but the large majority of application failures fall under file and access permission problems,
registry-related errors, startup and initialization failures, intermittent crash
and error codes, performance bottlenecks, debugging script installers or updaters,
and security access and token issues. So, if I can learn to use ProcMon and build filters
that will help me capture the majority of those seven types of category application failures,
my chances of at least gleaning good information that I can pass on to developers
so that they can help solve the problem are pretty high.
Now, if you are one of those IT professionals that would rather call the developer on the phone or
contact them, whatever, via email and say, your application is broke. And we all know what
happens when you do that. This fog of love flows in through that company. The developers run out
of their chairs and they all hold hands and they say to themselves, a customer's unhappy.
Our application is broke. Let's fix it. Now, if you believe that, go ahead. I would rather send
as much information as I can that's relevant to the problem so that the poor developer that's
given your problem can look at what you sent and say, well, they've at least tried hard to point
me in the right direction and they've given me as much information as they can. Let me see if I
can solve this. Now, I, on the other hand, prefer the fog of love and the holding of hands. That's
been so effective for me over the last 30 years. All right, all kidding aside, in video two, we're
going to focus on filters for all of those seven categories and techniques and ideas to trap and
display and identify whether your application failure is one of those or maybe two of those
categories so that you can help your developer team or pass that information on to the company
that develops your software, one or the other, so that you can learn to use Process Monitor
more effectively in troubleshooting applications. We encourage you to become a member of our channel.
It's $2.99 a month. You can become a member for six months, for a year, whatever you would like. We
really appreciate your support. Our videos are designed to teach and train. We provide video
notes, PowerPoints, and all the resources we possibly can to our members, and I just encourage
you if what we produce is helpful to you, become a member. It helps with the cost of producing
this type of material, and we really appreciate your support.