Advanced Plus Security Divine_Barakah's PC Security Config 2026

[Victor M]

Adguard was trying to add its xml file

Add the xml file to what ? So it did not mention scheduler. Then the scheduler alarm was independent of Adguard ?

 

[Divine_Barakah]

Add the xml file to what ? So it did not mention scheduler. Then the scheduler alarm was independent of Adguard ?

 

[Divine_Barakah]

View attachment 299568View attachment 299569

And I checked Adguard logs and searched for the ID 99528fa*****

 

[Divine_Barakah]

Try to update to the latest platform version 4.18.26080.3. Run as admin and restart.

https://download.windowsupdate.com/c/msdownload/update/software/defu/2026/08/updateplatform.amd64fre_99b71e4d3a498fec8b527f4dc0cf4a74169de128.exe

Optionally Update for Windows Security platform - KB5007651 (Version 10.0.29628.1000)

https://catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=a32ca1d0-ddd4-486b-b708-d941db4f1141#Overview

Gemini confirms that this is the source for the "cosmetic" issue.

"This confirms that the warning banner in your Action Center is not caused by malware tampering with Defender. It is a bug introduced by the 10.0.29628.1000 platform package when communicating with SecHealthUI."

 

[Victor M]

AI to the rescue !

My suspicious mind is useless - it only know signs of compromise !

" When you are a hammer, everything looks like a nail "

 

[Divine_Barakah]

AI to the rescue !

My suspicious mind is useless - it only know signs of compromise !

" When you are a hammer, everything looks like a nail "

I could have been worried if I was not updating Adguard at the time I saw the OSA block. I checked the logs immediately and whitlested Adguard.

And regarding the notification I received from Windows Security, I checked real-time protection via powershell and everything is running as Intended.

 

[Divine_Barakah]

Other users reporting the same issue on Reddit

https://www.reddit.com/r/windowsinsiders/s/3OMUp5IehV

https://www.reddit.com/r/pchelp/s/vXwWOTt06g

https://www.reddit.com/r/Intune/s/wY0Yk9MbZQ

 

[Divine_Barakah]

Other users reporting the same issue on Reddit

https://www.reddit.com/r/windowsinsiders/s/3OMUp5IehV

https://www.reddit.com/r/pchelp/s/vXwWOTt06g

https://www.reddit.com/r/Intune/s/wY0Yk9MbZQ

Running these commands in Powershell fixed the issue for me

# 1. Set update channels to stable staged ring
Set-MpPreference -EngineUpdatesChannel Staged
Set-MpPreference -PlatformUpdatesChannel Staged
Set-MpPreference -DefinitionUpdatesChannel Staged

# 2. Reset the Defender platform to OS baseline
& "C:\Program Files\Windows Defender\MpCmdRun.exe" -ResetPlatform

# 3. Pull fresh, stable definitions and platform files
& "C:\Program Files\Windows Defender\MpCmdRun.exe" -SignatureUpdate

 

[Divine_Barakah]

Running these commands in Powershell fixed the issue for me

 

[Divine_Barakah]

View attachment 299581

So upon research, it seems Windows, by default, sets Defender's update channel to NotConfigured (0), which allows Microsoft to manage rollouts through Windows Update.

I manually sat the updates channel to "Staged", but this was not what fixed my issue. It was the - ResetPlatform flag that purged the platform update that was causing my issue.