Scheduled Windows Diagnostics: what EnabledExecution disables

On this page

Short answer: EnabledExecution=0 disables specifically the scheduled launch of Windows diagnostic packages. Task Scheduler can still run the corresponding system task, but its handler does not perform detection, troubleshooting or automatic remediation. This does not disable all Windows diagnostics and is not a proven optimization of FPS, latency, RAM or disk.

Status: the purpose of the policy is documented by Microsoft. On Windows 11 Pro 25H2 it is statically confirmed that its value is checked inside the Scheduled Diagnostics handler and restricts the execution of diagnostic packages. The runtime behavior of the task and the impact on performance were not measured in this study.

Claim under test

We tested four claims:

Windows uses EnabledExecution as a machine policy for Scheduled Diagnostics.
The value 0 prohibits the scheduled execution of diagnostic packages.
Manually starting the same task does not bypass the policy check inside its handler.
Disabling this policy does not mean disabling all Windows diagnostic and maintenance tools.

This page is related to “Scheduled Diagnostics”, “Automatic Maintenance”, “Diagnostic Events” and “Activity Recording”. Blocking one maintenance branch does not disable all Windows diagnostics and does not prove overall CPU savings.

What Scheduled Diagnostics is

Scheduled Diagnostics allows Windows to periodically detect system problems, run diagnostics and, at a permitted level, automatically fix some of the issues found.

Microsoft describes three possible behaviors:

detection and troubleshooting with a user notification for interactive remediation;
detection, troubleshooting and automatic remediation of some problems;
prohibition of scheduled detection, diagnostics and remediation.

If the policy is not configured, Windows uses local troubleshooting preferences. In the absence of such a local setting, Microsoft documents detection, diagnostics and remediation enabled by default.

Scope of the study

Area	What was checked	Status
Microsoft Policy CSP	Purpose, Registry mapping, default state and application without reboot	Documented
Windows 11 Pro 25H2 build 26200.8655 x64	Policy reading and branching of the Scheduled Diagnostics handler	Statically confirmed
Windows 10 and Windows Server	Only the applicability stated in the public documentation	Exact runtime path not verified
User performance	CPU, RAM, I/O, FPS, frametime and input latency	Not measured

Microsoft’s public documentation indicates support for the corresponding ADMX-backed policy on Windows 10 2004 with certain cumulative updates and on Windows 11 21H2 and newer for the Pro, Enterprise, Education and IoT Enterprise editions. Home is not listed in that table. This does not prove that the internal path is unchanged on every edition and build.

Methodology

The study combined two classes of evidence:

official Microsoft documentation with the purpose of the policy, its Registry mapping and its states;
static inspection of the Windows system component that services the Scheduled Diagnostics task.

We checked the handling of the states 0, 1, a missing value and an additional execution level. No virtual machine, system traces or diagnostic package launches were used. Decompiled code, internal tools and raw artifacts are not published.

Results

State	Documented or confirmed behavior
`EnabledExecution=0`	Scheduled detection, diagnostics and remediation are prohibited
`EnabledExecution=1` without a separate level	The Scheduled Diagnostics path is allowed; the exact action depends on the execution level
Policy absent	Local preferences are used; Microsoft documents the enabled default behavior
Value of the wrong type	Normal execution is not guaranteed; such a state is not recommended

On the build studied, the check is performed inside the handler of the system task. Therefore, manually starting the same task does not turn execution prohibited by the policy into permitted execution.

What is confirmed

EnabledExecution relates to Scheduled Diagnostics, not to all Windows diagnostics.
The value 0 blocks the execution of diagnostic packages through the scheduled handler studied.
The system task and its registration are not removed in the process.
A policy change is applied without a reboot; Scheduled Diagnostics requires the Task Scheduler service to be running.
Removing the policy value returns Windows to local preferences and the standard default logic.

What is not confirmed

a measurable reduction in background activity, CPU, RAM or disk operations;
an increase in average FPS, P1, P0.1 or a decrease in input latency;
disabling sfc, chkdsk, Microsoft Defender, disk optimization or all maintenance tasks;
preventing all Windows notifications about detected problems;
the same internal path on Windows 10, Windows 11 and Windows Server.

The absence of a quantitative result matters: excluding one rare diagnostic path may not change the metrics in a normal gaming session at all.

Limitations

The study was performed statically on one up-to-date system. It confirms the existence and meaning of the decision path, but does not show the frequency of actual launches, the amount of work performed, a possible backlog after the setting is returned or the user-visible effect.

The official default state and the fallback to local preferences are documented by Microsoft. The behavior of a clean installation where both the policy value and the local preference value are physically absent at the same time was not reproduced separately.

Practical conclusion

For most users it is safer to leave Windows default: this way Windows retains the ability to detect and fix some problems in advance.

Disabling makes sense only as a deliberate trade-off if the user wants to prohibit specifically the scheduled diagnostic packages and accepts the loss of this preventive function. Do not apply the setting for a promised performance gain: the study did not show such a result.

The related free setting is described on the “Scheduled Diagnostics” page in BoosterX.

Restoring the state

To revert, remove the policy override via the Windows default state in BoosterX. According to Microsoft documentation, no reboot or service restart is required: the change is applied immediately.

After reverting, the specific behavior is determined by local Windows preferences. If they are not configured, Microsoft states detection, diagnostics and remediation enabled by default.

Public primary sources

ADMX_sdiagschd Policy CSP, Microsoft Learn - purpose of the policy, supported versions, Registry mapping, states and application without reboot.

The study was published by the BoosterX team and relates to a product setting. The presence of the setting in BoosterX was not used as proof of its effectiveness. BoosterX Wiki is not affiliated with, authorized by, sponsored by or endorsed by Microsoft Corporation.

Last source check: 2026-08-24.

Change history

2026-09-20: shortened the description to the search snippet limit.
2026-08-24: first public version based on Microsoft documentation and a static inspection of Windows 11 Pro 25H2.