Additional Microsoft Defender tools and services that provide security across various platforms and environments
The provided context does not define error code 0x8050111c for MpCmdRun.exe, so its specific meaning cannot be stated from the available information.
However, the context does describe how Defender scans behave when started via MpCmdRun and how to investigate scan failures:
-
MpCmdRun-based scans (including scheduled scans) are subject to time limits:- Quick scans: 1‑day limit
- Full scans: 7‑day limit
If a scan exceeds these limits, it is canceled. This can appear as a failed scan when using
MpCmdRuneven though the Defender engine itself is functional.
- Other common reasons scans are canceled or terminated include:
- Device restarts during the scan
- Device running on battery during a scheduled full scan
- Other power‑state changes (sleep/hibernate/Modern Standby) during the scan
- To investigate what is happening on the device when the scan fails, review the Defender and system event logs:
- Open Event Viewer → Application and Service Logs → Microsoft → Windows → Windows Defender → Operational and look for scan events (for example, Event ID 1000) around the time the
MpCmdRunscan fails. - Also review the System log for restart or power‑related events (IDs 6005, 6006, 6007, 6008, 42, 105, 107, 506, 507) that might interrupt the scan.
- The same information can be obtained via PowerShell:
# All Defender operational events Get-WinEvent -LogName 'Microsoft-Windows-Windows Defender/Operational' # Only scan events Get-WinEvent -LogName 'Microsoft-Windows-Windows Defender/Operational' | where id -eq '1000'
- Open Event Viewer → Application and Service Logs → Microsoft → Windows → Windows Defender → Operational and look for scan events (for example, Event ID 1000) around the time the
- If Defender is generally encountering errors during scans or malware removal (not just timeouts), the context recommends:
- Running Windows Update to ensure the Defender platform, engine, and signatures are fully up to date.
- If update errors occur, manually installing the latest protection updates from the Microsoft Malware Protection Center.
Given the context, the next concrete steps are:
- Use Event Viewer or
Get-WinEventto confirm whether theMpCmdRunscan is being canceled due to timeout or power/restart events. - Ensure the device remains powered, plugged in, and awake for the duration of the scan.
- Run Windows Update and, if needed, manually update Defender protection components.
The contents of MpCmdRun.log are not described in the context, so they cannot be interpreted here, but correlating its timestamps with the Defender and System event logs should help pinpoint the cause.
References: