Anavem
Languagefr
How to Check Microsoft Defender Antivirus Signature Versions Using 5 Methods

How to Check Microsoft Defender Antivirus Signature Versions Using 5 Methods

Master five different techniques to verify and monitor Microsoft Defender AV signature versions across Windows environments using Intune, PowerShell, Command Prompt, Windows Security, and Registry methods.

April 13, 2026 12 min
mediummicrosoft-defender 7 steps 12 min

Why Monitor Microsoft Defender Antivirus Signature Versions?

Microsoft Defender Antivirus relies on regularly updated signature files to detect and protect against the latest malware threats. These security intelligence updates, released multiple times daily, contain definitions for new viruses, spyware, and other malicious software. Monitoring signature versions ensures your Windows systems maintain current protection levels and helps identify update failures before they compromise security.

What Are the Different Types of Defender Signatures?

Microsoft Defender uses three main signature types: antivirus signatures for traditional malware detection, antispyware signatures for potentially unwanted programs and spyware, and Network Inspection System (NIS) signatures for network-based threat detection. Each signature type updates independently, and comprehensive monitoring requires checking all three components along with the engine version that processes these signatures.

Which Methods Provide the Most Accurate Signature Information?

This tutorial covers five distinct approaches to checking Microsoft Defender signature versions, each serving different use cases. The Windows Security app offers the simplest GUI method for individual systems, while PowerShell provides detailed programmatic access ideal for scripting. Command Prompt tools enable direct interaction with Defender's core functions, Event Viewer tracks historical update patterns, and Registry access offers the most direct data source. For enterprise environments, Intune admin center provides centralized fleet monitoring capabilities.

Implementation Guide

Full Procedure

01

Check Signature Versions Using Windows Security App

The Windows Security app provides the most user-friendly method to check your current Microsoft Defender signature versions. This built-in tool displays security intelligence versions and last update timestamps without requiring administrative privileges.

Open the Windows Security app by typing Windows Security in the Start menu search bar and clicking the result. Navigate to Virus & threat protection from the main dashboard.

Click on Protection updates under the Virus & threat protection settings section. Here you'll see the current Security Intelligence version (for example, 1.441.355.0) along with the last update timestamp.

Pro tip: The Windows Security app automatically refreshes this information every few hours, so you're seeing near real-time data without manual commands.

Verification: The protection updates page should display three key pieces of information: Security Intelligence version number, last update date and time, and next scheduled check time. If any of these are missing, your Defender installation may need attention.

02

Use PowerShell Get-MpComputerStatus for Detailed Information

PowerShell provides the most comprehensive method for checking Defender signature versions, especially useful for scripting and automation. The Get-MpComputerStatus cmdlet returns detailed information about all signature types.

Open PowerShell as Administrator by right-clicking the Start button and selecting Windows PowerShell (Admin). Run the following command:

Get-MpComputerStatus | Select-Object AntivirusSignatureVersion, AntispywareSignatureVersion, AMProductVersion, AntivirusSignatureLastUpdated, AntispywareSignatureLastUpdated

This command displays the antivirus signature version, antispyware signature version, engine version (AMProductVersion), and the last update timestamps for both signature types. The current versions should show 1.441.355.0 for signatures and 1.1.25100.9002 for the engine.

For a more detailed view including NIS (Network Inspection System) signatures, run:

Get-MpComputerStatus | Format-List *Signature*, *Version*, *Updated*
Warning: If PowerShell returns errors about the Windows Defender module, ensure the Windows Defender service is running with Get-Service WinDefend and restart if necessary.

Verification: The output should show version numbers in the format X.XXX.XXX.X and recent timestamps. If signatures are more than 7 days old, force an update using Windows Update or manual methods.

03

Verify Signatures Using Command Prompt MpCmdRun Tool

The MpCmdRun.exe command-line tool provides direct access to Microsoft Defender's signature management functions. This method is particularly useful for troubleshooting and automated scripts.

Open Command Prompt as Administrator and navigate to the current platform directory. The path changes with each platform update, so use this command to find the current version:

cd "%ProgramData%\Microsoft\Windows Defender\Platform"

List the available platform versions:

dir

Navigate to the highest version number directory (should be around 4.18.25100.9008 or newer):

cd 4.18.25100.9008

Check the current signature status:

MpCmdRun.exe -SignatureUpdate

This command attempts to update signatures and displays the current version information in the output. For a status-only check without updating, you can also run:

MpCmdRun.exe -GetFiles
Pro tip: Create a batch file with these commands for regular signature monitoring. The MpCmdRun tool provides exit codes that can be used in automated monitoring scripts.

Verification: The command output should display "Signature update started" followed by version information. If you see "No signature updates available," your signatures are current. Error codes indicate connectivity or permission issues.

04

Monitor Signature Updates Through Event Viewer

Event Viewer provides historical tracking of signature updates and can help identify patterns or issues with automatic updates. Microsoft Defender logs signature check events every hour with detailed version information.

Open Event Viewer by pressing Win + R, typing eventvwr.msc, and pressing Enter. Navigate to the Microsoft Defender operational log:

Applications and Services LogsMicrosoftWindowsWindows DefenderOperational

Filter the log for Event ID 1151, which represents signature update checks. Right-click on Operational and select Filter Current Log. In the Event IDs field, enter:

1151

Click OK to apply the filter. Double-click on recent Event ID 1151 entries to view detailed signature version information. The event details will show the complete definition version string and update status.

Look for these key fields in the event details:

  • Current Signature Version: Shows the active signature version
  • Previous Signature Version: Displays the version before the last update
  • Update Source: Indicates whether updates came from Windows Update, WSUS, or manual installation
Warning: If you don't see Event ID 1151 entries, the Operational log may be disabled. Enable it by right-clicking the log name and selecting "Enable Log."

Verification: Recent Event ID 1151 entries should appear every hour. If the last entry is more than 2-3 hours old, check your Windows Update settings and network connectivity.

05

Access Signature Information via Windows Registry

The Windows Registry stores Microsoft Defender signature version information that can be accessed programmatically or manually. This method is useful for custom monitoring solutions and provides the most direct access to version data.

Open Registry Editor as Administrator by typing regedit in the Start menu, right-clicking the result, and selecting Run as administrator. Navigate to the signature updates registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Defender\Signature Updates

Within this key, examine these important values:

  • SignatureVersion: Current security intelligence version
  • AntivirusSignatureVersion: Specific antivirus signature version
  • AntispywareSignatureVersion: Antispyware signature version
  • AntivirusSignatureLastUpdated: Timestamp of last antivirus update
  • AntispywareSignatureLastUpdated: Timestamp of last antispyware update

For automated monitoring, you can query these registry values using PowerShell:

Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows Defender\Signature Updates" | Select-Object *SignatureVersion*, *LastUpdated*

This PowerShell command provides the same information as manual registry browsing but in a scriptable format.

Pro tip: Export these registry values to a text file for historical tracking using reg export commands in your monitoring scripts.

Verification: The registry values should match the versions displayed in other methods. If registry values are missing or corrupted, reinstall Microsoft Defender using Windows Features or run sfc /scannow to repair system files.

06

Monitor Enterprise Environments Using Intune Admin Center

For organizations managing multiple Windows devices, the Intune admin center provides centralized monitoring of Microsoft Defender signature versions across your entire fleet. This method requires Microsoft Intune licensing and enrolled devices.

Sign in to the Intune admin center at https://endpoint.microsoft.com using your organizational credentials. Navigate to the endpoint protection reporting section:

ReportsEndpoint analyticsMicrosoft Defender for Endpoint

Alternatively, access device-specific information through:

DevicesAll devices → Select a device → Endpoint protection

The reports display signature version information for each enrolled device, including:

  • Current Security Intelligence version
  • Last update timestamp
  • Update compliance status
  • Devices with outdated signatures

Create custom reports by clicking Create report and selecting Microsoft Defender Antivirus as the report type. Configure filters for:

- Signature version older than X days
- Devices with failed updates
- Compliance status by organizational unit

For automated monitoring, use the Microsoft Graph API to query device compliance data:

Connect-MgGraph -Scopes "DeviceManagementManagedDevices.Read.All"
Get-MgDeviceManagementManagedDevice | Select-Object deviceName, lastSyncDateTime, complianceState
Warning: Intune reporting data syncs every 6-24 hours. For real-time signature status, use the device-specific methods on individual machines.

Verification: The Intune dashboard should show your enrolled devices with current signature versions. If devices appear with "Unknown" status, verify they're properly enrolled and communicating with Intune services.

07

Troubleshoot Outdated Signatures and Update Failures

When signature versions are outdated or updates fail, systematic troubleshooting ensures your Microsoft Defender protection remains current. Common issues include network connectivity problems, corrupted signature cache, and SHA-2 signing compatibility.

First, check if your system supports SHA-2 signed updates (required since October 2019). Run this PowerShell command to verify:

Get-HotFix | Where-Object {$_.HotFixID -eq "KB4474419" -or $_.HotFixID -eq "KB4490628"}

If no results appear and you're running Windows 10 version 1703-1809, install the SHA-2 support update through Windows Update.

Clear corrupted signature cache using MpCmdRun:

cd "%ProgramData%\Microsoft\Windows Defender\Platform\4.18.25100.9008"
MpCmdRun.exe -RemoveDefinitions -DynamicSignatures
MpCmdRun.exe -SignatureUpdate

Force an immediate signature update through PowerShell:

Update-MpSignature -UpdateSource MicrosoftUpdateServer

If automatic updates continue failing, manually download the latest signatures from the official Microsoft WDSI page:

  • 64-bit systems: Download mpam-feX64.exe
  • 32-bit systems: Download mpam-fe.exe

Run the downloaded file as Administrator to install the latest signatures manually.

Pro tip: Set up a scheduled task to run Update-MpSignature daily as a backup to automatic updates, especially in environments with restricted internet access.

Verification: After troubleshooting, verify the signature version using any of the previous methods. The version should match the latest available (currently 1.441.355.0). Check Event Viewer for successful update events (Event ID 1151) within the next hour.

Frequently Asked Questions

How often does Microsoft Defender update its antivirus signatures?+
Microsoft Defender antivirus signatures update multiple times per day, typically every 1-3 hours when new threats are identified. The system automatically checks for updates hourly and downloads them via Windows Update. Manual updates can be triggered using PowerShell commands or the MpCmdRun tool. Enterprise environments may have different update schedules based on WSUS or Intune policies.
What is the difference between antivirus and antispyware signature versions in Microsoft Defender?+
Antivirus signatures detect traditional malware like viruses, trojans, and worms, while antispyware signatures target potentially unwanted programs (PUPs), adware, and spyware. Both signature types may have different version numbers and update schedules. The security intelligence version number typically encompasses both types, but checking individual signature versions helps identify specific update failures or delays in either protection category.
Why do Microsoft Defender signature updates fail and how can I fix them?+
Common causes include network connectivity issues, corrupted signature cache, insufficient disk space, or missing SHA-2 support on older Windows versions. Solutions include clearing the signature cache with MpCmdRun -RemoveDefinitions, manually downloading updates from Microsoft WDSI, ensuring SHA-2 support is installed, and verifying Windows Update service is running. Enterprise environments should check WSUS configuration and Intune policies for update restrictions.
Can I check Microsoft Defender signature versions remotely across multiple computers?+
Yes, several methods enable remote monitoring: PowerShell remoting with Invoke-Command and Get-MpComputerStatus, Microsoft Intune admin center for enrolled devices, Group Policy with WMI queries, and SCCM reporting for enterprise environments. The Intune admin center provides the most comprehensive dashboard for signature version compliance across your device fleet, while PowerShell scripting offers custom automation capabilities.
What should I do if my Microsoft Defender signatures are severely outdated?+
If signatures are more than 7 days old, immediately download manual updates from the official Microsoft WDSI page (mpam-feX64.exe for 64-bit systems). Run the installer as Administrator, then verify the update with Get-MpComputerStatus in PowerShell. Check Windows Update settings, ensure internet connectivity, and verify the Windows Defender service is running. For persistent issues, reset Windows Update components or reinstall Microsoft Defender through Windows Features.

Discussion

Share your thoughts and insights

Sign in to join the discussion