Process Explorer (procexp.exe)
Part of Sysinternals Suite
Advanced features:
Detailed process information
View open handles and loaded DLLs
Analyze process relationships
Powerful tool for advanced system troubleshooting
From <https://claude.ai/chat/32155873-e13b-461c-ba7b-f4eb0c09aa09>
Compare Process Explorer and Process Monitor
The Process Explorer and Process Monitor tools are part of the Windows Sysinternals tool suite:
Process Explorer. Enables you to determine the currently active processes on a Windows computer, and depending upon mode:
Enables you to see the handles that the selected process has opened.
Enables you to see the dynamic-link libraries (DLLs) and memory-mapped files that the process has loaded.
Process Monitor. This is an advanced tool for monitoring Windows that shows real-time file system, registry,
and process/thread activity. Process Monitor includes monitoring and filtering capabilities.
https://learn.microsoft.com/en-us/training/modules/explore-support-diagnostic-tools/7-compare-process-explorer-process-monitor
Here’s a detailed IT-focused guide on using Process Explorer, with a comparison to Process Monitor, practical examples, and tips you can use in real helpdesk work or interviews.
Process Explorer is part of Microsoft Sysinternals and acts as a supercharged Task Manager.
Think of it as Task Manager on steroids:
See exact parent/child process hierarchy
Check DLLs loaded by each process
Monitor CPU, memory, handles, and threads in real-time
Identify hidden or suspicious processes
IT use cases:
⭐ Troubleshooting app crashes
⭐ Investigating high CPU, RAM, or handle leaks
⭐ Detecting malware or rogue processes
⭐ Identifying which process locks a file
1️⃣ Download from Sysinternals: https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer
2️⃣ Extract and run procexp.exe
3️⃣ Optional: Run as Administrator for full process visibility
Quick tip:
⭐ Pin it to the Start Menu or a troubleshooting toolkit for fast access.
⭐ Shortcut: Win + R → type path to procexp.exe → Enter
1️⃣ Process Tree
Shows parent → child relationships
Example: explorer.exe → chrome.exe → chrome_child.exe
2️⃣ Columns
CPU%, Private Bytes, Working Set, I/O Reads/Writes
Add Handles, Threads, Command Line for deeper insight
3️⃣ DLLs and Handles view
Ctrl + D → loaded DLLs
Ctrl + H → handles (file, registry keys)
4️⃣ Search function
Ctrl + F → search for a handle or DLL
Example: “Who has locked my Excel file?”
User:
“My PC is extremely slow.”
Steps:
1️⃣ Open Process Explorer
2️⃣ Sort by CPU%
3️⃣ Expand tree to find parent process causing children to spike
Observation:
svchost.exe → high CPU, multiple child services
Resolution:
Identify the service causing spike → restart service or escalate
User:
“I can’t delete a file; Windows says it’s in use.”
Steps:
1️⃣ Ctrl + F → search for file name
2️⃣ Process Explorer shows which process has it open
3️⃣ Kill the handle safely
Tip:
⭐ Don’t just kill the process; close handle to prevent crashes
Scenario: Application crashes with “ucrtbase.dll missing.”
Steps:
1️⃣ Select process → View DLLs (Ctrl + D)
2️⃣ Identify mismatched DLL version
Resolution:
Update the application or replace corrupted DLL
Rule of thumb:
Process Explorer = who / what process
Process Monitor = what / what action
⭐ Use Process Explorer first to identify suspicious processes.
⭐ Only use Process Monitor when you need deep forensic logging.
⭐ Combine both for root-cause analysis: e.g., high CPU → check handles → check I/O → monitor actions.
⭐ Admin tip: Right-click → “Properties” → “Strings” or “Verify digitally signed” for suspicious processes.
Question:
“When would you use Process Explorer instead of Process Monitor?”
Answer:
“I would use Process Explorer to identify which process is causing high CPU, memory, or file locks in real time because it provides a clear process tree and loaded DLLs. If I need to see the exact operations the process is performing on files, registry, or network, I would then use Process Monitor.”
Context:
User is working remotely.
Excel freezes intermittently but does not crash.
No error messages pop up.
Windows 10 / 11 environment.
Your goal: identify the cause and suggest a solution using Process Explorer and, if needed, Process Monitor.
What to say aloud:
“I understand Excel is freezing intermittently. I’ll start by identifying which process or resource might be causing the freeze using Process Explorer, and if necessary, I’ll monitor the exact operations Excel is performing with Process Monitor.”
Why this works:
Shows structured thinking
Names tools specifically
Avoids guessing
Uses conditional escalation (“if necessary”)
Actions:
1️⃣ Open Process Explorer as Administrator.
2️⃣ Locate EXCEL.EXE in the process tree.
3️⃣ Look at:
CPU usage → sudden spikes?
Memory → working set vs private bytes
Handles → files or registry keys that might be stuck
Threads → unusually high thread count
Example observation:
Excel shows 2% CPU normally, spikes to 60% when freezing
Handle count steadily increases, never drops
Threads count unusually high → potential plugin or add-in
Say aloud:
“Excel is showing periodic CPU spikes and an increasing number of handles, which suggests it might be waiting on another process or file. This could be caused by a third-party add-in or a file lock.”
Tip for interview scoring:
Correlating CPU + handles + threads shows analytical thinking.
Mention the parent process if relevant (like EXCEL.EXE launched via OUTLOOK.EXE) to demonstrate depth.
Actions:
1️⃣ Select EXCEL.EXE → right-click → Properties → DLLs tab
2️⃣ Look for unusual or outdated DLLs
3️⃣ Example: SomeAddIn.dll loaded that is not part of Office
Say aloud:
“I noticed that an add-in DLL loaded with Excel may be causing resource contention. Verifying its version and compatibility is the next step.”
Professional tip:
This shows awareness of software dependencies, not just CPU/Memory.
Why use Process Monitor:
Process Explorer identifies who or what process is the bottleneck.
Process Monitor identifies what actions the process is performing in real time.
Actions in Process Monitor:
1️⃣ Filter for Process Name = EXCEL.EXE
2️⃣ Observe filesystem and registry activity
3️⃣ Watch for:
Repeated failed registry access (permissions issues)
Slow read/write operations on large spreadsheets
Add-ins accessing network resources (OneDrive, SharePoint)
Example observation:
Excel repeatedly accesses C:\Users\Jonathan\AppData\Local\Temp\*.tmp
One file fails with ACCESS DENIED
File is locked by another process (OUTLOOK.EXE)
Say aloud:
“Process Monitor shows Excel repeatedly trying to access a temporary file that’s locked by Outlook, which explains the intermittent freezing.”
Tip for interviews:
Explaining correlation between Process Explorer and Process Monitor is a strong signal of systematic troubleshooting.
Immediate actions:
1️⃣ Close Excel and any other application locking the file
2️⃣ Remove or disable problematic add-ins temporarily
3️⃣ Clear the Temp folder if permissions are blocking access
Long-term actions:
Ensure Office and add-ins are updated
Monitor file access on shared/network drives
Educate user to avoid simultaneous editing conflicts
Say aloud:
“By closing conflicting processes and verifying add-ins, we prevent Excel from freezing. I would also monitor updates and temporary file access to prevent recurrence.”
“I start with Process Explorer to identify which process is using CPU, memory, threads, or handles excessively. In this scenario, Excel showed spikes and handle accumulation, suggesting a file or add-in issue. I then use Process Monitor to track exact filesystem and registry activity, revealing that Excel was repeatedly attempting to access a temp file locked by Outlook. Based on these findings, I would close the conflicting process and verify add-ins to resolve the issue.”
Original idea:
“Explain how to use the Process Explorer & also, compare it it to Process Monirot for an IT with exemples & tips”
Refined, professional:
⭐ “Explain how IT professionals use Process Explorer, compare it to Process Monitor, and provide practical examples and troubleshooting tips.”
Fixed typos: it it → it, Monirot → Monitor
Improved structure and clarity
Professional, concise phrasing
Think of it like a diagnostic sequence:
1️⃣ Process Explorer → Identify which process is misbehaving
2️⃣ Process Monitor → Identify exact operations causing the problem
Use Process Explorer first for efficiency
Escalate to Process Monitor only if more detail is required
Process Explorer = who / what resource is causing trouble
Process Monitor = what exactly is being done / accessed / blocked
Combine them for root-cause troubleshooting
Always explain reasoning aloud in interviews