If a Microsoft Defender Antivirus update appears stuck, open Windows Security > Virus & threat protection > Protection updates and select Check for updates. If the check fails or leaves you on an older definition version, confirm that the Defender service is running and that Windows Update and BITS can start if your PC uses Microsoft Update. Then run Update-MpSignature in Windows PowerShell as an administrator and compare the installed signature version before and after. These steps apply to Windows 11 and Windows 10 PCs that use Microsoft Defender Antivirus.

A Windows 11 PC shows Microsoft Defender security intelligence up to date, confirmed by PowerShell commands. Before you troubleshoot Defender updates​

  • Confirm which antivirus is in charge. In Windows Security > Virus & threat protection, look under Who’s protecting me? and select Manage providers. If another antivirus is your primary provider, update that product through its own controls. On a work PC, Defender can also be running in passive mode by design. Don’t treat either setup as a stuck Defender update or try to switch antivirus providers to complete this guide.
  • Have an administrator account and a connection to the update source. A personal PC normally gets security intelligence through Microsoft Update. A work or school PC may get it from an internal update server or a network share. Use the organization’s approved connection and leave its update policy in place.
  • On Windows 10, distinguish Defender updates from Windows updates. Standard support for Windows 10 Home and Pro ended on October 14, 2025. Microsoft says it will continue providing security intelligence updates for built-in Defender Antivirus on Windows 10 through October 2028. Receiving new definitions does not mean the operating system itself is receiving security fixes.

Check for definitions in Windows Security​

  1. Open Windows Security. On either Windows version, open Start, type Windows Security, and select the app. If you prefer Settings, the paths differ:
    • Windows 11: Start > Settings > Privacy & security > Windows Security.
    • Windows 10: Start > Settings > Update & Security > Windows Security.
  2. Select Virus & threat protection. Under Virus & threat protection updates, select Protection updates. Note the installed Security intelligence version and the last-updated date before requesting an update. That gives you a baseline even if the progress indicator never clears.
  3. Select Check for updates. When the check finishes, compare the version and date with what you recorded. A newer version confirms Defender installed new definitions. If the check finishes without an error and the version is unchanged, your update source may simply have nothing newer. If the check does not finish, shows an error, or leaves you with definitions you know are out of date, continue to the service checks.

Confirm the services needed for the update can run​

  1. Open Start, type Windows PowerShell, right-click Windows PowerShell, and select Run as administrator. Approve the prompt or enter administrator credentials. Keep this window open for the update and verification.
  2. Run this read-only command:
    Code:
    Get-Service -Name WinDefend, wuauserv, BITS |
        Format-Table -AutoSize DisplayName, Name, StartType, Status
    Read the Status and StartType columns separately:
    Service nameWhat to look for
    WinDefendMicrosoft Defender Antivirus Service should show Running when Defender is your active antivirus. If it is stopped, recheck the provider before assuming the service has failed.
    wuauservWindows Update is part of the Microsoft Update path. If that path is failing, check that the service can start.
    BITSBackground Intelligent Transfer Service is another service Microsoft lists for that path. It can start on demand, so an idle Stopped status alone does not establish a fault.
  3. If Microsoft Update is your source, the update is failing, and either wuauserv or BITS is stopped but not disabled, start only the stopped service. Run the matching line below; run both only if both meet those conditions.
    Do not change startup types, stop an active service, or override a disabled service on a managed PC. If WinDefend is stopped even though Defender is your primary antivirus, or a required service is disabled or refuses to start, record the service name and any error and use the troubleshooting steps below.
    Code:
    Start-Service -Name wuauserv
    Start-Service -Name BITS
    Run the Get-Service command again to check the result. Starting a service this way does not change its startup type. There is no setting to undo, and you don’t need to stop the service afterward.

Request and verify a fresh update in PowerShell​

  1. In the same administrator window, check what Defender is actually using before you retry:
    Code:
    Get-MpComputerStatus |
        Select-Object AMRunningMode, AntivirusSignatureVersion,
                      AntivirusSignatureLastUpdated
    AMRunningMode should be Normal if Defender is your active antivirus. Save the signature version and timestamp. These are the definition fields to compare, not the Defender engine or platform version.
  2. Request the update:
    Update-MpSignature
    Without a source parameter, the cmdlet uses the configured update source order. This is the right first attempt on a managed device as well as on a personal PC. Let the command finish and copy any error it reports. You don’t need to clear the existing definitions or restart Windows just to request this update.
  3. Run the Get-MpComputerStatus command from step 1 again. Interpret the result this way:
    • The signature version increased: Defender installed newer definitions. The timestamp tells you when the installed signatures were last updated. If Windows Security was still showing the earlier version, reopen Protection updates and compare it with the PowerShell result before retrying.
    • The version stayed the same and there was no error: This alone is not a failure. On a personal PC, compare AntivirusSignatureVersion with the published Version on Microsoft’s Security intelligence updates for Microsoft Defender Antivirus and other Microsoft antimalware page. On a managed PC, compare it with the version your administrator expects the configured source to offer; an internal server may not have approved the newest public release yet.
    • The version is still behind what your source should offer, or PowerShell reports an error: Note the time of the attempt. Check the Defender event log before changing anything else.

Find out why the update is still stuck​

  1. Check whether Defender failed during search, download, or installation. Open Start, search for Event Viewer, and go to Applications and Services Logs > Microsoft > Windows > Windows Defender > Operational. Look for entries around the time you ran the update. Event 2000 records a successful signature update; check the signature type and the previous and current versions. Event 2001 records a failure and can identify the update source, the stage that failed, and the error code. An older failure doesn’t invalidate a newer successful update.
  2. Follow the failing source. Microsoft identifies 0x80072EE7 as a name-resolution error. On a work PC, send the event details to IT so they can check the reported server, DNS, or proxy rather than having you disable the firewall or change network settings. If the event names an internal Windows Server Update Services (WSUS) server, IT should also check that it has approved and is offering the Defender security intelligence update. A service showing Running does not prove that the update server is reachable or has the package.
  3. On a personal PC, try a specific source if the normal request failed. If Defender is running and your PC is not subject to an organization’s update policy, you can request the definitions directly from Microsoft’s security intelligence source:
    Update-MpSignature -UpdateSource MMPC
    MMPC is the name PowerShell still uses for that source. The parameter applies to this request only; it does not rewrite the configured update order. Run Get-MpComputerStatus again afterward. If the version advances, Defender could install the definitions from that source, but that does not prove the normal automatic update path is fixed.
  4. If other Windows updates also fail, troubleshoot Windows Update itself. Microsoft recommends starting with the Windows Update troubleshooter in Get Help. The Settings path is Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run on Windows 11, or Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update > Run the troubleshooter on Windows 10. Save your work and restart after the troubleshooter finishes, then retry the Defender update and check the signature version again.
  5. Escalate if Defender cannot run or definitions remain stale. If Defender is supposed to be active but WinDefend remains stopped, or if the update source still produces a recent event 2001, send IT or Microsoft Support the before-and-after signature version and timestamp, the three service statuses, and the event’s source, stage, and error code. Those details distinguish a Defender startup problem from an update delivery failure without deleting existing definitions or weakening protection.