DEV Community

Cover image for How to Turn Off Windows 11 Telemetry That Tracks Claude Code, Codex and Cursor
Alan West
Alan West

Posted on Originally published at blog.authon.dev

How to Turn Off Windows 11 Telemetry That Tracks Claude Code, Codex and Cursor

Windows 11 has a list of coding agents baked into a system DLL. If you run claude.exe, codex.exe, cursor.exe or copilot.exe, a telemetry component notices, sets a bit, and, if optional diagnostic data is on, queues a report for Microsoft. It does the same for gcc.exe, python.exe, node.exe and code.exe. I went through what the component records, why calling it "optional" is misleading, and the five steps I used to turn Windows 11 telemetry off on my own dev box. The last step is a PowerShell check so you can prove it worked.

The finding comes from Xusheng's writeup, published 16 November 2026, which hit the Hacker News front page with roughly 700 points and close to 600 comments. I'll stick to what the post actually shows, because the thread has already started inflating it.

What Windows 11 is collecting about your dev tools

The code lives in MissionControlAggregator.dll (version 10.0.26100.9818 on the test machine, a Parallels Windows 11 ARM64 VM on build 26200.9974). It holds executable-name matchers in two groups.

Coding agents:

  • CLI slots: copilot.exe, claude.exe, codex.exe, agy.exe, plus the extensionless equivalents inside WSL
  • Desktop slots: github.exe, claude.exe, codex.exe, cursor.exe, antigravity.exe

Developer tools, grouped by category: node.exe, python.exe, dotnet.exe, gcc.exe, clang.exe, gdb.exe, javac.exe, devenv.exe, code.exe and others. Some slots also check the publisher string (Node.js Foundation, Python Software Foundation). The GCC/Clang group doesn't, so any binary named gcc.exe counts.

The inputs are existing ETW events: KernelProcess.AppStateChangeSummary for regular programs, Win32kTraceLogging.AppInteractivitySummary for desktop apps, and Microsoft.Windows.Lxss.Manager.Exec for WSL, which reads the imageName field. You don't need WSL for this. A plain Windows codex.exe trips the CLI matcher.

The output is a Segments.SubCohorts event from the Microsoft.Windows.MissionControlAggregator provider, with fields like CliAgentSubCohorts and DesktopAgentSubCohorts. Each tool category is one bit. Running a copy of codex.exe produced CliAgentSubCohorts: 4, which is 1 << 2. A copy of gcc.exe produced SubCohorts: [8]. Reports cover a roughly daily window.

The whole thing is gated behind a feature flag, CLICodingAgentUsage (ID 62580080). On the test VM it had already been switched on as a service experiment. The author didn't enable it. Nobody opted in to anything; Microsoft flipped the flag on from their side.

What it isn't

The writeup found no prompts, no source code, no runtime, no focus time and no interaction counts. All the event records is which categories of tool showed up during a window, which is pretty coarse.

It is also marked "isRequired": false, so it counts as optional diagnostic data and not the Required level that Home and Pro users can't switch off. A lot of HN comments get this wrong. The author confirmed the event was queued for upload in DiagTrack's EventStore.db, but didn't capture it going over the wire.

That doesn't make it fine, though. On a clean Windows 11 Home install from the official ISO with the region set to US, the Diagnostic data toggle defaulted to "Include Optional". So "optional" here means on unless you noticed the toggle during setup and turned it off.

The name gives the purpose away: "cohorts". Microsoft is segmenting its users by which AI agents they use, and it shipped the classifier in a system DLL and switched it on through a feature flag before any of us knew it existed. If you wanted a number for how many Windows machines run Claude Code versus Copilot CLI, this is how you would get it. I can see why a product team wants that. I still don't want my dev box doing their market research.

Step 1: turn off optional diagnostic data

This kills the event in the writeup. It works on every edition.

Settings → Privacy & security → Diagnostics & feedback → turn off Send optional diagnostic data. While you're there, turn off Tailored experiences too.

One HN commenter's advice was not to trust the Settings toggle at all, on the grounds that Windows overrides user settings but leaves Group Policy alone. I haven't seen a documented case of an update flipping this particular toggle, but locking it with policy costs two minutes, so do that next.

Step 2: lock it with Group Policy or the AllowTelemetry registry key

On Pro, Enterprise or Education, open gpedit.msc and go to:

Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds

  • Allow diagnostic data: Enabled, set to the lowest option offered
  • Limit diagnostic log collection: Enabled
  • Limit dump collection: Enabled
  • Configure diagnostic data opt-in settings user interface: Enabled, set to "Disable diagnostic data opt-in settings", so the Settings toggle can't be raised again

Home has no gpedit, so set the policy value directly from an elevated PowerShell:

New-Item -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection' -Force | Out-Null
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection' -Name AllowTelemetry -Type DWord -Value 0
Enter fullscreen mode Exit fullscreen mode

What most guides leave out is that, per Microsoft's own documentation, "Diagnostic data off" (value 0) "is only available on Windows Server, Windows Enterprise, and Windows Education editions." Home and Pro treat it as Required (1). Setting 0 still helps, since it pins you at the floor, but you can't get below Required on those editions this way.

Required isn't a small set, either. The same doc lists "app state change details, such as how much processor time and memory were used, and the total uptime for an app" and compatibility data about "which apps are installed on a device". The agent cohort bitfield is optional, but the Required level already gets your installed app list and per-app uptime, and Home and Pro users have no switch to turn that off.

Level AllowTelemetry Home / Pro Enterprise / Education
Diagnostic data off 0 Treated as 1 Honoured
Required 1 Default floor Available
Optional 3 Was the default on the writeup's clean Home install Available

Step 3: the DiagTrack service

The aggregator runs as AggregatorHost.exe, a child of the DiagTrack service ("Connected User Experiences and Telemetry"), which is set to Automatic. Microsoft doesn't document any supported way to get below Required on Home or Pro. Disabling the service is the unsupported way, and it's what I do:

Stop-Service DiagTrack -Force
Set-Service DiagTrack -StartupType Disabled
Enter fullscreen mode Exit fullscreen mode

This has a cost. Microsoft notes that with no diagnostic data, information about Windows Update failures isn't sent. On a personal dev machine I accept that. Don't do this on a fleet managed with Intune update reports, because they depend on this data.

Step 4: block the endpoints

Microsoft publishes the Connected User Experiences and Telemetry upload hosts:

v10.events.data.microsoft.com
v10c.events.data.microsoft.com
v10.vortex-win.data.microsoft.com
Enter fullscreen mode Exit fullscreen mode

Block them at your router, Pi-hole or firewall instead of relying on the hosts file alone, so a single settings change on the box can't undo it. Microsoft asks you not to block settings-win.data.microsoft.com, which it says is the remote config channel and doesn't upload diagnostic data. That's also the kind of channel that lets an experiment like CLICodingAgentUsage get switched on without your input, so you can decide for yourself whether to take their advice.

Step 5: check what's still being sent

Don't trust any of the steps above until you've checked the output. Microsoft's Diagnostic Data Viewer for PowerShell does this from an elevated prompt:

Install-Module -Name Microsoft.DiagnosticDataViewer
Enable-DiagnosticDataViewing
# use the machine normally for a while, run claude / codex / cursor
Get-DiagnosticData -StartTime (Get-Date).AddHours(-12) | Export-Csv 'mydata.csv'
Select-String -Path .\mydata.csv -Pattern 'MissionControlAggregator','SubCohorts'
Disable-DiagnosticDataViewing
Enter fullscreen mode Exit fullscreen mode

Run the check once before you change anything and again after Step 1, while DiagTrack is still running. Seeing an event in the viewer doesn't mean it has already been uploaded; Microsoft notes some may still be queued. If SubCohorts shows up after Step 1, something re-enabled optional data. Turn viewing off when you're done: it stores up to 1 GB or 30 days of events, and Microsoft's docs put the average device at about 6 MB of diagnostic data a day.

You can also confirm the policy and service stuck:

Get-ItemProperty 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection' | Select-Object AllowTelemetry
Get-Service DiagTrack | Select-Object Status, StartType
Enter fullscreen mode Exit fullscreen mode

Is this the push to Linux?

Much of the HN thread turned into a Linux migration argument. One of the better counterpoints was that Intel, AMD and NVIDIA drivers already collect the executable names and paths you run unless you opt out, and that most Chrome setups end up keeping your full browsing history in a Google account. Fair enough. On its own this event is mild; it's a bitfield. What bothers me is that the OS shipped a classifier for which AI vendor I use, enabled it through a server-side experiment, and set the toggle that covers it to on by default.

My setup is optional data off, policy locked, DiagTrack disabled, endpoints blocked at the router, plus a re-check with Get-DiagnosticData after every feature update. Took about ten minutes.

Did you know Windows was fingerprinting your toolchain? Are you blocking it and staying on Windows, or is this what finally moves your dev box to Linux? And if you've caught the optional toggle flipping back on after an update, post your build number below.

Sources

Top comments (0)