Skip to content

Commit 70e1b1b

Browse files
committed
Learn Editor: Update troubleshoot-av-performance-issues-with-wprui.md
1 parent 5802703 commit 70e1b1b

File tree

1 file changed

+26
-27
lines changed

1 file changed

+26
-27
lines changed

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

Lines changed: 26 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -45,14 +45,13 @@ Manually
4545

4646
1. Download the [MDE Client Analyzer ](/defender-endpoint/download-client-analyzer).
4747

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

5050
> [!TIP]
5151
> 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.
5252
5353

54-
55-
1. Run the MDE Client Analyzer with the -a and -v switches
54+
3. Run the MDE Client Analyzer with the -a and -v switches
5655

5756
PowerShellCopy
5857

@@ -69,33 +68,33 @@ Manually
6968
7069
1. Download and install WPR.
7170

72-
1. Under *Windows Kits*, right-click **Windows Performance Recorder**.
71+
2. Under *Windows Kits*, right-click **Windows Performance Recorder**.
7372

7473
![Screenshot showing the Start menu](media/wpr-01.png)
7574

76-
1. Select **More**. Select **Run as administrator**.
75+
3. Select **More**. Select **Run as administrator**.
7776

78-
1. Right-click **Yes** when the User Account Control dialog box appears.
77+
4. Right-click **Yes** when the User Account Control dialog box appears.
7978

8079
![Screenshot showing the UAC page.](media/wpt-yes.png)
8180

82-
1. Next, download the [Microsoft Defender for Endpoint analysis](https://github.com/YongRhee-MDE/Scripts/blob/master/MDAV.wprp) profile and save as `MDAV.wprp` to a folder such as `C:\temp`.
81+
5. Next, download the [Microsoft Defender for Endpoint analysis](https://github.com/YongRhee-MDE/Scripts/blob/master/MDAV.wprp) profile and save as `MDAV.wprp` to a folder such as `C:\temp`.
8382

84-
1. In the WPR dialog box, select **More options**.
83+
6. In the WPR dialog box, select **More options**.
8584

8685
![Screenshot showing the page where you can select more options](media/wpr-03.png)
8786

88-
1. Select **Add Profiles...** and browse to the path of the `MDAV.wprp` file.
87+
7. Select **Add Profiles...** and browse to the path of the `MDAV.wprp` file.
8988

90-
1. A new profile named Microsoft Defender for Endpoint analysis should appear under Custom measurements.
89+
8. A new profile named Microsoft Defender for Endpoint analysis should appear under Custom measurements.
9190

9291
![Screenshot showing the in-file.](media/wpr-infile.png)
9392

9493
> [!WARNING]
9594
> If your Windows Server has 64 GB of RAM or more, use the custom measurement `Microsoft Defender for Endpoint analysis for large servers` instead of `Microsoft Defender for Endpoint analysis`. Otherwise, your system consumes a high amount of non-paged pool memory or buffers, leading to system instability. Explore **Resource Analysis** to choose profiles to add.
9695
> This custom profile provides the necessary context for in-depth performance analysis.
9796
98-
1. To use the custom measurement Microsoft Defender for Endpoint verbose analysis profile in the WPR UI:
97+
9. To use the custom measurement Microsoft Defender for Endpoint verbose analysis profile in the WPR UI:
9998

10099
1. Ensure no profiles are selected under the *First-level triage*, *Resource Analysis* and *Scenario Analysis* groups.
101100

@@ -110,34 +109,34 @@ Manually
110109
> [!IMPORTANT]
111110
> Select **File** to use the file logging mode if you can directly reproduce the performance issue. Most issues fall under this category. However, if you cannot directly reproduce the issue, select Memory to use the memory logging mode. This prevents the trace log from inflating excessively due to long run times.
112111
113-
1. Now you're ready to collect data. Close all unnecessary applications. Click **Hide options** to keep the space occupied by the WPR window small.
112+
10. Now you're ready to collect data. Close all unnecessary applications. Click **Hide options** to keep the space occupied by the WPR window small.
114113

115114
![Screenshot showing the Hide options.](media/wpr-08.png)
116115

117-
1. Select **Start**.
116+
11. Select **Start**.
118117

119118
![Screenshot showing the Record system information page.](media/wpr-09.png)
120119

121-
1. Reproduce the issue.
120+
12. Reproduce the issue.
122121

123122
> [!TIP]
124123
> Limit the data collection to a maximum of five minutes. Ideally, aim for two to three minutes, as a significant amount of data is being collected.
125124
126-
1. Select **Save**.
125+
13. Select **Save**.
127126

128127
![Screenshot showing the Save option.](media/wpr-10.png)
129128

130-
1. Fill in **Type in a detailed description of the problem:** with information about the problem and how you reproduced the issue.
129+
14. Fill in **Type in a detailed description of the problem:** with information about the problem and how you reproduced the issue.
131130

132131
![Screenshot showing the pane in which you fill.](media/wpr-12.png)
133132

134-
1. Select **File Name:** to determine where your trace file is saved. By default, it's saved to `%user%\Documents\WPR Files\`.
133+
15. Select **File Name:** to determine where your trace file is saved. By default, it's saved to `%user%\Documents\WPR Files\`.
135134

136-
1. Select **Save**.
135+
16. Select **Save**.
137136

138137
![Screenshot showing the WPR gathering general trace.](media/wpr-13.png)
139138

140-
1. After the trace has been merged and saved, right-click **Open folder**.
139+
17. After the trace has been merged and saved, right-click **Open folder**.
141140

142141
![Screenshot that displays the notification that WPR trace has been saved.](media/wpr-14.png)
143142

@@ -151,11 +150,11 @@ To collect a WPR trace using the command-line tool wpr.exe:
151150

152151
1. Download **[Microsoft Defender for Endpoint analysis](https://github.com/YongRhee-MDE/Scripts/blob/master/MDAV.wprp)** performance trace profile as `MDAV.wprp` in a local directory such as `C:\traces`.
153152

154-
1. Right-click the **Start Menu** icon and select **Windows PowerShell (Admin)** or **Command Prompt (Admin)** to open an Admin command prompt window.
153+
2. Right-click the **Start Menu** icon and select **Windows PowerShell (Admin)** or **Command Prompt (Admin)** to open an Admin command prompt window.
155154

156-
1. Select **Yes** in the User Account Control dialog box.
155+
3. Select **Yes** in the User Account Control dialog box.
157156

158-
1. At the **Command Prompt (Admin)**, run the following command to start a Microsoft Defender for Endpoint performance trace:
157+
4. At the **Command Prompt (Admin)**, run the following command to start a Microsoft Defender for Endpoint performance trace:
159158

160159
```console
161160
@@ -166,25 +165,25 @@ To collect a WPR trace using the command-line tool wpr.exe:
166165
> [!WARNING]
167166
> If your Windows Server has 64 GB of RAM or more, use profiles `WDForLargeServers.Light` and `WDForLargeServers.Verbose` instead of profiles `WD.Light` and `WD.Verbose`, respectively. Otherwise, your system consumes a high amount of non-paged pool memory or buffers, leading to system instability.
168167
169-
1. Reproduce the issue.
168+
5. Reproduce the issue.
170169

171170
> [!TIP]
172171
> Limit the data collection to a maximum of five minutes. Ideally, aim for two to three minutes, as a significant amount of data is being collected.
173172
174-
1. At the **Command Prompt (Admin)**, run the following command to start a Microsoft Defender for Endpoint performance trace:
173+
6. At the **Command Prompt (Admin)**, run the following command to start a Microsoft Defender for Endpoint performance trace:
175174

176175
```console
177176
wpr.exe -stop merged.etl "Timestamp when the issue was reproduced, in HH:MM:SS format" "Description of the issue" "Any error that popped up"
178177
```
179178

180-
1. Wait until the trace is merged.
179+
7. Wait until the trace is merged.
181180

182-
1. Include both the file and the folder in your submission to Microsoft Support.
181+
8. Include both the file and the folder in your submission to Microsoft Support.
183182

184183
## See also
185184

186185
- [Collect Microsoft Defender Antivirus diagnostic data](collect-diagnostic-data.md)
187186
- [Configure and validate exclusions for Microsoft Defender Antivirus scans](configure-exclusions-microsoft-defender-antivirus.md)
188187
- [Performance analyzer for Microsoft Defender Antivirus](tune-performance-defender-antivirus.md)
189188

190-
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]
189+
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]

0 commit comments

Comments
 (0)