Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | The application failed to initialize properly (0x800106BA) | System Event Log | Event ID 7031 or 7024 |
| Affected OS Build Range | Windows 10, Windows 11, Windows Server | Product Documentation | All supported versions |
| Registry Key Override | HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\DisableAntiSpyware | Registry Editor / GPO | Value set to 1 disables service |
| Relevant Service Name | WinDefend | Services.msc / PowerShell | Windows Defender Antivirus Service |
| Log Line Signature | Event ID 5010: Scanning for malware... is disabled | Microsoft-Windows-Windows Defender/Operational | Indicates passive mode or failure |
Log Files to Check
C:\Windows\System32\winevt\Logs\System.evtxC:\Windows\System32\winevt\Logs\Microsoft-Windows-Windows Defender%4Operational.evtx
What This Error Actually Means
The error code 0x800106BA, accompanied by the descriptive string "The application failed to initialize properly," is a critical failure indicator within the Windows Endpoint Security stack. Specifically, this HRESULT denotes that the Windows Defender Antivirus service (WinDefend) attempted to start but encountered an initialization failure before it could fully load its core components. This is not merely a transient network timeout; it signifies that the service executable (MsMpEng.exe) crashed during its startup sequence or was forcibly terminated by the Service Control Manager (SCM) due to a configuration conflict or corruption.
In the context of enterprise endpoint management, this error effectively renders the device unprotected against real-time threats. The WinDefend service is responsible for coordinating file system filtering, network inspection, and cloud-delivered protection. When this service fails with 0x800106BA, the Windows Security Center (wscsvc) detects the absence of a valid antimalware provider and may report that real-time protection is disabled. This state often triggers compliance alerts in Microsoft Intune or SCCM, flagging the device as non-compliant with security baselines. The error originates from the SCM's attempt to transition the service state from STOPPED to RUNNING, failing at the initialization handshake where the service registers its filters and connects to the cloud infrastructure.
Affected Versions and Scope
This error is prevalent across modern Windows operating systems, specifically affecting Windows 10 (versions 1809 and later), Windows 11 (all releases), and Windows Server 2019/2022. The scope of impact is broad because the underlying architecture of Microsoft Defender Antivirus has remained consistent across these builds, relying on the same service registration mechanisms. However, the frequency of this error often correlates with specific tenant configurations rather than OS bugs.
Devices managed via Microsoft Intune using Endpoint Security profiles are particularly susceptible if there are conflicting policies between Group Policy Objects (GPO) and MDM settings. For instance, a device enrolled in both Active Directory and Entra ID may receive contradictory instructions regarding the DisableAntiSpyware registry key. Furthermore, this error is frequently observed in environments where third-party antivirus solutions have been recently uninstalled or failed to deregister properly from the Windows Security Center. It is important to note that standalone, non-domain-joined devices running default configurations rarely encounter this specific initialization failure unless malware has actively tampered with system files.
Where To Look First: Logs and Event IDs
To diagnose the root cause of 0x800106BA, administrators must correlate events from two distinct log sources. The primary source is the System event log, located at C:\Windows\System32\winevt\Logs\System.evtx. Here, you should look for Event ID 7031 or Event ID 7024. These events are generated by the Service Control Manager and will explicitly state: "The Windows Defender Antivirus Service service terminated with the following error: The application failed to initialize properly (0x800106BA)." This confirms that the SCM detected the crash.
The secondary, and often more informative, source is the Microsoft-Windows-Windows Defender Operational log, located at C:\Windows\System32\winevt\Logs\Microsoft-Windows-Windows Defender%4Operational.evtx. In this log, search for Event ID 5010, which contains the signature: "Scanning for malware and other potentially unwanted software is disabled." This event indicates that the service recognized a policy override or a conflicting provider and intentionally shut down its scanning engines. To quickly extract these events, use the following PowerShell cmdlet:
Get-WinEvent -LogName "System" | Where-Object {$_.Id -eq 7031 -or $_.Id -eq 7024} | Select-Object TimeCreated, Message
Root Causes
Group Policy or MDM Override
The most common cause is an explicit policy disabling Defender. This can occur via a legacy GPO setting "Turn off Microsoft Defender Antivirus" or an Intune Endpoint Security profile that inadvertently disables real-time protection. When this registry key HKLM\SOFTWARE\Policies\Microsoft\Windows Defender\DisableAntiSpyware is set to 1, the service refuses to initialize, resulting in the 0x800106BA error.
Conflicting Third-Party Antivirus
If a third-party antivirus product is installed but fails to register correctly with the Windows Security Center, Defender may enter a confused state. Defender attempts to start, detects another provider claiming control, and then fails to initialize because it cannot determine its operational mode (active vs. passive). This often happens after a failed uninstall of a competitor AV.
Corrupted Service Registration
A failed Windows Update or a system file corruption can damage the service registration for WinDefend. If the SCM cannot locate the executable path or if the dependencies (such as wscsvc) are missing, the initialization fails immediately. This is less common but critical in server environments where updates are applied manually.
Fix Procedure
- Check for Policy Overrides: Run
gpresult /h gp_report.htmland review the Computer Configuration section. Look for "Turn off Microsoft Defender Antivirus." If present, remove the GPO or update the Intune profile. In Intune admin center, navigate to Devices > Configure > Endpoint security > Antivirus and ensure real-time protection is enabled. - Clear Registry Overrides: Open an elevated PowerShell session and run:
Remove-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows Defender" -Name "DisableAntiSpyware" -ErrorAction SilentlyContinueThis ensures no local registry override is forcing the service to stop. - Reset Service State: Ensure the Windows Security Center is running, as Defender depends on it. Run:
Start-Service wscsvc -ForceThen, attempt to start Defender:Start-Service WinDefend - Repair System Files: If the service still fails, run a system file check to repair potential corruption in the service binaries:
sfc /scannowAfter completion, reboot the device. - Verify Intune Compliance: If managed by Intune, force a sync and check compliance. Use the Graph API to verify the device's security state:
Invoke-MgGraphRequest -Method GET -Uri "https://graph.microsoft.com/v1.0/deviceManagement/managedDevices" | Select-Object id, deviceName, osVersion
WinDefend service key from the registry (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinDefend). Doing so will break the Windows Security Center integration and may require a full OS repair to restore. Always use PowerShell or GPO to manage the service state.
Error Code Variants
| Error Code | Description | Distinguishing Factor |
|---|---|---|
0x800106BA |
Initialization Failure | Service crashes during startup; often due to policy conflicts or corruption. |
0x80070005 |
Access Denied | Permission issue; usually occurs when a non-admin user tries to modify Defender settings. |
0x80070422 |
Service Not Running | The service is stopped but not crashed; often due to a disabled startup type. |
Verification
To verify the fix, first check the service status using PowerShell:
Get-Service WinDefend | Select-Object Status, StartType
The status should be Running and StartType should be Automatic. Next, confirm that real-time protection is active by running:
Get-MpComputerStatus | Select-Object RealTimeProtectionEnabled
This should return True. Finally, check the Operational log for Event ID 5010. If the fix was successful, you should no longer see recent entries indicating that scanning is disabled. Instead, you may see Event ID 5007 ("Antimalware platform has been started"), confirming healthy initialization.
Prevention
To prevent recurrence, implement a baseline configuration in Microsoft Intune that explicitly enables real-time protection and cloud-delivered protection. Use the OMA-URI ./Device/Vendor/MSFT/WindowsDefender/RealTimeProtection/EnableRealtimeProtection to enforce this setting across all managed devices. Additionally, monitor for third-party antivirus installations using compliance policies. If a device installs an unauthorized AV, trigger an automatic remediation script that uninstalls the conflicting software and re-enables Defender. Regularly audit GPOs to ensure no legacy policies are overriding MDM settings, as GPO takes precedence over MDM in hybrid environments.
dsregcmd /status command to quickly verify if a device is properly enrolled in Entra ID. Misconfigured enrollment can sometimes lead to policy application failures, which may indirectly cause Defender initialization issues if security policies are not delivered correctly.