![]() ![]() It will additionally track a few other events in a limited fashion. What it does do is capture specific types of I/O (Input / Output) operations, whether they happen through the file system, registry, or even the network. It’s not going to track which processes are open and wasting CPU on your computer - that’s the job of Process Explorer, after all. For instance, Process Monitor doesn’t care if you move your mouse around, and it doesn’t know whether your drivers are working optimally. Process Monitor captures a ton of data, but it doesn’t capture every single thing that happens on your PC. If you’ve ever wondered how some geek figured out a registry hack that nobody has ever seen, it was probably through Process Monitor. We don’t do a lot of registry hack articles anymore, but back when we first started we would use Process Monitor to figure out what registry keys were being accessed, and then go tweak those registry keys to see what would happen. Want to understand which registry keys your favorite application is actually storing their settings in? Want to figure out what files a service is touching and how often? Want to see when an application is connecting to the network or opening a new process? It’s Process Monitor to the rescue. This is like taking a peek at a global logfile for every single event that happens on your Windows PC. Unlike the Process Explorer utility that we’ve spent a few days covering, Process Monitor is meant to be a passive look at everything that happens on your computer, not an active tool for killing processes or closing handles. Wrapping Up and Using the Tools Together. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |