Skip to content

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

Your vault is empty.

Free Fix 0x80072EE2

Microsoft Defender error 0x80072EE2: definition downloads time out every time

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

Fix it now

0x80072EE2 is the HRESULT form of WinINet 12002, ERROR_INTERNET_TIMEOUT: the request timed out. Defender asked for a definition package and nothing came back in time, which points at the path between the machine and Microsoft rather than at the antivirus.

Run the first two in an elevated Command Prompt and the last two in elevated PowerShell

netsh winhttp show proxy
w32tm /resync
Update-MpSignature
Get-MpComputerStatus | Select-Object AntivirusSignatureVersion,AntivirusSignatureLastUpdated
  1. Check the clock. Turn on automatic time in Settings, Time and language, Date and time, then run w32tm /resync. Certificate validation fails on a machine with the wrong date, and updates are simply the first thing you notice.
  2. Read netsh winhttp show proxy. Services run in the system context and use that setting, not the one in your browser.
  3. If the network requires a proxy and this reports direct access, set it: netsh winhttp import proxy source=ie copies the current user configuration into the system one.
  4. Retry with Update-MpSignature and read the error it returns rather than the one in Windows Update.
  5. If a gateway inspects TLS, ask for Microsoft’s update endpoints to be excluded from inspection rather than working around it on the client.
  6. Confirm with Get-MpComputerStatus that the signature timestamp has moved to today.

w32tm /resync is the whole command. There is no /force parameter; w32tm rejects an unrecognised switch, prints its usage and never attempts the resynchronisation.

If the signature timestamp moves, you are done. If not, the next section works through which layer is refusing.

Why it happens

Defender fetches signature packages over HTTPS. Depending on configuration, that traffic goes through the Windows Update transport, through an internal update server, or directly to Microsoft’s malware protection endpoints. All of those requests are made by services running under the machine account rather than by anything in your user session.

That distinction causes most of these failures. The proxy you configure in a browser, or in the network settings of your profile, applies to your session. A service uses the WinHTTP proxy configuration, which is a separate setting that has to be populated deliberately. The result is a machine where the web works perfectly and Defender times out every time, which sends people hunting for a fault inside the antivirus that is not there.

The companion codes come from different layers and are worth reading carefully. 0x8024402C is WU_E_PT_WINHTTP_NAME_NOT_RESOLVED – the same as ERROR_WINHTTP_NAME_NOT_RESOLVED, meaning the proxy server or target server name cannot be resolved. 0x80248014 is WU_E_DS_UNKNOWNSERVICE, an operation that did not complete because the service is not in the data store. 0x80072EF1 is WinINet 12017, the operation cancelled, usually because the handle it was running on was closed before it completed.

Event 2004 in the Defender operational log is the one most often misread. Microsoft publishes it as MALWAREPROTECTION_SIGNATURE_REVERSION: there was a problem loading antimalware definition, and the engine attempts to load the last-known good set. It is about definitions that would not load, not about definitions that would not download. If you are seeing 2004 rather than 2001, the package arrived and the engine could not use it, which is a different investigation.

System-context requests have no proxy

You have this one if Everything else on the machine reaches the internet, but netsh winhttp show proxy reports direct access on a network that requires a proxy.

  1. Run netsh winhttp import proxy source=ie from an elevated Command Prompt to copy the user configuration across.
  2. Or set it explicitly: netsh winhttp set proxy proxy-server="host:port" bypass-list="<local>".
  3. Retry Update-MpSignature and see whether the timeout is replaced by success or by a different error.
  4. Where Defender needs its own proxy rather than the system one, Set-MpPreference -ProxyServer sets it.

The system clock or time zone is wrong

You have this one if The date or time is visibly out, the machine has been off for a long period, or its battery-backed clock is failing.

  1. Turn on automatic time and time zone in Settings.
  2. Run w32tm /resync in an elevated Command Prompt and read what it reports.
  3. If the service is not running, start it with net start w32time and resync again.
  4. If the clock drifts back after every shutdown, the motherboard battery is the likely culprit and no software fix will hold.

Certificate validation depends on the current time being roughly correct. A machine that thinks it is in the wrong year cannot open a trusted connection to anything.

A TLS-inspecting appliance breaks the connection

You have this one if Updates fail only on the corporate network and succeed on a mobile hotspot or at home.

  1. Confirm the difference by testing on another network before changing anything.
  2. Ask whoever runs the gateway to exclude Microsoft’s update and malware protection endpoints from inspection.
  3. Do not solve it by disabling certificate checks on the client; that trades a broken update channel for a worse problem.
  4. Retest after the exclusion is in place.

The update source has nothing to give

You have this one if The machine is managed and points at an internal update server, and 0x8024402C or 0x80248014 appear alongside the timeout.

  1. Read the current order with Get-MpPreference before changing it.
  2. Confirm whether the internal server actually synchronises Defender definition content.
  3. Set an order that includes a fallback: Set-MpPreference -SignatureFallbackOrder "InternalDefinitionUpdateServer|MicrosoftUpdateServer|MMPC".
  4. Retry the update and confirm the signature timestamp moves.

The documented default is already MicrosoftUpdateServer | MMPC, so setting exactly that changes nothing on a machine with no explicit configuration. Add InternalDefinitionUpdateServer at the front only where there really is one.

The connection is metered or otherwise deferred

You have this one if The machine is on mobile broadband or a hotspot, and background downloads never complete.

  1. Check whether the connection is marked as metered in Settings, Network and internet.
  2. Force an update with Update-MpSignature rather than waiting for the background schedule.
  3. Where the machine lives on a metered link, consider a UNC or MMPC source rather than the default transport.

Full reference

Where each of these five codes comes from

Code Published as What it tells you
0x80072EE2 WinINet 12002, ERROR_INTERNET_TIMEOUT – the request has timed out Nothing answered in time
0x8024402C WU_E_PT_WINHTTP_NAME_NOT_RESOLVED – the proxy server or target server name cannot be resolved Name resolution, or a proxy name that is wrong
0x80248014 WU_E_DS_UNKNOWNSERVICE – the operation did not complete because the service is not in the data store The update client has no record of the service it was told to use
0x80072EF1 WinINet 12017, ERROR_INTERNET_OPERATION_CANCELLED – the operation was cancelled, usually because the handle was closed before it completed Something ended the request early
Event 2004 MALWAREPROTECTION_SIGNATURE_REVERSION – there was a problem loading antimalware definition; the engine attempts to load the last-known good set Definitions that would not load, not a download failure

The tools for this job

Command What it tells you or does
netsh winhttp show proxy The proxy configuration services actually use
netsh winhttp import proxy source=ie Copies the user proxy configuration into the system one
w32tm /resync Resynchronises the clock against the configured source
Update-MpSignature Attempts a definition update now and reports the failure directly
Get-MpComputerStatus Signature, engine and platform versions with their timestamps
Get-MpPreference The configured fallback order, proxy and update settings
Set-MpPreference -SignatureFallbackOrder Sets the order of definition sources

w32tm validates its arguments strictly. w32tm /resync /force is not a valid command: /force is not among the documented parameters, and w32tm reports the argument as unexpected, prints its usage block and exits without resynchronising anything.

The definition sources you can choose between

Value What it means
InternalDefinitionUpdateServer An internal update server such as WSUS
MicrosoftUpdateServer Microsoft Update
MMPC The Microsoft Malware Protection Center
FileShares A UNC file share holding the definition packages

Defender contacts them in the order given, separated by pipe characters, and stops at the first that delivers. The documented default where nothing is set is MicrosoftUpdateServer followed by MMPC. That matters because setting exactly the default is a common piece of advice that does nothing at all – the useful change is either putting an internal server in front of it, or adding a FileShares source for machines that cannot reach Microsoft.

Which layer is failing

What you find Where the fault is
Browsing works, netsh winhttp show proxy reports direct access The system proxy is not configured and services cannot get out
The system clock is well out Certificate validation fails, so no secure connection is established
A TLS-inspecting appliance is in the path The substituted certificate is not accepted by the update client
The machine points at an internal update server That server may hold no Defender content; the fallback order decides what happens next
The connection is marked as metered Windows defers background downloads on that connection
Event 2004 rather than 2001 The package arrived and would not load. This is not a transport problem

A manual update as a stopgap

Microsoft publishes standalone security intelligence packages that can be run on a machine which cannot reach the update service, and MpCmdRun.exe -SignatureUpdate -UNC <path> will pull from a file share you populate yourself. Both are reasonable for an isolated machine and neither fixes the channel, so treat them as a way of buying time rather than as the answer.

Checks to make before blaming the network

  • Test on a hotspot. It separates client from network in one step.
  • Check the clock in UTC rather than by looking at the tray, because a wrong time zone and a wrong time look identical there.
  • Read the update stage from event 2001 in the Defender operational log; a failure at Download and a failure at Install are different problems.
  • Confirm whether the machine is managed. A policy pointing at an update server that no longer exists produces this permanently and silently.
  • Check whether anything else on the machine is failing to reach Microsoft. If Windows Update itself is broken, this is a symptom rather than the problem.

Every code this article covers

Code What it points at Source
0x80072EE2 The HRESULT form of WinINet 12002, ERROR_INTERNET_TIMEOUT: the request has timed out Microsoft Learn
0x8024402C WU_E_PT_WINHTTP_NAME_NOT_RESOLVED: the same as ERROR_WINHTTP_NAME_NOT_RESOLVED – the proxy server or target server name cannot be resolved Microsoft Learn
0x80248014 WU_E_DS_UNKNOWNSERVICE: an operation did not complete because the service is not in the data store Microsoft Learn
Event ID 2004 MALWAREPROTECTION_SIGNATURE_REVERSION: there was a problem loading an antimalware definition and the engine attempts to load the last-known good set. It records definitions that would not load, not a download that failed Microsoft Learn
0x80072EF1 The HRESULT form of WinINet 12017, ERROR_INTERNET_OPERATION_CANCELLED: the operation was cancelled, usually because the handle it was running on was closed before it completed Microsoft Learn

Confirm the fix worked

  1. Get-MpComputerStatus shows a signature timestamp from today.
  2. Update-MpSignature completes without returning an error.
  3. The Defender operational log records a successful update rather than repeat entries at 2001 or 2004.
  4. netsh winhttp show proxy reports the configuration you intended.
  5. The same update succeeds after a restart, proving the proxy or time setting persisted rather than applying only for the session.

Questions people ask about this

Does fixing this cost anything?

No. Defender ships with Windows and its definitions are free. Everything here is network configuration and built-in tooling. There is no licence that makes a timeout go away.

Why does the browser work when Defender cannot download?

Because they use different proxy settings. Your browser uses the user session configuration; Defender’s services use the WinHTTP system configuration. Populating the second one is the fix in a large share of these cases.

Is w32tm /resync /force the command I want?

No. /force is not a documented parameter of w32tm /resync – the documented ones are /computer:, /nowait, /rediscover and /soft. Given an unrecognised switch, w32tm reports the argument as unexpected, prints its usage and exits without resynchronising. Use w32tm /resync.

Can I just download definitions by hand?

Microsoft publishes standalone security intelligence packages, and MpCmdRun can pull from a UNC share. Both are reasonable stopgaps for an isolated machine, and neither repairs the channel.

I see event 2004, not 2001. Is that the same problem?

No. 2004 records a problem loading a definition and the engine reverting to the last-known good set, which means the package arrived. Look at the platform and the definition store rather than at the network.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix Kaspersky says databases are corrupted and updates keep failing License Error Defender event 5001: real-time protection off while another antivirus holds the registration License Error Microsoft Defender real-time protection will not turn on: what 0x800106BA really is License Error Bitdefender threat scanner cannot be initialized: the scan engine never loads
โ† Back to Knowledge Base