Skip to content

Recommendation

Situational

For a developer it can be disabled: dotnet commands send usage data by default, and BoosterX advises disabling it for everyone who does not send feedback to the .NET team.

If the .NET SDK is not installed and dotnet commands do not run, no data is sent and the setting changes nothing.

Main effect
Disabling .NET SDK telemetry
FPS and memory
FPS is not affected

This concerns the telemetry of the .NET SDK and CLI tools — commands such as dotnet build or dotnet run, not applications written in .NET. According to Microsoft’s public documentation, collection is enabled by default: when commands are executed, information about the command and its parameters, the SDK version and the operating system is sent, and when the CLI crashes, the exception name and the call stack of the tool code are sent. Running an application via dotnet does not generate telemetry: data is collected only for tool commands.

Disabling is about privacy, not speed: telemetry does not interfere with the operation of commands, and no performance gain should be expected. On the first run of an SDK command, a telemetry notice is shown — this is expected behavior, not an error. Telemetry of .NET applications and web services is not affected: they send only what their developer implemented.

Open a new terminal window — environment variables are read when it starts — and run $Env:DOTNET_CLI_TELEMETRY_OPTOUT: the variable must be set.

Open “Optimization” → “Privacy” → “Dev tools and CLI” → “Dot Net Telemetry”, move the toggle to the “On” position: BoosterX will apply the opt-out of .NET CLI telemetry. Click “Apply”. If “Instant apply” is enabled, a separate button is not required. To revert, move the toggle to the “Off” position and apply the change again: BoosterX will return Windows to its default state with .NET telemetry enabled; a new terminal window will pick up the variable.

Last verified: 2026-09-19.