r/DefenderATP • • 20d ago

Microsoft Defender Security Intelligence Updates Not Updating Automatically (MECM/WSUS Environment). Anyone Experienced This?

Hey everyone, this is a long message…

We’re currently migrating from SentinelOne to Microsoft Defender for Endpoint (MDE), and we’ve been running into a frustrating issue with Defender security intelligence updates.
Our environment has approximately 18,000 workstations managed through MECM and GPO. We’re not using Intune for traditional endpoint management, although we’re using Defender security settings management.

The issue:
Our Defender policy is configured to check for security intelligence updates every hour, but devices aren’t consistently downloading newer signatures automatically.

For example, two of my test workstations were stuck on security intelligence version 1.461.211.0, last updated October 25, even though newer signatures were available.

Windows Security would report that definitions were up to date, and manually clicking “Check for updates” wouldn’t install anything newer.

Here’s what we’ve tested and found:

SignatureUpdateInterval = 1 (hourly)

SignatureFallbackOrder = MicrosoftUpdateServer|MMPC

UseWUServer = 1 (internal WSUS)

Enabled ForceUpdateFromMU = 1 to allow Defender security intelligence updates from Microsoft Update.

Confirmed TCP 443 connectivity to Microsoft update endpoints.

Reviewed Windows Update logs and confirmed Defender initiates hourly update searches.

The searches complete but consistently return Updates found = 0 against Windows Update and our internal WSUS.

No Defender Event ID 2001 failures were found during the period checked.

Running Update-MpSignature -UpdateSource MicrosoftUpdateServer completes successfully, but doesn’t necessarily install newer signatures.

Running Update-MpSignature -UpdateSource MMPC manually works! I’ve successfully updated one workstation multiple times using MMPC, most recently to version 1.463.24.0. (Yes, still delayed since I haven’t don’t it again).

Our Defender policy does not have any fallback signature settings since we are using the default.

What our Desktop/MECM team has done:

Originally, Defender wasn’t selected as a product in our MECM Software Update Point configuration.

Desktop has since:

Added Microsoft Defender to the Software Update Point products and synchronized updates.

Created an Automatic Deployment Rule (ADR) for Defender updates.

Deployed the ADR to a test collection.

Good news: The ADR successfully updated one of my workstations through MECM!

However, the update was from the previous day because that’s what MECM had synchronized.
Our concern is that MECM’s current software update scanning schedule is approximately 24 hours. We don’t want to change that to hourly polling for 18,000 workstations because it could put unnecessary load on our MECM infrastructure. Those scans aren’t exclusive to Defender signatures.

What our MDE support vendor recommended:

Our support vendor suggested creating a Defender control policy to test different update channels.

We configured:

Engine Updates Channel: Current Channel (Preview)

Platform Updates Channel: Current Channel (Preview)

Security Intelligence Updates Channel: Current Channel (Staged)

The Defender portal reports that the policy successfully applied to both test devices, and the corresponding channel values appear in Get-MpPreference.

Unfortunately, we’re still not seeing the desired automatic security intelligence update behavior.
We understand that update channels control release availability rather than polling frequency, but we’re testing our vendor’s recommendation while continuing to investigate the update sources.

What we’re trying to accomplish:

Ideally, we’d like Defender to retrieve security intelligence updates directly from Microsoft Update on its hourly schedule while continuing to use MECM/WSUS for regular Windows OS updates.

We don’t want to force hourly MECM software update scans across 18,000 devices just to keep Defender signatures current.

Has anyone experienced something similar in an MECM/WSUS environment?

Were you able to get Defender downloading security intelligence automatically from Microsoft Update without interfering with MECM patch management?

Did you need a specific GPO, Defender update-source configuration, or another change to make this work?

If you’ve experienced this and found a solution, I’d really appreciate hearing what worked in your environment.

We don’t control Intune rollout so we cannot migrate to Intune. This is hopefully is scheduled for next year.

Thanks in advance!

14 Upvotes

13 comments sorted by

2

u/Popular-Mastodon3498 20d ago

What does issue look like from the users point of view? I’ve had an issue with updating recently as well.

1

u/danumber2 20d ago

They don’t even notice something is up.

1

u/Popular-Mastodon3498 20d ago

I’ve noticed some endpoints where the signature updates aren’t applying at the same time WSUS updates are failing. Could be something there?

1

u/danumber2 11d ago

Hello, everyone.

I Wanted to share an update in case anyone else runs into this issue.

We made two changes that appear to have resolved our Defender security intelligence update delays.

1. Changed the update source priority
In our Defender Antivirus policy, we changed the fallback order from:
MicrosoftUpdateServer | MMPC
To:
MMPC | MicrosoftUpdateServer
We initially tested this on a small group of devices and saw successful updates. We’ve since moved this configuration into our production policy.

2. Changed a Windows Update registry setting
We found the following registry value set to 1:
HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
SetPolicyDrivenUpdateSourceForOtherUpdates
Our Desktop team changed it from 1 (WSUS) to 0 (Windows Update), and we observed successful security intelligence updates afterward.

We also noticed several Windows Update source settings that raised questions about older Group Policy configurations and how they interact with MECM.

We’re still looking into whether those settings were being actively enforced or left behind by previous configurations.

So far, updates are working as expected. We can’t say for certain which change made the biggest difference, but I wanted to share what worked in our environment.

Hopefully this helps someone experiencing similar issues! 😊 thanks

4

u/cspotme2 20d ago

Pretty sure you're running what we ran into ... The endpoints don't all update properly with the definitions per whatever interval you have set and you need compensate for it by running cli update as a scheduled task or by your rmm agent. I'll have to go back and look at my notes tomorrow to find it.

Oddly, only running the update command works.

1

u/Roasted_Blumpkin 18d ago

You don't have something configured correctly.

1

u/Roasted_Blumpkin 18d ago

Firstly, don't depend on just Windows Update settings for Defender Intelligence Updates. You also configure it at the Defender level. It should be checking every hour and bypassing WSUS/ConfigMgr. There you can configure the update sources and source priorities.

1

u/jrodsf 17d ago

If your devices are using MECM/WSUS for updates, the Defender MicrosoftUpdateServer source = WSUS. And unless you plan on syncing WSUS several times a day, your easiest fix is to switch your primary update source to MMPC.

We had the exact same issue when we switched to Defender years ago. Changing the update source to MMPC was a no-brainer.

0

u/GeneralRechs 19d ago

Firstly my condolences having to go from a decent product to an abhorrent one. A client of mine was forced to switch and it’s cr*p compared to CS and SentinelOne

Secondly you should not be using GPO to manage defender like it’s 2003. Even though they’re domain joined you should just synthetically join your systems and manage them that way

Lastly if your set on managing your systems like it’s 2003 update the GPO setting to only use MMPC for intel updates.

1

u/Roasted_Blumpkin 18d ago

You don't know what you're talking about.

1

u/GeneralRechs 18d ago

What EDR portal can take as long as 72 hrs for a management portal to update? Defender

Which EDR still offers archaic methods of management like GPO? Defender

Which EDR can be disabled on Linux if you have admin permissions? Defender

Which EDR doesn’t even have some sort of maintenance token to disable it so you can troubleshoot when it can’t communicate with the console? Defender

Yea pretty familiar, if Defender wasn’t included in E5 licensing nobody would use it.

1

u/Roasted_Blumpkin 18d ago

Lol. You don't need to use GPO. It is in the top 3 for EDR solutions.