Skip to content

Commit 38afe42

Browse files
committed
self review
1 parent 1e6a16b commit 38afe42

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

defender-endpoint/troubleshoot-security-intelligence-not-updated.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -62,11 +62,12 @@ The following screenshot shows an error about **Signature Update failed**.
6262

6363
2. If it does, then you could try updating via Microsoft Malware Protection Center (MMPC).
6464

65-
Run the following PowerShell command as an administrator.
65+
Run the following PowerShell command as an administrator.
66+
67+
```powershell
68+
& "${env:ProgramFiles}\Windows Defender\MpCmdRun.exe" -SignatureUpdate -MMPC
69+
```
6670
67-
```powershell
68-
& "${env:ProgramFiles}\Windows Defender\MpCmdRun.exe" -SignatureUpdate -MMPC
69-
```
7071
3. If it works, then you could be having issues with the Security intelligence [Fallback order](manage-protection-updates-microsoft-defender-antivirus.md#fallback-order) being set to a WSUS server that doesn't have the **Security intelligence** updates approved. Or if pointing to a UNC share, they might be stale or the Windows Update service might be having issues.
7172
1. To check the WSUS server that the machine goes to, review `HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\WUServer (REG_SZ)`. Once you find the WUServer, check if that WSUS server has the MDAV security intelligence [(KB2267602 for MDAV and KB2461484 for SCEP)](microsoft-defender-antivirus-updates.md#security-intelligence-updates) approved.
7273
2. To check the UNC share, review [Manage how and where Microsoft Defender Antivirus receives updates](manage-protection-updates-microsoft-defender-antivirus.md#create-a-unc-share-for-security-intelligence-and-platform-updates).

0 commit comments

Comments
 (0)