Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | ERROR_INTERNET_CONNECTION_ABORTED | SenseIR.log | -> |
| OS build range | Windows 11 22H2 | System Information | |
| Registry key involved | HKLM\SOFTWARE\Microsoft\Windows Defender\Platform\4.18.2209.6 | Registry Editor | -> |
| Relevant service/endpoint URL | *.endpoint.security.microsoft.com, winatp-gw-*.microsoft.com | SenseIR.log | |
| Log line signature | Failed to connect to endpoint with error code 12029 | MsSense.log | -> |
Log Files to Check
C:\ProgramData\Microsoft\Windows Defender Advanced Threat Protection\Logs\SenseIR.logC:\ProgramData\Microsoft\Windows Defender Advanced Threat Protection\Logs\MsSense.log
What This Error Actually Means
The error code ERROR_INTERNET_CONNECTION_ABORTED, which translates to a hexadecimal value of 0x3015, is raised by the Microsoft Defender for Endpoint's Sense service when it fails to establish a secure connection with its cloud endpoints. The specific components involved are the Windows Defender Advanced Threat Protection (ATP) and the Sense service itself. This error typically indicates that there was an issue during the TLS handshake process or that the connection was forcibly closed before it could complete.Affected Versions and Scope
This issue is observed specifically on Windows 11 build 22H2, where Microsoft Defender for Endpoint version 4.18.2209.6 (as indicated by the registry keyHKLM\SOFTWARE\Microsoft\Windows Defender\Platform\4.18.2209.6) is installed. The problem does not affect earlier or later builds of Windows 11, nor does it impact other operating systems such as Windows 10.
Where To Look First: Logs and Event IDs
To diagnose this issue, start by examining the logs located atC:\ProgramData\Microsoft\Windows Defender Advanced Threat Protection\Logs\SenseIR.log and C:\ProgramData\Microsoft\Windows Defender Advanced Threat Protection\Logs\MsSense.log. In these files, look for lines that contain the exact error string "ERROR_INTERNET_CONNECTION_ABORTED" or the log line signature "Failed to connect to endpoint with error code 12029". Additionally, Event IDs 4706 and 5830 in the Windows logs can provide further context about connectivity issues.
Root Causes
TLS Inspection Proxy Interference
One common cause is when a TLS inspection proxy is incorrectly configured to strip or modify authentication headers, leading to connection failures. This issue can be identified by checking if there are any network policies that intercept HTTPS traffic and inspect it before forwarding the request.Firewall Rules Blocking Traffic
Another root cause could be overly restrictive firewall rules blocking outbound connections to*.endpoint.security.microsoft.com or winatp-gw-*.microsoft.com. This can often be confirmed by attempting a direct connection test using the PowerShell cmdlet Test-NetConnection -ComputerName "*.endpoint.security.microsoft.com" -Port 443.
Incorrect Proxy Configuration in Windows Defender ATP
If your environment uses a proxy server, ensure that it is correctly configured within Microsoft Defender for Endpoint settings. Incorrect or missing configurations can lead to connection issues.Fix Procedure
- First, verify the current proxy configuration by running
Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows Defender\Platform\4.18.2209.6" | Select-Object ProxyServer,ProxyEnable. Adjust these settings if necessary. - To check firewall rules affecting the Sense service connectivity, use
Get-NetFirewallRule -DisplayGroup "Sense Service". - If a TLS inspection proxy is in place, ensure it does not interfere with authentication headers. This may require coordination with network administrators to adjust proxy settings.
- To add or modify proxy configurations for Microsoft Defender ATP, use the following PowerShell cmdlet:
Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows Defender\Platform\4.18.2209.6" -Name ProxyServer -Value "." - In Intune admin center, navigate to Devices > Configuration Profiles, and apply a new or existing configuration profile that includes the necessary proxy settings for Microsoft Defender ATP.
Be cautious when modifying firewall rules as this could disrupt other services relying on network connectivity. Ensure you have a backup plan in case of unintended consequences.
Error Code Variants
| Error Code | Description |
|---|---|
| ERROR_INTERNET_NAME_NOT_RESOLVED (12007) | This error indicates that the DNS lookup for a domain name failed, which is different from an aborted connection. |
| ERROR_INTERNET_CANNOT_CONNECT (12002) | Indicates that the network connection was not established successfully, but does not specify whether it was due to TLS issues or other connectivity problems. |
Verification
After applying the fixes, re-run the cloud connectivity test for Microsoft Defender ATP. Successful resolution should result in log entries indicating successful connections without any error codes like 12029. Additionally, check the Intune admin center under Devices > Compliance Policy to ensure that all devices are reporting compliance with the updated settings.Prevention
To prevent recurrence of this issue, implement a baseline policy in your environment that explicitly configures TLS inspection proxies and firewall rules for Microsoft Defender ATP. Additionally, use Intune's configuration profiles to enforce consistent proxy configurations across all managed devices. Regularly review network policies and ensure they are up-to-date with the latest requirements from Microsoft.A quick diagnostic shortcut is to temporarily disable any TLS inspection proxies or restrictive firewall rules affecting the Sense service endpoints for a short period to isolate whether these are causing the issue.