Hi,
I've been investigating persistent CPU usage by Microsoft Defender Antivirus (MsMpEng.exe) on Windows 11 25H2 (OS Build 26200.9974), and found a rather unusual issue involving a scheduled task.
I first noticed this after installing the November cumulative update KB5132061.
Even when the PC was completely idle, MsMpEng.exe constantly consumed around 3.5-4% CPU (in Task Manager).
After investigating with Microsoft Defender Performance Analyzer and Sysinternals Process Monitor, I discovered the following:
1. The scheduled task
The task is located at:
\Microsoft\Windows\Flighting\FeatureConfig\GovernedFeatureUsageProcessing
Its configuration contains:
- Two
WnfStateChangeTrigger triggers. - WNF state names:
7548BCA32B0D890F and 7550BCA32B0D890F. - COM Handler CLSID:
{866F38A9-0302-4926-A36F-E4BAABAAE116}. - COM DLL:
C:\Windows\System32\fcon.dll. - Action name in Task Scheduler logs:
Governed Feature Usage Reporting Task Handler.
2. Repeated task launches
After enabling the Task Scheduler Operational log, I discovered an unusually high number of task launches.
During one captured burst, Event ID 129 recorded approximately 40-51 launches per second over several consecutive seconds.
Each launch created a separate, short-lived taskhostw.exe process.
Process Monitor also showed repeated file-open operations by MsMpEng.exe involving taskhostw.exe and its associated Windows system DLLs.
3. Disabling the task dramatically reduced CPU usage
I temporarily disabled only GovernedFeatureUsageProcessing to test whether it was related to the Defender CPU usage.
I also measured the actual CPU time consumed by MsMpEng.exe over 180 seconds using PowerShell. These measurements are normalized across all logical processors.
Before disabling:
- CPU time: 53.58 seconds.
- Total CPU usage: 1.86%.
- CPU usage (one logical processor equivalent): 29.77%.
After disabling:
- CPU time: 0.33 seconds.
- Total CPU usage: 0.01%.
- CPU usage (one logical processor equivalent): 0.18%.
The CPU also returned to its normal idle clock frequency. My Intel Core i5-14400F had been running at around 4.0 GHz even when the system was idle. After disabling the task, its clock frequency returned to the usual idle range of approximately 1.0-1.2 GHz.
This strongly suggests that the scheduled task's repeated activity is responsible for the excessive Defender CPU usage, although I haven't identified the underlying cause of the repeated WNF notifications.
4. How to check and test this on your system
This is a scheduled task, not a Windows service.
Check its current state (PowerShell):
Get-ScheduledTask -TaskPath '\Microsoft\Windows\Flighting\FeatureConfig\' -TaskName 'GovernedFeatureUsageProcessing' | Select-Object TaskName,State
Temporarily disable it (run PowerShell as Administrator):
Disable-ScheduledTask -TaskPath '\Microsoft\Windows\Flighting\FeatureConfig\' -TaskName 'GovernedFeatureUsageProcessing'
Wait a short while and observe whether MsMpEng.exe CPU usage decreases. In my case, it dropped from around 4% to just 0-0.1% after disabling the task (in Task Manager).
Re-enable it:
Enable-ScheduledTask -TaskPath '\Microsoft\Windows\Flighting\FeatureConfig\' -TaskName 'GovernedFeatureUsageProcessing'
You can also find it through the graphical interface:
- Press
Win + R and enter taskschd.msc. - Navigate to
Task Scheduler Library → Microsoft → Windows → Flighting → FeatureConfig. - Find
GovernedFeatureUsageProcessing. - Right-click to disable or enable it.
Disabling this task does not disable Microsoft Defender or Windows Update. However, it may affect the processing of governed feature usage information, so this should be treated as a diagnostic test rather than a universal fix.
5. Questions
Has anyone else encountered this behaviour?
I'm particularly interested in:
- What do these two WNF state names represent?
- Why would
GovernedFeatureUsageProcessing launch dozens of times per second? - Could this be a bug in Windows Feature Configuration or its
fcon.dll COM handler? - Has anyone observed similar behaviour after a Windows cumulative update?
- Is there any known side effect to keeping this particular scheduled task disabled?
I found older reports involving other tasks in the same Flighting\FeatureConfig directory, but haven't found anyone reporting this exact issue:
https://www.reddit.com/r/WindowsHelp/s/Mdxxu3EhLE
https://www.reddit.com/r/techsupport/s/79X5dFJk5W
I'd like to understand the root cause rather than simply leave the task disabled as a workaround.
Thanks!