Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 2001

Defender event ID 2001 and 2003: signature updates fail silently in the log

11 min read Updated October 5, 2026 Antivirus & Endpoint Security

Fix it now

Defender logs 2001 when a security intelligence update fails and 2003 when an engine update fails, and neither reliably raises a warning on screen. Read the timestamps rather than the green tick, then force an update and read the error it returns.

Run these on the failing machine, in an elevated PowerShell window

Get-MpComputerStatus | Format-List AMProductVersion,AMEngineVersion,AntivirusSignatureVersion,AntivirusSignatureLastUpdated,RealTimeProtectionEnabled
Update-MpSignature
  1. Read AntivirusSignatureLastUpdated. That timestamp is the ground truth. Windows Security reports the last successful check, which can be days behind what the log says.
  2. If Update-MpSignature fails, roll the local intelligence back to its default set and pull a fresh copy: "%ProgramFiles%\Windows Defender\MpCmdRun.exe" -RemoveDefinitions -All then the same tool with -SignatureUpdate, in an elevated Command Prompt.
  3. Check the log for 2005 and 2006 before you repeat any of this. Both point at the antimalware platform rather than at the definitions, and clearing definitions will not move either.
  4. Confirm Windows Update and Background Intelligent Transfer Service are running in services.msc, since updates travel through them.

Microsoft recommends running MpCmdRun.exe from the versioned Platform folder, C:\ProgramData\Microsoft\Windows Defender\Platform\<version>, rather than from Program Files. The Program Files copy works, but the Platform copy is the current one.

If the signature timestamp has moved to today and keeps moving, you are done. If not, the next section separates the three things that update independently and shows which one is actually failing.

Why it happens

Defender is three moving parts, not one. The antimalware platform is the client itself and arrives through Windows Update. The engine is the scanning code. The security intelligence is the detection data, and it changes several times a day. Each updates on its own schedule, which is why Microsoft publishes a separate event for each failure rather than one generic update error.

That separation is the whole diagnostic. 2001 is a security intelligence update failure, 2003 an engine update failure, 2006 a platform update failure. The fix for one does nothing for the others, so clearing the local definition store is a reasonable response to a run of 2001 entries and a wasted maintenance window if what you have is 2006.

Two more entries name the state the machine has fallen back into. 2004 means a definition could not be loaded and the engine is attempting to load the last-known good set, so the machine has moved backward rather than merely failed to move forward. 2005 means the engine could not load because the platform is out of date. 3002 is different in kind, and urgent: real-time protection itself encountered an error and failed.

Silence is why these get missed. Defender retries on a schedule, so an intermittent failure fills the log and never produces a visible warning, and the interface goes on showing the result of the last successful check.

The local security intelligence is damaged

You have this one if Every update attempt fails, and AntivirusSignatureLastUpdated has not moved for days on a machine that has been online throughout.

  1. From an elevated Command Prompt: "%ProgramFiles%\Windows Defender\MpCmdRun.exe" -RemoveDefinitions -All.
  2. Immediately run the same tool with -SignatureUpdate so the machine is not left on the default set.
  3. Restart, then re-read Get-MpComputerStatus and confirm the version and timestamp have both moved.

-RemoveDefinitions -All is documented as restoring the installed security intelligence to a previous backup copy or the original default set. It is a rollback, not a deletion, so the machine is never left with nothing.

The platform is out of date and the engine will not load on it

You have this one if 2005 or 2006 in the log, with or without 2001. The engine version in Get-MpComputerStatus is behind and stays behind however many times you refresh definitions.

  1. Let Windows Update run to completion. The platform ships through Windows Update.
  2. If it is wedged, reset the binaries with MpCmdRun.exe -ResetPlatform, then let Windows Update bring it forward again.
  3. Re-read AMProductVersion and AMEngineVersion and confirm both moved.

This is the case that survives every round of clearing definitions, because the definitions were never the problem.

The update transport is not working

You have this one if Other Windows updates also fail or sit pending, or the Windows Update and transfer services are stopped.

  1. In services.msc, confirm Windows Update and Background Intelligent Transfer Service are running and not disabled.
  2. Run sfc /scannow then DISM /Online /Cleanup-Image /RestoreHealth elevated, and restart.
  3. Check free space on the system drive; updates fail quietly with no room to stage them.

The machine is pointed at a source that carries no Defender content

You have this one if The machine is managed and takes updates from an internal server, and the failures are consistent rather than occasional.

  1. Confirm the internal server synchronises Defender security intelligence at all. Many are configured without it.
  2. Give the client somewhere to fall back to: Set-MpPreference -SignatureFallbackOrder "InternalDefinitionUpdateServer|MicrosoftUpdateServer|MMPC".
  3. Prove the path with one named source: Update-MpSignature -UpdateSource MicrosoftUpdateServer.

With no fallback order set, Microsoft documents the default as MicrosoftUpdateServer then MMPC. A policy pinning the client to an internal server only is what turns a missing synchronisation into a silent failure.

The scheduled tasks that trigger updates were disabled

You have this one if Manual updates succeed every time, and the machine never updates on its own between them.

  1. In Task Scheduler, open Task Scheduler Library, Microsoft, Windows, Windows Defender.
  2. Re-enable anything disabled there, then leave the machine for a day.
  3. Check the timestamp the following morning and confirm it moved on its own.

Tuning utilities disable these routinely, and they rarely stop at one.

Full reference

Reading the entries together

Pattern in the log What it means Where to look
2001 occasionally A transient download failure; the next attempt usually succeeds Nowhere yet
2001 several times a day The update channel is genuinely broken Transport, source, proxy
2001 followed by 2004 New data failed to load and the engine went back to the last-known good set Local intelligence store
2003 with no 2001 The engine update failed while intelligence is arriving normally Engine and platform
2005 The engine could not load because the platform is out of date Windows Update
2006 The platform update itself failed Windows Update, disk space
2007 A warning that the platform will soon be out of date Windows Update, before it becomes 2005
3002 Real-time protection encountered an error and failed Treat as the priority

The commands worth knowing

Command What it does
Get-MpComputerStatus Product, engine and signature versions, the last-updated timestamps, and whether real-time protection is on
Update-MpSignature Checks for and applies new security intelligence now
Update-MpSignature -UpdateSource MMPC Forces the attempt against one named source, which is how you prove where the failure is
MpCmdRun.exe -RemoveDefinitions -All Restores the installed security intelligence to a previous backup copy or the original default set
MpCmdRun.exe -RemoveDefinitions -Engine Restores the previously installed engine, which is the narrower move when 2003 is the only entry
MpCmdRun.exe -SignatureUpdate Checks for new security intelligence; -MMPC and -UNC pin the source
MpCmdRun.exe -ResetPlatform Resets platform binaries back to %ProgramFiles%\Windows Defender
MpCmdRun.exe -GetFiles Collects the Defender logs into a support cab under C:\ProgramData\Microsoft\Windows Defender\Support

There are two copies of MpCmdRun.exe on a healthy machine: one in C:\Program Files\Windows Defender and one under C:\ProgramData\Microsoft\Windows Defender\Platform\<version>. Microsoft recommends the Platform copy because it is the current build. If the two behave differently, that difference is itself a platform problem.

Update sources, and the order they are tried in

Set-MpPreference -SignatureFallbackOrder takes a pipe-separated list, and Defender stops as soon as one source works. The documented values are InternalDefinitionUpdateServer, MicrosoftUpdateServer, MMPC and FileShares, and with nothing set the order is MicrosoftUpdateServer then MMPC. On a managed estate the useful shape is the internal server first with Microsoft behind it, so a laptop off the corporate network still updates.

Set-MpPreference -SignatureUpdateInterval exists as well and controls how often the client checks. Microsoft documents it only as the signature update interval, so treat it as a dial to shorten on machines that are rarely connected, and not as a fix for a channel that is broken. A shorter interval on a broken channel produces more 2001 entries, not fewer.

When the common causes are all ruled out

  • Check the machine’s date and time. Certificate validation on the download path fails on a badly wrong clock, and the failure surfaces as a plain update error.
  • Collect the logs with MpCmdRun.exe -GetFiles before you make more changes. It writes MpSupportFiles.cab, and it is the thing support will ask for.
  • Look at what else is filtering traffic. A proxy substituting its own certificate mid-download produces consistent failures that look nothing like a proxy problem from the endpoint.
  • Confirm real-time protection is actually on with Get-MpComputerStatus. A machine logging 3002 has a runtime failure to fix before the update question matters at all.
  • On a server, confirm the role is installed and the service is running before chasing the update path; a Defender that is not running cannot fail to update in the way this article describes.

How far behind is too far behind

Security intelligence changes several times a day, so a week is a meaningful gap and a fortnight is a serious one. Cloud-delivered protection covers part of the gap while the machine is online and reachable, but it is a supplement rather than a substitute: a machine that is offline, or whose outbound path is blocked, has only what is on the disk. The practical rule is that the timestamp should never be more than a day or two old on a machine that is switched on.

Every code this article covers

Code What it points at Source
2001 The security intelligence update failed Microsoft Learn
2003 The antimalware engine update failed, which is a different operation from a signature update Microsoft Learn
2004 A definition could not be loaded, so the engine attempts to load the last-known good set Microsoft Learn
3002 Real-time protection encountered an error and failed Microsoft Learn
2005 The engine failed to load because the antimalware platform is out of date; the platform loads the last-known good engine and attempts to update Microsoft Learn
2006 The platform update failed. This is a platform problem, not a definitions problem Microsoft Learn

Confirm the fix worked

  1. Get-MpComputerStatus shows an AntivirusSignatureLastUpdated timestamp from today.
  2. AMProductVersion and AMEngineVersion are current, which is what rules 2005 and 2006 back out.
  3. The Defender operational log records successful update events instead of repeating 2001, 2003 or 2006.
  4. RealTimeProtectionEnabled reports True, with no new 3002 entries since the restart.
  5. The machine updates unattended overnight, with nobody running a command.

Questions people ask about this

Windows Security says I am protected. Should I believe it?

Believe the timestamp instead. Get-MpComputerStatus reports when security intelligence was last updated, and the interface reports the last successful check, which can be days older than what the log is telling you.

Does any of this cost money?

No. Microsoft Defender Antivirus and its security intelligence are part of Windows, and every command here is built in. There is no product that makes a failed update succeed.

What is the difference between 2001, 2003 and 2006?

They are three different components. 2001 is the detection data, 2003 is the scanning engine, and 2006 is the antimalware platform that hosts both. Clearing definitions addresses the first and does nothing for the other two, which is why the same fix keeps being applied to a machine that keeps failing.

Is 2004 serious on its own?

It is worse than 2001, because it means the engine has gone back to the last-known good set rather than simply failing to move forward. One after a bad download is normal. A run of them means the machine is being protected by older data than the day before.

Should I set a shorter update interval?

On laptops that are rarely on the network it is a reasonable adjustment. On an always-on desktop the default is fine, and shortening the interval on a broken channel just produces more failed attempts.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error Avira says your licence has expired and protection features are locked Free Fix Malwarebytes Runtime Error 0 and error 502 during install or upgrade License Error Panda subscription expired: Panda Dome drops to limited free protection Free Fix Norton error 3048 3: your Norton product is damaged and needs repair
โ† Back to Knowledge Base