You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Q:** Can I use Microsoft Defender Antivirus in passive mode without onboarding to Microsoft Defender for Endpoint?
86
86
87
-
**A:** No. Passive mode is a functionality in Microsoft Defender for Endpoint Plan 2.
87
+
**A:** No. Passive mode is a functionality in Microsoft Defender for Endpoint Plan 1, Microsoft Defender for Endpoint Plan 2 and Microsoft Defender for Business.
88
88
89
89
**Q:** Can I use [EDR in block mode](edr-in-block-mode.md) without onboarding to Microsoft Defender for Endpoint?
- Support phase: **Security and Critical Updates**
108
108
109
109
#### What's new
110
110
111
-
- Product improvements
111
+
- Improved caching of [device control settings](device-control-policies.md) to improve reliability in occasionally connected environments.
112
+
- Performance improvement in on-access scans of files in network locations.
113
+
- Fixed the Defender service description to match the latest installed version.
114
+
- Improved Defender engine update logic when the update is included in a custom image.
115
+
- Fix in health reporting where signature update data might have been incorrect.
116
+
- Fixed reporting issue with [controlled folder access](controlled-folders.md) (CFA) protected folders using the PowerShell cmdlet [Get-MpPreference](/powershell/module/defender/get-mppreference) when CFA is disabled.
117
+
- Improved performance when scanning UPX-packed files (Ultimate Packer for eXecutables) and updated the validation process to verify the integrity of the packed file itself.
118
+
- Added support for distinguishing regular cloud allow signatures from clean [Indicators of Compromise](indicators-overview.md) (IoC) in [attack surface reduction](attack-surface-reduction.md) (ASR).
- Release date: **October 30, 2024** (Engine and Platform)
162
-
- Platform: **4.18.24090.11**
163
-
- Engine: **1.1.24090.11**
164
-
- Support phase: **Security and Critical Updates**
165
-
166
-
#### What's new
167
-
168
-
- Improved detection logic to reduce false positives related to the Azure Site Recovery rule, [Block Office applications from injecting code into other processes](/defender-endpoint/attack-surface-reduction-rules-reference#block-office-applications-from-injecting-code-into-other-processes)
169
-
- Resolved an issue that could lead to a Windows device to be marked as [noncompliant in Intune](/mem/intune/fundamentals/reports#device-compliance-reports) when Microsoft Defender Antivirus starts.
170
-
- Resolved an issue with catchup scan configuration, where the [DaysUntilAggressiveCatchupQuickScan](/windows/client-management/mdm/defender-csp#configurationdaysuntilaggressivecatchupquickscan) policy setting wasn't honored.
171
-
- Fixed `SharedSignatureRoot` processing when an empty value was set.
172
-
- Fixed a problem with [device control](device-control-overview.md) where certain file systems (like `FAT`, `FAT32`, `exFAT`) with volume information displayed when a blocking rule was defined.
173
-
- Improved performance in specific scenarios where network files were accessed.
174
-
- Fixed an issue with [Azure Virtual Desktop](/azure/virtual-desktop/overview) where the Intune policy wasn't being honored.
175
-
- Fixed potential deadlock for [custom detection rules](/defender-xdr/custom-detection-rules) on the Windows client
176
-
- Resolved an issue where [antivirus exclusions](configure-exclusions-microsoft-defender-antivirus.md) weren't being honored with [AMSI](/windows/win32/amsi/antimalware-scan-interface-portal).
177
-
- Fixed issue impacting a subset of devices where [antivirus exclusions configured through SCCM](/mem/configmgr/protect/deploy-use/endpoint-antimalware-policies#exclusion-settings) weren't honored
178
-
179
-
> [!IMPORTANT]
180
-
> On Windows Server 2019 and later, a new binary (`MpDefenderCoreService.exe`) will be included in the update package to support future service improvements (more information to follow).
181
-
182
-
183
165
### Previous version updates: Technical upgrade support only
184
166
185
167
After a new package version is released, support for the previous two versions is reduced to technical support only. For more information about previous versions, see [Microsoft Defender Antivirus updates: Previous versions for technical upgrade support](msda-updates-previous-versions-technical-upgrade-support.md).
- Release date: **October 30, 2024** (Engine and Platform)
36
+
- Platform: **4.18.24090.11**
37
+
- Engine: **1.1.24090.11**
38
+
- Support phase: **Technical upgrade support (only)**
39
+
40
+
#### What's new
41
+
42
+
- Improved detection logic to reduce false positives related to the Azure Site Recovery rule, [Block Office applications from injecting code into other processes](/defender-endpoint/attack-surface-reduction-rules-reference#block-office-applications-from-injecting-code-into-other-processes)
43
+
- Resolved an issue that could lead to a Windows device to be marked as [noncompliant in Intune](/mem/intune/fundamentals/reports#device-compliance-reports) when Microsoft Defender Antivirus starts.
44
+
- Resolved an issue with catchup scan configuration, where the [DaysUntilAggressiveCatchupQuickScan](/windows/client-management/mdm/defender-csp#configurationdaysuntilaggressivecatchupquickscan) policy setting wasn't honored.
45
+
- Fixed `SharedSignatureRoot` processing when an empty value was set.
46
+
- Fixed a problem with [device control](device-control-overview.md) where certain file systems (like `FAT`, `FAT32`, `exFAT`) with volume information displayed when a blocking rule was defined.
47
+
- Improved performance in specific scenarios where network files were accessed.
48
+
- Fixed an issue with [Azure Virtual Desktop](/azure/virtual-desktop/overview) where the Intune policy wasn't being honored.
49
+
- Fixed potential deadlock for [custom detection rules](/defender-xdr/custom-detection-rules) on the Windows client
50
+
- Resolved an issue where [antivirus exclusions](configure-exclusions-microsoft-defender-antivirus.md) weren't being honored with [AMSI](/windows/win32/amsi/antimalware-scan-interface-portal).
51
+
- Fixed issue impacting a subset of devices where [antivirus exclusions configured through SCCM](/mem/configmgr/protect/deploy-use/endpoint-antimalware-policies#exclusion-settings) weren't honored
52
+
53
+
> [!IMPORTANT]
54
+
> On Windows Server 2019 and later, a new binary (`MpDefenderCoreService.exe`) will be included in the update package to support future service improvements (more information to follow).
0 commit comments