Skip to content

Commit 44a6ae6

Browse files
authored
Update validate-antimalware.md
The documentation causes confusion with customers with regard to the detection behavior of Windows Defender as they expect an immediate detection once the file is saved. But due to perf optimizations that make this type of validation quite problematic. Added instruction line "3. Open a Command Prompt and Run: 'type EICAR.txt' " to make the validation deterministic and reduce confusion of Cx (less IcM).
1 parent c911942 commit 44a6ae6

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

defender-endpoint/validate-antimalware.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,9 @@ You can run an antivirus detection test to verify that the device is properly on
5252
1. Copy the following string: `X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*`.
5353

5454
2. Paste the string into a `.TXT` file and save it as `EICAR.txt`.
55-
55+
56+
3. Open a Command Prompt and run: `type EICAR.txt`.
57+
5658
### Linux/macOS
5759

5860
1. Ensure that real-time protection is enabled. Run the following command and confirm the output is `"true"`:
@@ -86,4 +88,4 @@ You can run an antivirus detection test to verify that the device is properly on
8688
- [Microsoft Defender for Endpoint - demonstration scenarios](defender-endpoint-demonstrations.md)
8789
- [Microsoft Defender Antivirus in Windows Overview](microsoft-defender-antivirus-windows.md)
8890
- [Microsoft Defender for Endpoint on Linux](microsoft-defender-endpoint-linux.md)
89-
- [Microsoft Defender for Endpoint on macOS](microsoft-defender-endpoint-mac.md)
91+
- [Microsoft Defender for Endpoint on macOS](microsoft-defender-endpoint-mac.md)

0 commit comments

Comments
 (0)