Windows Update Fails to Update Microsoft Defender

Topic

New Reply

I often get Defender update notifications in Windows Update (see attachment 1) but they always fail to install with error 0x80240017. However, when I immediately check “Protection Update” under “Windows Security”, it always shows a newer/updated version (see attachment 2). In this case, Windows Update shows version 1.421.556.0 but Windows Protection Update shows version 1.421.561.0. Also, the Windows Reliability Monitor (attachment 3) shows two update failures both offered by Windows Update and two update successes I assume that were done automatically. Why does Windows Update offer me Defender updates that always fail but Defender gets updated another way? Is there a way to stop Windows Update offering me an older update that is already on my system.

Reply | Quote

Replies

Double post!

Please do not double post without linking to the original.

cheers, Paul

Reply | Quote

Sorry Paul,

I did not realize that I was double posting by also posting on MS’s site. On AskWoody, how do I link to the original? I was expecting to get separate and different responders by posting on two sites!

Thanks

Reply | Quote

See this post for details.

cheers, Paul

1 user thanked author for this post.

sahalen

Reply | Quote

@sahalen –

I’ve also had that problem and I figured it out over time. The conclusion I came to is the same as Hania Lian mentions to you in the second reply to your original post on MS’s site. Here’s a brief quote to refresh your memory:

Hello,

Error 0x80240017 usually means that the update is not applicable to your system, probably because a newer update is already installed. Windows Security might have already auto-updated the Defender before Windows Update attempted its scheduled check, hence the discrepancy and the failure message.

Hania then goes on to describe how to purge the WU cache.

What I’ve been able to do that’s a lot faster (because of my settings for WU) is:

When I see that WU is offering an older update than the one that’s currently in use by Defender, I simply click the “Pause updates for 7 days” setting and then wait ten seconds (yes, I count to 10 to make sure), after which I click the button labeled “Resume updates” which then forces WU to rescan for updates and, finding none that are applicable (because the in-use definitions are newer than the ones it wanted to install), it then says that I’m fully up to date. Please be aware that this procedure could result in the unwanted installation of updates on your system by WU if your settings aren’t set quite right, so tread with caution using it.

 

Reply | Quote

Hi Bob99,

Thanks for your reply. After installing a month’s updates, I “Pause” the next month’s update(s) until the end of that month. I wait until I get the go from Susan Bradley. However, I often get the Defender update notifications in WU while I am already on “Pause”, so if I click on “Resume updates”, I’m afraid that I will get unwanted updates. You say “…if your settings aren’t set quite right…”. Can you please expand on what settings to set? Is there a way to stop WU or the system from getting the Defender updates?

Thank-you

Reply | Quote

@sahalen –

Is this behavior you’re asking about occurring on a Windows 10 Home or Windows 10 Pro machine? The answer to this question will dictate what you should do to have settings the same as or comparable to mine.

Also, in addition to certain settings with Windows to help control Windows Update, I also use wushowhide.cab to hide unwanted Windows updates.

 

Reply | Quote

Hi Bob99,

My machine is a Windows 10 Pro. I use “Windows Update MiniTool” to hide unwanted Windows updates.

Thanks again,

sahalen

Reply | Quote

sahalen wrote:

My machine is a Windows 10 Pro

Windows 10 Pro you don’t have to hide updates. You should set ‘notify=2’ which will notify you about new updates and let you install when you are ready. If you wish to hide some of the updates you can use WUmgr providing you didn’t disable preview, Firmware, BIOS, driver updates in GPEdit. Other than these updates I don’t see any updates needing to be hidden.

https://www.askwoody.com/forums/topic/2000016-guide-for-windows-update-settings-for-windows-10/

Reply | Quote

There is a disconnect between update processing performed by Windows Security and Windows Update.  I have also noticed that there can be a significant lag between the time when Win10 22H2 checks for updates and the time when the system issues a notification that updates are available during which time Windows Security may have already performed an update.

However, as long as Windows is keeping Defender current with KB226702 updates in my opinion this disconnect is an annoying but not significant issue.  I view it as an essentially cosmetic issue related to the tracking of failed installations of superseded updates.  Of course, opinions can vary.

1 user thanked author for this post.

Bob99

Reply | Quote

EricB,

Yes, I agree with you that it is essentially a cosmetic issue and doesn’t cause any issues. I was just hoping there was a way to nip it in the bud.

Thanks,

sahalen

Reply | Quote

sahalen wrote:

I was just hoping there was a way to nip it in the bud.

There most likely is, but it most likely involves MS rewriting the updating routines within WU as they apply to Defender definition and program updates which Defender goes and gets itself.

The method I had planned on describing that you undertake was only a workaround to reduce the likelihood of your seeing that error in the reliability history entries, and there have been times where it’s still happened to me because I didn’t pay attention to one thing or another.

That’s why I’m inclined to agree with @EricB ‘s statement that his is a cosmetic issue that hasn’t caused any real problems or harm at all, but can be annoying on occasion.

Reply | Quote