Home › Windows Defender Antivirus › 0x80508005

Windows Defender Antivirus · 0x80508005 · Windows 10 / Windows 11 / Windows Server

Defender Error 0x80508005: Engine Gone on Win10/11

MsMpEng.exe crashed due to corrupt signatures or conflicts. Restart service and repair system files.

Error Details

FactValueSourceNote
Exact error code0x80508005Windows Event LogMALWAREPROTECTION_ENGINE_GONE
Affected OS BuildWindows 10/11/ServerOS VersionAll supported builds
Registry KeyHKLM\SOFTWARE\Policies\Microsoft\Windows Defender\DisableAntiSpywareRegistry EditorCheck for third-party AV conflict
Service NameWinDefendServices.mscWindows Defender Antivirus Service
Log SignatureEvent ID 3002 or 3007Microsoft-Windows-Windows Defender/OperationalIndicates signature load failure

Log Files to Check

What This Error Actually Means

The error code 0x80508005, internally mapped to the constant MALWAREPROTECTION_ENGINE_GONE, represents a critical failure state within the Windows Defender Antivirus (WDAV) architecture. This is not merely a transient network timeout or a signature download delay; it indicates that the core antimalware engine process, MsMpEng.exe, has either crashed, failed to initialize, or was forcibly terminated by an external agent. When this error surfaces, the real-time protection subsystem is effectively offline, leaving the endpoint vulnerable to active threats until the service is restored.

In technical terms, this error signifies a breakdown in the communication channel between the Windows Security Center and the Defender engine. The operating system expects MsMpEng.exe to be running and responsive to RPC calls for scanning, definition updates, and policy enforcement. When the process is absent or unresponsive, the system logs Event ID 3007 with this specific hex code, alerting administrators that the "engine is no longer functional." This state often triggers a fallback mechanism where Defender attempts to revert to a known-good set of signatures (Event ID 3002), but if the engine itself cannot load, even this recovery fails. For enterprise administrators, this error is a red flag indicating either severe system corruption, aggressive third-party interference, or misconfigured Group Policy Objects (GPOs) that are actively suppressing the service.

Affected Versions and Scope

This issue affects Windows 10 (all supported builds), Windows 11, and Windows Server 2016/2019/2022 environments where Windows Defender Antivirus is the primary or secondary security layer. The scope is broad, impacting both standalone devices and those managed via Microsoft Intune or Configuration Manager (SCCM). It is particularly prevalent in hybrid Azure AD joined scenarios where policy conflicts between local GPOs and cloud-based Endpoint Protection policies can cause race conditions during service startup.

Devices running Windows 8.1 or earlier are not affected by this specific error code structure, as the underlying engine architecture differs significantly. Furthermore, if a third-party antivirus solution is fully compliant with the Windows Security Service SDK (WSSSDK) and has successfully registered itself as the primary security provider, Defender will be in a "passive mode" rather than an active protection state. In passive mode, 0x80508005 should not occur because the engine is intentionally dormant. Therefore, this error is almost exclusively seen on devices where Defender is expected to be active but has failed to maintain its operational state.

Where To Look First: Logs and Event IDs

To diagnose 0x80508005, you must inspect the Windows Event Log under Applications and Services Logs > Microsoft > Windows > Windows Defender > Operational. The primary indicators are Event ID 3007, which explicitly logs the error code, and Event ID 3002, which often precedes it when signature loading fails. You can query these events directly using PowerShell to filter for the specific hex code:

Get-WinEvent -LogName "Microsoft-Windows-Windows Defender/Operational" | Where-Object {$_.Message -match "0x80508005"} | Select-Object TimeCreated, Id, Message

Additionally, examine the local log file located at C:\ProgramData\Microsoft\Windows Defender\Support\MpCmdRun.log. This file provides granular details about engine initialization failures. Look for lines containing "Failed to start" or "Engine load failed." The raw EVTX file is stored at C:\Windows\System32\winevt\Logs\Microsoft-Windows-Windows Defender%4Operational.evtx, which can be exported for offline analysis if the local machine is inaccessible. In Intune-managed environments, cross-reference these local logs with the device compliance status in the Intune admin center under Devices > Monitor > Device compliance.

Root Causes

Corrupted Signature Database or Engine Files

The most common cause is a corrupted definition update or engine binary. If a signature download is interrupted or disk space is critically low (Defender requires approximately 1 GB free in C:\ProgramData\Microsoft\Windows Defender\), the engine may fail to load the new definitions and crash. You can identify this by checking for Event ID 3002 immediately preceding the 3007 error. The system attempts to revert to a previous signature set, but if the rollback fails due to file corruption, the engine remains offline.

Third-Party Security Product Conflict

A non-compliant third-party antivirus or endpoint detection and response (EDR) agent may forcefully terminate MsMpEng.exe to prevent resource contention. This often occurs when the third-party product does not properly register with the WSSSDK. To detect this, check if any other security software is installed and verify its registration status using Get-MpComputerStatus. If AntivirusEnabled is false but another AV is present, a conflict is likely.

Group Policy or Registry Misconfiguration

If the registry key HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\DisableAntiSpyware is set to 1, Defender is disabled. However, if this value is removed or changed dynamically while the service is running, it can cause a crash. Additionally, aggressive GPOs that restrict network access for MsMpEng.exe can prevent signature updates, leading to engine failure.

Fix Procedure

  1. Restart the Windows Defender Service: Open an elevated PowerShell session and restart the service to clear transient states. Use the following cmdlets:
    Stop-Service -Name WinDefend -Force; Start-Service -Name WinDefend
  2. Verify Service Status: Confirm the service is running and real-time protection is enabled:
    Get-MpComputerStatus | Select-Object RealTimeProtectionEnabled, AntivirusEnabled
  3. Force Signature Update: If the service starts but protection remains off, force a signature update to replace potentially corrupted definitions:
    Update-MpSignature -NotificationAreaToggle $true
  4. Repair System Files: If the engine fails to start, corruption in system files may be the cause. Run DISM and SFC:
    DISM /Online /Cleanup-Image /RestoreHealth
    sfc /scannow
  5. Check Registry Policies: Ensure no local policies are disabling Defender. Verify that HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\DisableAntiSpyware is either absent or set to 0.
  6. Intune Policy Review: In the Intune admin center, navigate to Endpoint Security > Antivirus and ensure no conflicting profiles are assigned. Check the device configuration under Devices > Windows > Configuration profiles.
Warning: Do not manually delete files in C:\ProgramData\Microsoft\Windows Defender\Platform\ unless instructed by Microsoft Support. Removing these files can break the engine entirely and require a full OS repair.

Error Code Variants

Error Code Description Distinguishing Factor
0x80508005 MALWAREPROTECTION_ENGINE_GONE Engine process crashed or failed to start. Critical failure.
0x80508006 MALWAREPROTECTION_ENGINE_NOT_RUNNING Engine is not running but may be in a suspended state. Less severe than 0x80508005.
0x80508007 MALWAREPROTECTION_ENGINE_OUT_OF_DATE Signatures are stale, but the engine is functional. Requires update, not repair.
0x80070005 Access Denied Permission issue preventing service start or file access. Not specific to Defender logic.

Verification

To prove the fix worked, verify that RealTimeProtectionEnabled returns True in PowerShell:
Get-MpComputerStatus | Select-Object RealTimeProtectionEnabled Additionally, check the Event Log for the absence of new 3007 errors. A successful recovery will log Event ID 1123 ("Microsoft Defender Antivirus has successfully updated its virus and spyware definitions"). In Intune, navigate to Devices > Monitor > Device compliance and confirm the device status changes from "Non-compliant" to "Compliant." The Windows Security Center should also display "Real-time protection: On."

Prevention

To prevent recurrence, enforce consistent policy management. Use Intune to deploy a baseline configuration that ensures Defender is always active unless a compliant third-party AV is detected. Configure the OMA-URI ./Device/Vendor/MSFT/Policy/Config/SecurityCenter/AllowEngineUpdates to ensure signature updates are not blocked. Regularly monitor disk space on endpoints, as low disk space is a frequent trigger for engine crashes. Implement automated alerts for Event ID 3007 in your SIEM solution to detect early signs of engine failure before users report issues.

Tip: Use Get-MpThreatDetection to review recent scan results and ensure the engine is actively processing threats after recovery. This confirms full functionality beyond just service status.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.