Update for Windows Security platform - KB5007651 (Version 10.0.27703.1006) keeps reinstalling

I've had this issue a couple of times over the last year or so. It just happened to me again today. For me at least, I think it's caused by something being updated in my third-party AV (ESET). I've seen this correspond to times when ESET asks for a PC reboot following a component update. Looking at my ESET Update Logs, it looks like the culprit might be ESET's Rapid Response module.

I fix it by opening the Windows Security app and navigating to "Device security> Core isolation details> Microsoft Vulnerable Driver Blocklist" and temporarily turn it OFF. Then go check for Windows Updates again. It will probably give you a couple Microsoft Defender Antivirus updates (antimalware platform & Security Intelligence Update). Then turn "Microsoft Vulnerable Driver Blocklist" back ON.

The issue should be resolved after that.
___
EDIT: I forgot to mention;
If you don't ever use Microsoft Defender Antivirus scans in addition to a third party AV, you can also prevent further unnecessary Defender AV updates by doing the following:

•Open the Windows Security app, and navigate to "Virus & threat protection> Microsoft Defender Antivirus options" and turn OFF "Periodic scanning". (may need to reboot afterwards)

For some reason, that option seems to get re-enabled from time-to-time.🤷‍♂️

Thanks for the detailed update, it’s clear you’ve already gone above and beyond to troubleshoot this issue. Since the steps in the thread didn’t resolve it, and the update doesn’t appear in the uninstall list, this does seem like an issue that might require a patch to fully address.

If you’re okay with waiting for the next security update, that’s a reasonable approach. To ensure you receive the latest patch as soon as it’s available, head to Settings > Windows Update > and toggle On the "Get the latest updates as soon as they’re available".

In the meantime, I recommend relying solely on the Windows Security app to protect your system. While I couldn’t find any specific cases linking third-party antivirus software like Norton 360 to this glitch, it’s possible that it could be contributing to the issue. Temporarily disabling or uninstalling it might help rule that out.

I also highly encourage you to provide feedback to Microsoft so they’re aware of the issue. You can do this by pressing Windows key + F on your keyboard and describing the problem in detail.

Should you need further information please let me know.

I hope these steps help bring some clarity or progress to the situation.

"While I couldn’t find any specific cases linking third-party antivirus software like Norton 360 to this glitch, it’s possible that it could be contributing to the issue. Temporarily disabling or uninstalling it might help rule that out."

My apologies for not being clear. While following the kernel steps in the thread you provided, I turned N360 off.

I utilized the Feedback Hub. Thanks for your expertise John.

sola dei gloria

Thanks for replying to a low priority inquiry. I did see similar complaints in the historic record here, but assumed those were resolved through a patch of some sort, particular to the KB version.

My only troubleshooting steps involved plunking said title into google and seeing if this was a new issue. At one point I read a post from a year ago stating the problem went away after the next security update came around.

I did think to uninstall the update and let Windows Update do it's thing but, as I stated in my original post, the update in question doesn't show up in the list (only Update for Microsoft Windows KB5049622).

On Jan 15, I reached out to MS Support and let the guy look at my PC remotely. At first he indicated my PC was up to date, as the Windows Update screen said and to ignore the security update reinstallation. Then he downloaded a file called "mediacreationtool", a Windows 11 disc image file, and started the "install the OS without turfing my data" option (paraphrase in quotes). Before we parted ways, he said the error won't return.

I did try the kernel/scan steps in the thread you provided. Of course, Norton 360 makes a fuss over this but I turned it off and let MS Security take over. No change.

If it's a matter of waiting for a patch, that's cool, I can do that.

Hi there! I'm John, a fellow Microsoft user like you.

You're not alone, this issue has been reported by some users in the past. While it's not the latest concern, the suggestions from Sumit and the original poster about performing Security Scan and Kernel-mode Hardware-enforced Stack Protection here might still help: https://answers.microsoft.com/en-us/windows/for...

If the issue persists, please clarify what troubleshooting steps you and Microsoft Support have already performed. This will help me avoid recommending them again.

Click "Reply" below to let me know.

Regards,

John J.D.