Microsoft allows users to dial back diagnostic data collection in Windows 11, but a new analysis confirms you cannot shut it off entirely. The report, published by Pakistan Today on July 12, 2026, highlights that even the most restrictive privacy setting leaves several categories of telemetry running in the background.

While the findings won’t surprise anyone who has followed Windows’ privacy evolution, they serve as a sharp reminder that the operating system is designed to maintain a baseline data pipeline to Redmond, no matter how you configure the on-screen switches.

What the report found

At the heart of Pakistan Today’s analysis is a straightforward observation: Windows 11 continues to collect and transmit device, configuration, and usage information during normal operation, and the controls offered to users merely reduce the volume of data, not eliminate it.

The operating system’s diagnostic data settings work on a two-tier model. The first, called “Required diagnostic data,” is always on. It captures information about your device’s hardware, its capabilities, basic performance metrics, and whether the system is functioning correctly. The second, “Optional diagnostic data,” layers on more detailed usage patterns, app activity, browsing habits (through Edge), and enhanced error reporting. While users can decline to share optional data, the required stream remains active.

That required stream isn’t just a few anonymous bits, either. According to Microsoft’s own documentation — and corroborated by the report — it encompasses device properties (like processor type, memory, and storage), network information (connection type, speeds, and IP-derived location), event logs detailing system crashes and hangs, and data on which features are being used. If a hardware component fails or a driver misbehaves, that information gets uploaded automatically.

Crucially, the report points out that some of this data can be associated with a unique device identifier, allowing Microsoft to tie telemetry to a specific machine over time. While the company states it does not use required diagnostic data for advertising or personalized experiences, the persistent linkage raises questions about how effectively privacy can be managed when the identifier itself is part of the package.

The data that Windows 11 always sends

To understand what you’re really sharing, it helps to break down the contents of the required data channel. Microsoft publishes an exhaustive list, but the key categories are:

  • Device and PC attributes: Make, model, CPU, RAM, storage capacity, display resolution, battery type, and firmware version.
  • Network and connectivity: Adapter types, mobile operator (if applicable), signal strength, IP address, and nearby Wi-Fi access points.
  • Quality-related data: App hangs, system crashes, Blue Screen of Death (BSOD) dumps, driver failures, Windows Update success/failure logs, and reliability metrics.
  • Software inventory: Installed operating system edition, installed applications (limited to those Microsoft deems “relevant to updates and compatibility”), and driver versions.
  • in-use features: Which Windows components — like Cortana, Widgets, or Snap Assist — you interact with, and how often.

None of this data includes the content of your documents, keystrokes, or webcam streams, but the aggregate picture can be surprisingly detailed. If a user plays a specific game that causes a GPU driver crash, for instance, the telemetry can contain the game’s name and the time it was running, which some privacy advocates consider more revealing than necessary for remote debugging.

Who this matters to — and why

For everyday home users, the practical impact grades out as low to moderate. Microsoft uses the telemetry to patch bugs, deliver driver updates, and detect security threats before they spread. A typical Windows 11 laptop is a safer, more stable device because of this data flow. Yet the inability to go fully off-grid rankles anyone who wants complete control over outbound traffic.

IT professionals and system administrators face a sharper dilemma. In regulated industries — finance, healthcare, government — data sovereignty policies often demand that no telemetry leave the environment without explicit, informed consent. The required diagnostic baseline can complicate compliance audits, especially when the data includes network identifiers that could be considered personal information under GDPR or similar laws. While enterprise editions of Windows 11 offer a “Security” telemetry level (level 0) that limits uploads to the absolute minimum needed for Windows Update and Defender, that setting isn’t available to Professional or Home users, leaving many organizations with a gap they must bridge through network controls or third-party tools.

Developers and power users have a more nuanced relationship with telemetry. Many welcome the rapid bug fixes that the data enables, but they also chafe at the opacity. Without clear visibility into exactly what’s being sent — beyond Microsoft’s broad disclosures — it’s hard to audit whether a particular setting change actually reduces data leakage or simply re-labels the packets.

How telemetry became mandatory

Windows didn’t always phone home by default. With Windows 7, users could opt out of the Customer Experience Improvement Program (CEIP) entirely. That changed with the launch of Windows 10 in 2015, when mandatory telemetry sparked immediate backlash. Microsoft argued that the shift was necessary to deliver a “Windows as a Service” model, where continuous feedback from millions of devices would allow faster iteration and proactive fixes.

Over successive updates, the company refined the nomenclature and the controls. The old “Basic” level became “Required,” and “Full” became “Optional.” The privacy dashboard at account.microsoft.com gained tools to view and delete some of the stored data. Enterprise customers obtained group policy objects (GPOs) to force telemetry to the floor, but only on specific SKUs. Throughout, Microsoft has maintained that no version of Windows 10 or 11 can operate with zero telemetry, because certain functions — notably, cloud-delivered protection via Microsoft Defender and urgent security updates — depend on a heartbeat signal.

Privacy regulators in Europe and elsewhere have scrutinized this stance. The French data protection authority, CNIL, issued a compliance order regarding Windows 10 telemetry in 2022. Microsoft responded by making the privacy setup experience more granular and clarifying data collection purposes, but stopped short of offering a true off switch. The Pakistan Today report is the latest in a long line of reminders that the architecture hasn’t fundamentally changed.

Steps to cut down on Windows 11's tracking

You can’t reach zero, but you can get close. Here’s what to do right now:

  1. Dial down diagnostic data to Required. Go to Settings > Privacy & security > Diagnostics & feedback. Set “Diagnostic data” to Required diagnostic data. This removes the optional stream, which includes browsing history, speech transcripts, and detailed app usage.

  2. Turn off tailored experiences. On the same page, switch off “Tailored experiences.” This stops Windows from using your diagnostic data to personalize tips, ads, and recommendations inside the OS.

  3. Adjust feedback frequency. Still in Diagnostics & feedback, set “Feedback frequency” to Never. This stops Windows from randomly prompting you to answer surveys about your experience.

  4. Disable inking and typing data. Navigate to Settings > Privacy & security > Inking & typing personalization and switch off the toggle. This prevents words you type on the touch keyboard or pen input from being sent to the cloud.

  5. Review all privacy permissions. Work through each category under Settings > Privacy & security — especially location, camera, microphone, and app diagnostics — and revoke access for anything that doesn’t need it.

  6. Use a local account (optional). Signing in with a local account instead of a Microsoft account limits some data linkage, though required telemetry still operates at the device level.

For Professional users who can’t access the “Security” telemetry level, a workaround exists via the Group Policy Editor (if the system runs Windows 11 Pro or higher). Navigate to Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds. Enable “Configure Telemetry” and set it to 0 – Security. While this policy was originally meant for Enterprise and Education editions, it often applies on Pro as well, reducing transmitted data to just the essentials for malware protection and critical updates – though Microsoft does not officially support this configuration on Pro. Test thoroughly before deploying in a production environment.

Network-layer controls add another layer. Administrators can use firewall rules to block known telemetry endpoints at the perimeter. Microsoft publishes a list of required URLs for Windows operations. Blocking outside that list can stifle updates and Defender signatures, but a carefully crafted allowlist can limit data leakage without breaking functionality. This approach requires ongoing maintenance, however, as Microsoft adds and rotates endpoints regularly.

What comes next

Don’t hold your breath for a full opt-out toggle. Microsoft’s business model and engineering practices are now deeply intertwined with telemetric feedback, and the company’s public messaging frames required data as a non-negotiable foundation of a secure, modern OS. Regulatory pressure could slowly shift the dial — the European Union’s Digital Markets Act and future ePrivacy reforms may force greater transparency or user choice — but any change will be measured in years, not months.

Until then, Windows 11 users are left with a pragmatic trade-off. The plug can’t be pulled completely, but by combining the right settings, local account choices, and network vigilance, you can shrink the data fire hose down to a trickle. For most, that will be good enough. For the privacy absolutist, it remains a bitter pill.