Skip to content

Background ETW autologgers

On this page

Recommendation

Situational

Apply the disable if you are ready to give up the listed diagnostic traces and DiagTrack telemetry.

Update, compatibility and crash diagnostics will become less complete; FPS gains and latency reductions are not guaranteed.

Main effect
Disabling nine ETW sessions and DiagTrack
Confirmed benefit
−13.2 MB nonpaged pool
Required
Restart

What changes

Section titled “What changes”

An autologger is a Windows mechanism that starts ETW traces automatically at system boot. The BoosterX setting disables nine background diagnostic sessions: DiagLog, Diagtrack-Listener, LwtNetLog, NetCore, RadioMgr, ReFSLog, UBPM, WdiContextLog and WiFiSession.

The DiagTrack service (Connected User Experiences and Telemetry) is disabled as well: BoosterX stops it and blocks its automatic startup before modifying the logs, so that it does not recreate Diagtrack-Listener. Applying requires a restart.

Exceptions and differences

Section titled “Exceptions and differences”

Disabling reduces diagnostic data for investigating update, compatibility, network and radio issues. The features themselves do not break: the setting affects traces, not application services.

DiagTrack is also controlled by a separate card, “Telemetry services”: re-enabling the service may restore Diagtrack-Listener. The diagnostic data level is set by the “Telemetry in the data collection policy” setting.

Confirmed effect

Section titled “Confirmed effect”

In the study “How much memory can actually be freed”, disabling autologgers yielded −13.2 MB of nonpaged pool with all nine sessions and four background services fully disabled. The total working set of the disabled components was about 78 MB, while the real gain in free memory was +22–30 MB: part of what was disabled was not running anyway. This is a confirmed boundary of the effect, not a promise of proportional system acceleration.

How to verify the result

Section titled “How to verify the result”
  1. After applying and restarting, check in BoosterX that the setting is still applied.
  2. Open “Event Viewer” → “Applications and Services Logs” and make sure diagnostic entries from the listed sources no longer appear.
  3. In “Services” (services.msc), check that Connected User Experiences and Telemetry has the startup type “Disabled”.

How to change and revert

Section titled “How to change and revert”

In BoosterX, open “Optimization” → “Privacy” → “Windows diagnostics and reports” → “Background ETW autologgers” and set the toggle to “On”: BoosterX will disable the listed sessions and stop DiagTrack. Click “Apply” at the bottom of the page; with “Instant apply” enabled, the change is made immediately, then restart the PC. To revert, set the toggle to “Off” and apply the change: the autologgers will get their default startup parameters, and DiagTrack will start again after a restart.

Confirmation

Section titled “Confirmation”

Last check: 2026-09-22.