Skip to content

Commit 3eb5d27

Browse files
Merge branch 'main' into patch-10
2 parents 29cac0f + 46f09fb commit 3eb5d27

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -54,9 +54,9 @@ There are two ways to capture the Windows Performance Recorder (WPRUI) trace:
5454
1. Run the MDE Client Analyzer with the `-a` and `-v` switches.
5555

5656
PowerShellCopy
57-
57+
5858
```
59-
C:\Work\tools\MDEClientAnalyzer\MDEClientAnalyzer.cmd
59+
C:\Work\tools\MDEClientAnalyzer\MDEClientAnalyzer.cmd -a -v
6060
```
6161

6262
## Manually
@@ -90,7 +90,7 @@ There are two ways to capture the Windows Performance Recorder (WPRUI) trace:
9090

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

93-
> [!WARNING]
93+
> [!WARNING]
9494
> 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 might consume a high amount of nonpaged pool memory or buffers, leading to system instability. To address this, explore **Resource Analysis** to choose profiles to add.
9595
> This custom profile provides the necessary context for in-depth performance analysis.
9696

0 commit comments

Comments
 (0)