Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | This operation returned because the timeout period expired. (0x800705B4) | Event Viewer - System Logs, Event ID 7000/7011 | -> Indicates service start failure |
| Affected OS build range | Windows 10/11 | Microsoft Defender for Endpoint documentation | -> Applies to all supported versions |
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender\Scan\ScanOnlyIfIdle | Windows Registry | -> May cause timeout if set too short |
| Relevant service endpoint URL | *.endpoint.security.microsoft.com | Network connectivity check | -> Must be accessible for MDE onboarding |
| Log line signature | Timeout occurred during platform update or scan operation | MpSupportFiles.cab - MPLog-<date>.log | -> Indicates specific timeout location in logs |
Log Files to Check
C:\ProgramData\Microsoft\Windows Defender\Support\MpSupportFiles.cabC:\ProgramData\Microsoft\Windows Defender Advanced Threat Protection\Logs\MSSense.log
What This Error Actually Means
The error code
0x800705B4, which translates to "This operation returned because the timeout period expired," is raised when a critical component of Microsoft Defender for Endpoint (MDE) fails to complete an expected action within its designated time frame. This can occur during various operations such as service startup, platform updates, real-time protection scans, or remediation actions. The primary components that may raise this error are the Windows Defender Antivirus Service (
WinDefend) and the Microsoft Defender for Endpoint sensor service (
SENSE). When either of these services times out during initialization or an ongoing operation, it triggers a timeout event, leading to the 0x800705B4 error.
Affected Versions and Scope
This issue affects Windows 10 and Windows 11 operating systems where Microsoft Defender for Endpoint is enabled. The problem can manifest in both on-premises environments and cloud-managed devices through Intune or other management solutions. It does not affect earlier versions of Windows (such as Windows 7) that do not support MDE, nor does it impact macOS or Linux endpoints managed by MDE.
Where To Look First: Logs and Event IDs
To diagnose the root cause of this error, start by examining the following logs:
C:\ProgramData\Microsoft\Windows Defender\Support\MpSupportFiles.cab
C:\ProgramData\Microsoft\Windows Defender Advanced Threat Protection\Logs\MSSense.log
In
Event Viewer > Windows Logs > System, look for Event IDs 7000 and 7011 from the source Service Control Manager. These events will describe service start failures with the error message "This operation returned because the timeout period expired." Additionally, check the
MpSupportFiles.cab archive for the
MPLog-.log file inside, where you should filter for lines containing 'Timeout' or 'error'. In the
MSSense.log, search for similar timeout entries.
Root Causes
Third-party Antivirus Conflicts
When a third-party antivirus product is installed alongside Microsoft Defender, it can cause conflicts during service startup. This often results in Defender entering passive mode and the SENSE sensor timing out during state negotiation. To identify this issue, run
Get-MpComputerStatus | Select-Object AntivirusProduct, AMRunningMode. If
AMRunningMode is 'Passive Mode', another AV product is likely preventing Defender from starting properly.
Network Connectivity Issues
If the Windows Defender services fail to download updates or communicate with Microsoft's servers due to network restrictions, this can lead to timeout errors. Check connectivity to
go.microsoft.com and
ctldl.windowsupdate.com using
Test-NetConnection -ComputerName go.microsoft.com -Port 443. Ensure that the firewall or proxy settings allow access to URLs like
*.endpoint.security.microsoft.com,
*.wdcp.microsoft.com, and
*.wd.microsoft.com.
Driver Conflicts with WdFilter Driver
Conflicts between the Windows Defender Minifilter driver (
WdFilter.sys) and other drivers (such as backup agents or security products) can cause deadlocks, leading to timeout errors during real-time protection scans. Use
fltmc instances in an elevated command prompt to list all minifilter drivers and identify potential conflicts.
Fix Procedure
Restart the Defender services: In an elevated PowerShell session, run:
Restart-Service WinDefend
Restart-Service Sense
- If a third-party AV is causing conflict, uninstall it and then run:
Start-MpWDOScan
This command restores Defender to active mode.
- To force a platform update, execute the following in an elevated command prompt:
MpCmdRun.exe -SignatureUpdate
If this times out, ensure network connectivity as described above and allow necessary URLs through your firewall or proxy settings.
- Remove conflicting minifilter drivers by disabling non-essential third-party filters temporarily. Use
fltmc instances to list all minifilter drivers and disable problematic ones.
Error Code Variants
| Error Code | Description |
0x800705B4 | This operation returned because the timeout period expired. |
0x80072EEF | The service did not respond to multiple start requests in a timely fashion. |
0x8007139F | The specified network name is no longer available. |
Verification
To verify that the issue has been resolved, run
Get-MpComputerStatus in PowerShell and confirm that
AntivirusEnabled=True,
RealTimeProtectionEnabled=True, and
NISEnabled=True. Additionally, check Event Viewer > Windows Defender > Operational for Event ID 2000 (signature update succeeded) to ensure no further timeout errors are occurring in the Service Control Manager log.
Prevention
To prevent recurrence of this issue, implement policies that restrict third-party antivirus installations alongside Microsoft Defender. Use OMA-URI .Device/Vendor/MSFT/Policy/Defender/AntivirusDisableThirdPartyAntivirus in Intune to enforce this policy. Additionally, ensure proper network configurations allow necessary traffic for Defender updates and communications with Microsoft's servers.
Restarting services can temporarily break enrolled devices if not done carefully.
Use Get-MpComputerStatus to quickly check the current status of Windows Defender without diving into logs.