Skip to content

Commit 2f66d88

Browse files
authored
Update microsoft-defender-antivirus-compatibility.md
Needed to clarify smart app control clause as it overlaps with MDE and causes ambiguity around passive mode enablement scenarios.
1 parent e20834d commit 2f66d88

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

defender-endpoint/microsoft-defender-antivirus-compatibility.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ The following table summarizes what to expect:
6363
|Windows version|Primary antivirus/antimalware solution|Microsoft Defender Antivirus state|
6464
|---|---|---|
6565
|Windows 10 <br/>Windows 11|Microsoft Defender Antivirus|Active mode|
66-
|Windows 10 <br/>Windows 11|A non-Microsoft antivirus/antimalware solution|Disabled mode (happens automatically) <br/><br/> In Windows 11, if SmartAppControl is enabled, Microsoft Defender Antivirus goes into passive mode.|
66+
|Windows 10 <br/>Windows 11|A non-Microsoft antivirus/antimalware solution|Disabled mode (happens automatically) <br/><br/> Note that in Windows 11, if SmartAppControl is enabled, you may observe that Microsoft Defender Antivirus goes into passive mode instead of remaining in disabled mode. However, this is not the same scenario as for devices onboarded to Microsoft Defender for Endpoint.|
6767
|Windows Server 2025 <br/>Windows Server 2022 <br/>Windows Server 2019<br/>Windows Server, version 1803, or newer <br/>Windows Server 2016 <br/>Windows Server 2012 R2 |Microsoft Defender Antivirus|Active mode|
6868
|Windows Server 2025<br/>Windows Server 2022<br/>Windows Server 2019<br/>Windows Server, version 1803, or newer <br/>Windows Server 2016 |A non-Microsoft antivirus/antimalware solution|Disabled<br/>(set manually; see the note that follows this table) |
6969

0 commit comments

Comments
 (0)