Quote:March-2024 (Engine: 1.1.24030.4 | Platform: Coming soon)​

• Security intelligence update version: 1.409.1.0
  
• Release date: April 2, 2024 (Engine) / Coming soon (Platform)
  
• Engine: 1.1.24030.4
  
• Platform: Coming soon
  
• Support phase: Security and Critical Updates
  

What's new​

• Added manageability settings to opt-out for One Collector telemetry channel and Experimentation and Configuration Service (ECS).
  
• Microsoft Defender Core Service will be disabled when 3rd party Antivirus is installed (except when Defender for Endpoint is running in Passive mode).
  
• The known issue in 4.18.24020.7 where enforcement of device level access policies wasn't working as expected no longer occurs.
  
• Fixed high CPU issue caused by redetection done during Sense originating scans.
  
• Fixed an issue with Security Intelligence Update disk cleanup.
  
• Fixed an issue where the Signature date information on the Security Health report wasn't accurate.
  
• Introducted performance improvements when processing paths for exclusions.
  
• Added improvements to allow recovering from erroneously added Indicators of compromise (IoC).
  
• Improved resilience in processing attack surface reduction exclusions for Anti Malware Scan Interface (AMSI) scans.
  
• Fixed a high memory issue related to the Behavior Monitoring queue that occured when MAPS is disabled.
  
• A possible deadlock when receiving a Tamper protection configuration change from the Microsoft Defender portal no longer occurs.
  

Quote:All our updates contain

• Performance improvements
  
• Serviceability improvements
  
• Integration improvements (Cloud, Microsoft Defender XDR)
  

May-2024 (Engine: 1.1.24050.5 | Platform: 4.18.24050.7)​

• Security intelligence update version: 1.413.1.0
  
• Release date: May 30, 2024 (Engine) / June 4, 2024 (Platform)
  
• Engine: 1.1.24050.5
  
• Platform: 4.18.24050.7
  
• Support phase: Security and Critical Updates
  

What's new​

• Improved performance when running configuration queries.
  
• Optimized how scans are prioritized.
  
• Fixed a crash caused by a race condition with a device control driver.
  
• Added Event Viewer Logging for scan start event where the scan originates from Powershell.