Skip to content

Conversation

nizanm1970
Copy link
Contributor

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).

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).
Copy link
Contributor

Learn Build status updates of commit 44a6ae6:

✅ Validation status: passed

File Status Preview URL Details
defender-endpoint/validate-antimalware.md ✅Succeeded

For more details, please refer to the build report.

@paulinbar paulinbar merged commit 5003dc2 into MicrosoftDocs:public Sep 5, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants