Skip to content

Scheduled Diagnostics

On this page

Recommendation

Situational

Leave Windows default if you need the standard preventive diagnostics. If you disable it, some problems will have to be tracked manually.

Disabling it prohibits the scheduled launch of diagnostic packages, but does not disable all Windows diagnostics. FPS gains, latency reduction and RAM savings are not confirmed.

Usually chosen
Windows default
Main effect
Blocking Scheduled Diagnostics
Reboot
Not required

In short

Section titled “In short”

“Scheduled Diagnostics” controls the preventive launch of Windows diagnostic packages. When disabled, these packages stop detecting problems on a schedule and performing automatic fixes.

The setting does not turn off sfc, chkdsk, Microsoft Defender, disk optimization, manual troubleshooting tools or all automatic maintenance tasks.

What changes

Section titled “What changes”

When disabled, the corresponding system task may still exist and launch its handler, but the policy prohibits it from running diagnostic packages.

Returning to Windows default removes the explicitly set policy. After that, Windows uses the local troubleshooting settings. According to Microsoft documentation, if there are no such settings, diagnostics are enabled by default.

Registry changes

Section titled “Registry changes”

The setting is available in the free version of BoosterX. The table shows its registry values.

Field Value
Hive and path HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\ScheduledDiagnostics
Value name EnabledExecution
Type REG_DWORD
Disabled 0
Windows default Value absent
Revert Delete EnabledExecution via the Windows default state in BoosterX

Use BoosterX to change and revert. There are no ready-made .reg and PowerShell commands on this page.

Possible effect and trade-off

Section titled “Possible effect and trade-off”

Disabling stops the execution of diagnostic packages on this schedule. If they were not running during your workload before either, there will be no measurable change.

Windows will no longer detect and automatically fix some system problems in advance this way. Static research does not confirm savings in CPU, RAM and I/O or improvements in FPS, frametime and input latency.

Recommendation

Section titled “Recommendation”
  • Leave Windows default if you need standard diagnostics.
  • Disable the scheduled launch of diagnostic packages only if you are ready to track problems yourself.
  • Enabling the setting in an optimization profile does not by itself prove its benefit for your computer.

How to verify the result

Section titled “How to verify the result”
  1. Record the initial state in BoosterX.
  2. Change only “Scheduled Diagnostics” without disabling other maintenance components at the same time.
  3. Make sure Windows continues to run the manual diagnostic tools you need.
  4. If you are evaluating the load, compare several identical periods and do not treat the absence of a task launch as proof of acceleration.
  5. If problems appear, return Windows default.

How to change and revert

Section titled “How to change and revert”

In BoosterX, open “Optimization” → “Tweaks” → “Maintenance and diagnostics” → “Scheduled Diagnostics” and switch the toggle to “Enabled”: BoosterX will apply the prohibition of the scheduled launch of diagnostic packages. Click “Apply” at the bottom of the page. If “Instant apply” is enabled, the change is made immediately.

To revert, switch the toggle to “Disabled” and click “Apply”: BoosterX will delete the explicitly set policy and return control to Windows.

A reboot is not required. According to Microsoft documentation, the policy change is applied immediately. Scheduled Diagnostics itself works only when the Task Scheduler service is running.

Sources and verification boundaries

Section titled “Sources and verification boundaries”

The exact mechanism was statically verified on Windows 11 Pro 25H2 build 26200.8655 x64. Windows 10, Windows Home and Windows Server have not undergone the same verification. The performance impact was not measured.

Last verified: 2026-09-20.