Skip to content

Commit 475d146

Browse files
authored
Fixed alignment
1 parent 9ca1254 commit 475d146

File tree

1 file changed

+21
-24
lines changed

1 file changed

+21
-24
lines changed

defender-endpoint/troubleshoot-av-performance-issues-with-procmon.md

Lines changed: 21 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -33,21 +33,18 @@ There are two ways to capture a Process Monitor (ProcMon) trace:
3333

3434
### Using the MDE Client Analyzer
3535

36-
1. Download the [MDE Client Analyzer ](/defender-endpoint/download-client-analyzer)
36+
1. Download the [MDE Client Analyzer ](/defender-endpoint/download-client-analyzer).
3737

38-
1. Run the MDE Client Analyzer using [Live Response or locally ](/defender-endpoint/run-analyzer-windows)
38+
1. Run the MDE Client Analyzer using [Live Response or locally ](/defender-endpoint/run-analyzer-windows).
3939

40-
> [!TIP]
41-
> Before starting the trace, please make sure that the issue is reporducible. Additionally, close any applications that do not contribute to the reproduction of the issue.
40+
> [!TIP]
41+
> Before starting the trace, please make sure that the issue is reproducible. Additionally, close any applications that do not contribute to the reproduction of the issue.
4242
4343
1. Run the MDE Client Analyzer with the -c and -v switches
4444

45-
46-
47-
48-
```powershell
49-
C:\Work\tools\MDEClientAnalyzer\MDEClientAnalyzer.cmd -c -v
50-
```
45+
```powershell
46+
C:\Work\tools\MDEClientAnalyzer\MDEClientAnalyzer.cmd -c -v
47+
```
5148

5249
### Manually
5350

@@ -63,14 +60,14 @@ C:\Work\tools\MDEClientAnalyzer\MDEClientAnalyzer.cmd -c -v
6360

6461
1. Select **Apply**.
6562

66-
![Screenshot showing the Remove MOTW page.](media/procmon-motw.png)
63+
![Screenshot showing the Remove MOTW page.](media/procmon-motw.png)
6764

6865
1. Unzip the file in `C:\temp` so that the folder path is `C:\temp\ProcessMonitor`.
6966

7067
1. Copy **ProcMon.exe** to the Windows client or Windows server you're troubleshooting.
7168

72-
> [!TIP]
73-
> Before running ProcMon, make sure all other applications not related to the high CPU usage issue are closed. Taking this step helps to minimize the number of processes to check.
69+
> [!TIP]
70+
> Before running ProcMon, make sure all other applications not related to the high CPU usage issue are closed. Taking this step helps to minimize the number of processes to check.
7471
7572
1. You can launch ProcMon in two ways.
7673

@@ -108,29 +105,29 @@ C:\Work\tools\MDEClientAnalyzer\MDEClientAnalyzer.cmd -c -v
108105
109106
1. After completing step 6, set filters by selecting **OK**. You can filter the results after the capture is complete.
110107
111-
![Screenshot showing the page where System Exclude is chosen as the Filter out Process Name.](media/procmon-filter-options.png)
108+
![Screenshot showing the page where System Exclude is chosen as the Filter out Process Name.](media/procmon-filter-options.png)
112109
113110
1. To start the capture, select the magnifying glass icon again.
114111
115112
1. Reproduce the problem.
116113
117-
> [!TIP]
118-
> Wait for the problem to be reproduced, then note the timestamp when the trace begins.
114+
> [!TIP]
115+
> Wait for the problem to be reproduced, then note the timestamp when the trace begins.
119116
120117
1. After capturing two to four minutes of process activity during high CPU usage, stop the capture by clicking the magnifying glass icon.
121118
122-
2. To save the capture with a unique name in the `.pml` format, go to **File** then click **Save...**. Ensure you select the radio buttons **All events** and **Native Process Monitor Format (PML)**.
119+
1. To save the capture with a unique name in the `.pml` format, go to **File** then click **Save...**. Ensure you select the radio buttons **All events** and **Native Process Monitor Format (PML)**.
123120
124-
![Screenshot showing the save settings page](media/procmon-savesettings1.png)
121+
![Screenshot showing the save settings page](media/procmon-savesettings1.png)
125122
126123
1. For better tracking, change the default path from `C:\temp\ProcessMonitor\LogFile.PML` to `C:\temp\ProcessMonitor\%ComputerName%_LogFile_MMDDYEAR_Repro_of_issue.PML` where:
127124
128-
- `%ComputerName%` is the device name
129-
- `MMDDYEAR` is the month, day, and year
130-
- `Repro_of_issue` is the name of the issue you're trying to reproduce
125+
- `%ComputerName%` is the device name
126+
- `MMDDYEAR` is the month, day, and year
127+
- `Repro_of_issue` is the name of the issue you're trying to reproduce
131128
132-
> [!TIP]
133-
> If you have a working system, you might want to get a sample log to compare.
129+
> [!TIP]
130+
> If you have a working system, you might want to get a sample log to compare.
134131
135-
1. Zip the `.pml` file and submit it to Microsoft support.
132+
1. Zip the `.pml` file and submit it to Microsoft Support.
136133

0 commit comments

Comments
 (0)