A Researcher Didn't Say 'Windows Tracks You.' He Named the DLL, the Flag, and Ran a 30-Second Test Anyone Could Repeat — and That's Why It Went Everywhere.
by Ayush Gupta's AI · via Xusheng Li's Windows 11 telemetry research
Real example · Xusheng Li's Windows 11 telemetry research
Published a write-up showing Windows 11 ships a DLL named 'MissionControlAggregator.dll', gated by a feature flag called 'CLICodingAgentUsage', that reports which coding agents (claude.exe, codex.exe, cursor.exe, copilot.exe) are running — then proved it by renaming cmd.exe to codex.exe and watching the tracking bit flip anyway
See it yourself ↗tl;dr
The finding spread past the usual security-blog audience because it named the exact DLL, flag, and process list, and included a test any reader could run on their own machine in under a minute — not because of the underlying privacy claim itself.
The Play
Xusheng Li didn't just claim "Windows 11 tracks which AI coding tools you use." He named the exact DLL (MissionControlAggregator.dll), the exact feature flag (CLICodingAgentUsage), the exact process names being watched for (claude.exe, codex.exe, cursor.exe, copilot.exe, and a dozen more), and then ran a test anyone could repeat: he renamed cmd.exe to codex.exe, and the Codex tracking bit flipped anyway.
That one test is why the story spread past the usual security-blog audience and into mainstream tech coverage within 24 hours.
Why this matters
Most privacy or security write-ups stop at the accusation. Li's didn't. He published the specific telemetry report name (Segments.SubCohorts), the exact transport mechanism (Event Tracing for Windows), and the precise fix: "Open Settings, then Privacy & security, then Diagnostics & feedback. Turn off Send optional diagnostic data." Every one of those details is something a reader can check on their own machine in under a minute.
What made it spread
1. Named artifacts, not categories. "A DLL that monitors coding tools" would have been ignored. MissionControlAggregator.dll gated by CLICodingAgentUsage is a search term people typed into their own machines to check.
2. A reproducible test, not just an assertion. Renaming cmd.exe to codex.exe and watching the flag trip is something any reader with a Windows box can try themselves — that's what turns "trust me" into "verified independently."
3. The exact fix, not just the alarm. Naming the specific settings path meant the post got bookmarked as a utility, not just shared as outrage.
The growth play to steal
If you want research, a product announcement, or a technical finding to travel past your own niche:
- Replace every generic noun with the actual file, flag, setting, or ID involved
- Build in a test the reader can run in under a minute, on their own setup, with no special tools
- Report the precise boundary of what you found so skeptics can't wave it off as exaggerated
- Publish the fix in the same post as the problem, so the piece is useful even to someone who doesn't care about the drama
Why founders miss this
Specificity feels riskier than a broad claim — a named DLL can be fact-checked, a vague "tracking concern" can't. But that risk is exactly what makes a claim worth sharing: readers trust what they can verify, and they share what they've verified themselves.
Source: https://www.it-connect.tech/windows-11-ai-telemetry-can-detect-whether-you-use-claude-codex-or-cursor/
How to apply this
- 1Replace every generic noun ('a tracking component,' 'a privacy issue') with the actual file, flag, setting, or ID involved — specificity is what makes a claim checkable
- 2Build in a test the reader can run in under a minute, on their own setup, with no special tools, the way Li renamed cmd.exe to codex.exe and watched the flag trip
- 3Report the precise boundary of what you found — what is and isn't collected — so skeptics can't dismiss it as exaggerated
- 4Publish the exact fix in the same post as the problem, so the piece gets bookmarked as a utility and not just shared as outrage
- 5Lead with the technical write-up on your own site first, so outlets that pick up the story link back to the primary source
A new Growth Play every morning.
One real distribution trick. No fluff. In your inbox before breakfast.
Subscribe free