Fix it now
Microsoft publishes 0x80508023 as ERR_MP_THREAT_NOT_FOUND: the threat might no longer be present on the media, or malware might be stopping you scanning the device. Its documented resolution is to run the Microsoft Safety Scanner, then update your security software and try again.
Update-MpSignature
Start-MpScan -ScanType FullScan
Get-MpThreatDetection | Select-Object -Last 10 ThreatID,Resources,ActionSuccess
- Download a fresh copy of the Microsoft Safety Scanner from Microsoft and run it. It expires ten days after download, so an old copy on the desktop is not a valid test.
- Read its result. Detailed detections are written to %SYSTEMROOT%\debug\msert.log.
- Update definitions with
Update-MpSignature, then run a full scan again and see whether the same code returns. - If the item was on removable media, a network share or a mounted image that has since gone, the code is telling you the truth and there is nothing left to remove.
- If it returns on a fixed disk, run an offline scan with
Start-MpWDOScan, which restarts the machine and scans before Windows loads. - Confirm what actually happened with
Get-MpThreatDetectionrather than trusting the summary line.
Start-MpWDOScan restarts the computer immediately in order to scan outside Windows. Save your work and close everything first.
If a full scan completes and Protection history shows the item resolved, you are done. If not, the next section covers what else the engine reports and what each code means.
Why it happens
The 0x805080xx range comes from Defender’s own engine, and Microsoft publishes meanings for most of it. That matters here because this particular code is widely misdescribed as an aborted scan, and it is not. 0x80508023 is ERR_MP_THREAT_NOT_FOUND, and Microsoft’s stated reason is that the threat might no longer be present on the media, or that malware might be stopping you from scanning your device. The code Microsoft publishes for a scan that failed to complete is a different one: 0x80508018, ERR_MP_SCAN_ABORTED.
Those two readings lead somewhere completely different. “Threat not found” means Defender went to act on something and it was not there – so the first questions are whether the item was on media that has been removed, whether something else already deleted it, and whether the file was on a share or an image that unmounted between detection and remediation. “Scan aborted” would send you at the platform and the scan history. Working the second explanation against the first code is how people end up deleting their detection history for no reason.
The second half of Microsoft’s stated reason is the one to take seriously. Malware that is actively interfering with scanning produces this too, which is why the documented resolution starts with the Microsoft Safety Scanner rather than with anything inside Defender. Safety Scanner is a separate standalone tool with its own definitions, and running it is a genuine second opinion rather than a ritual.
The neighbouring codes fill in what the engine wants next, and they are worth knowing because they are actionable. 0x80508022 is a reboot being required to finish removal. 0x80508024 is a full system scan being required. 0x80508025 is manual remediation steps being required. 0x80508029 is a rescan being required. 0x80508030 is an offline scan being required. Each of those is the engine telling you the specific next step rather than reporting a fault.
The item genuinely is not there any more
You have this one if The detection was on removable media, a network share, a mounted image or a downloads folder that has since been cleared.
- Check where the detection was:
Get-MpThreatDetectionlists the resources involved. - If that path no longer exists or the volume is disconnected, the code is accurate and there is nothing to remediate.
- Reconnect the media and rescan it directly with
Start-MpScan -ScanType CustomScan -ScanPath "E:\"if you want it dealt with properly. - Otherwise clear the entry from Protection history and move on.
Something is interfering with the scan
You have this one if The code returns on a fixed disk, repeatedly, and the machine has other symptoms – slow start-up, unexpected processes, security tools closing on their own.
- Download a fresh Microsoft Safety Scanner and run it. This is Microsoft’s documented resolution for this code.
- Read %SYSTEMROOT%\debug\msert.log for the detail rather than relying on the on-screen summary.
- Update Defender’s definitions with
Update-MpSignatureand run a full scan again. - If it persists, run an offline scan with
Start-MpWDOScanso the engine reads the disk before Windows loads.
Safety Scanner expires ten days after download and does not replace real-time protection. Fetch it fresh each time you need it.
The threat is inside an archive the engine cannot clean in place
You have this one if 0x80508026 alongside, and the detection names a zip, an installer or another container.
- Read the code. 0x80508026 is ERR_MP_REMOVE_NOT_SUPPORTED – removal inside that container type may not be supported.
- Delete the archive yourself, which is what Microsoft suggests for a threat detected inside one.
- Rescan the folder to confirm nothing else is flagged.
The engine ran out of memory or is misconfigured
You have this one if 0x80508007 or 0x80508020 rather than 0x80508023.
- For 0x80508007, ERR_MP_NO_MEMORY: check available memory, close unused applications, restart the device and run the scan again.
- For 0x80508020, ERR_MP_BAD_CONFIGURATION: this is an engine configuration error, commonly related to input data the engine cannot work with. Update definitions and retry.
- If versions will not move at all, reset the platform with
"%ProgramFiles%\Windows Defender\MpCmdRun.exe" -ResetPlatform, restart, and let Windows Update bring it forward again.
The engine is asking for a specific next step
You have this one if A code in the same range that is not one of the above.
- 0x80508022: restart the machine to complete threat removal.
- 0x80508024: run a full system scan.
- 0x80508025: manual remediation steps are required; read the detection detail.
- 0x80508030: run an offline scan with
Start-MpWDOScan.
These are instructions rather than errors. Following them is quicker than treating them as faults.
Full reference
The engine codes Microsoft publishes
| Code | Symbolic name | Microsoft’s stated reason |
|---|---|---|
0x80508007 |
ERR_MP_NO_MEMORY | The device might have run out of memory |
0x8050800C |
ERR_MP_BAD_INPUT_DATA | There might be a problem with your security product |
0x80508020 |
ERR_MP_BAD_CONFIGURATION | An engine configuration error, commonly related to input data the engine cannot work with |
0x80508022 |
ERR_MP_REBOOT_REQUIRED | A reboot is required to complete threat removal |
0x80508023 |
ERR_MP_THREAT_NOT_FOUND | The threat might no longer be present on the media, or malware might be stopping the scan |
0x80508024 |
ERR_MP_FULL_SCAN_REQUIRED | A full system scan is required |
0x80508025 |
ERR_MP_MANUAL_STEPS_REQUIRED | Manual remediation steps are needed |
0x80508026 |
ERR_MP_REMOVE_NOT_SUPPORTED | Removal inside the container type might not be supported |
0x80508027 |
ERR_MP_REMOVE_LOW_MEDIUM_DISABLED | Removal of low and medium threats is disabled |
0x80508029 |
ERROR_MP_RESCAN_REQUIRED | A rescan of the threat is required |
0x80508030 |
ERROR_MP_CALLISTO_REQUIRED | An offline scan is required |
0x80508031 |
ERROR_MP_PLATFORM_OUTDATED | The platform version is unsupported |
0x80508018 |
ERR_MP_SCAN_ABORTED | May trigger when a scan fails to complete |
0x80016CFA is not in Microsoft’s published Defender error tables. If you have it, describe what the machine did rather than what the number means, because nobody outside Microsoft can tell you the second.
Microsoft Safety Scanner, and its limits
- It is a standalone tool that finds and removes malware and attempts to reverse changes made by threats it identifies.
- It expires ten days after download. Fetch a new copy each time rather than keeping one on a USB stick.
- It scans only when you run it. There is no real-time component and it does not replace an antivirus.
- Detailed detections are written to %SYSTEMROOT%\debug\msert.log.
- Removing it is deleting the executable. There is nothing to uninstall.
Commands for working a scan problem
| Command | What it does |
|---|---|
Update-MpSignature |
Updates the antimalware definitions |
Start-MpScan -ScanType FullScan |
Runs a full scan now |
Start-MpScan -ScanType CustomScan -ScanPath "C:\path" |
Scans one path |
Start-MpWDOScan |
Runs an offline scan, restarting the machine to do it |
Get-MpThreatDetection |
Lists active and past detections, with the resources involved |
Get-MpComputerStatus |
Signature, engine and platform versions with timestamps |
MpCmdRun.exe -ResetPlatform |
Resets the platform binaries back to %ProgramFiles%\Windows Defender |
MpCmdRun.exe -GetFiles |
Collects Defender logs into MpSupportFiles.cab for support |
Why an offline scan is the escalation
An offline scan runs before Windows loads, so files held open by running services are readable and anything that depends on a running process to hide itself cannot. That is precisely the situation Microsoft’s stated reason for this code describes – malware stopping you from scanning the device – which is why it is the right escalation rather than a generic “try harder” step. It is slower and it forces a restart, which is why it is not the default.
Repairs to avoid on this code
- Do not turn tamper protection off and delete the contents of the Defender Scans\History folder. Microsoft publishes no such repair for this code, and it destroys your detection and quarantine records for a problem that is not the documented cause.
- Do not add an exclusion to make the code go away. If the documented reason is that something is blocking the scan, excluding it is the opposite of the fix.
- Do not reset the platform as a first move. It is a reasonable step when versions will not advance, and a distraction when the engine is telling you a threat was not found.
- Do not treat a clean summary line as a clean machine while this code is appearing. Read Get-MpThreatDetection.
- Do not reinstall Windows on the strength of one scan code.
When it is worth escalating
- The code returns on a fixed disk after a fresh Safety Scanner run and a definition update.
- An offline scan also reports it.
- Get-MpThreatDetection shows detections whose remediation keeps failing.
- Collect the Defender logs with
MpCmdRun.exe -GetFilesand note the platform, engine and signature versions. - Take that to support, or to whoever runs security in your organisation, rather than continuing to rescan.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x80508023 |
ERR_MP_THREAT_NOT_FOUND: the threat might no longer be present on the media, or malware might be stopping you scanning the device. Microsoft’s resolution is to run the Microsoft Safety Scanner, then update the security software and try again | Microsoft Learn |
0x80508020 |
ERR_MP_BAD_CONFIGURATION: an engine configuration error, commonly related to input data that does not allow the engine to function properly | Microsoft Learn |
0x80508007 |
ERR_MP_NO_MEMORY: the device might have run out of memory. Check available memory, close unused applications, restart and rescan | Microsoft Learn |
0x80016CFA |
Not present in Microsoft’s published Microsoft Defender Antivirus error tables. Describe the behaviour rather than assuming a meaning for it | not published by the vendor |
0x80508026 |
ERR_MP_REMOVE_NOT_SUPPORTED: removal inside the container type might not be supported. Defender cannot remediate a threat inside an archive, so remove the archive yourself | Microsoft Learn |
Confirm the fix worked
- A full scan runs to completion and writes a result you can open in Protection history.
Get-MpThreatDetectionshows the detection resolved rather than repeatedly failing to remediate.- A fresh Microsoft Safety Scanner run reports nothing, with %SYSTEMROOT%\debug\msert.log to back it up.
Get-MpComputerStatusshows current signature, engine and platform versions with recent timestamps.- A second scheduled scan completes unattended, proving the fix holds outside your session.
Questions people ask about this
Does 0x80508023 mean my scan failed?
No. Microsoft publishes it as ERR_MP_THREAT_NOT_FOUND – the threat was no longer on the media, or something is blocking the scan. The published code for a scan that did not complete is 0x80508018, ERR_MP_SCAN_ABORTED.
Does it mean the machine is infected?
Not by itself. Half of Microsoft’s stated reason is benign – the item had gone. The other half is not, which is why the documented next step is a fresh Microsoft Safety Scanner run rather than shrugging.
Should I clear the Defender protection history?
No. That is a repair some articles recommend for this code and Microsoft publishes nothing of the kind. You would lose the record of what was found and quarantined, which is exactly the information you want while investigating this.
Is there anything to buy here?
No. Defender is built into Windows, the Microsoft Safety Scanner is free, and every command in this article is part of the operating system. Fixing a scan code costs nothing but time.
Why does an offline scan help?
It runs before Windows loads, so files locked by running services are readable and nothing can hide behind a running process. That matches the half of Microsoft’s stated reason that involves malware interfering with the scan.
