Microsoft has quietly changed how diagnostic data flows from its Edge browser on Windows 11 systems in the European Economic Area, a move that gives users independent control over a major source of telemetry. As of March 6, 2024, Edge diagnostic data is collected separately from Windows 11 telemetry on devices running version 23H2 and newer—and from Windows 10 version 22H2—within the EEA. The browser’s data collection is now governed by its own settings, entirely outside the Windows diagnostic data toggles that have long been the one-stop shop for privacy-conscious users.

What just changed for Edge and Windows telemetry

Until this month, Edge diagnostic data in the EEA was bundled with the rest of Windows’ telemetry. Flipping one switch in Settings—the diagnostic data level—applied to both the operating system and the browser. Now, that link is severed. Microsoft’s updated documentation now states that “Microsoft Edge diagnostic data is collected separately from Windows diagnostic data” on the affected systems, and “is subject to its own settings.”

The change applies only to devices in the European Economic Area, where privacy regulations have increasingly demanded granular, user-controlled consent. It does not affect the Rest of World, nor does it change how non-Edge applications or the Windows OS itself report telemetry. It simply means that Edge has its own dedicated pipeline for diagnostic data, with its own on/off switch that users must find and manage independently.

This separation also aligns with a broader EU-driven reconfiguration Microsoft has been rolling out since early 2023. Starting with the January 2023 preview cumulative update, devices joined to Microsoft Entra tenants with billing addresses in the EU or EFTA are automatically enrolled in the “Windows diagnostic data processor configuration.” Under that arrangement, the organization—not Microsoft—is the data controller responsible for responding to user data requests, and all diagnostic data from those devices is processed within Europe. For EEA users, Edge’s data split is another puzzle piece in a privacy landscape that now demands more active management.

Why this matters for your privacy

For the average Windows 11 user, the Edge split means one crucial thing: your existing Windows diagnostic data setting no longer covers the browser. If you’ve ever set “Send optional diagnostic data” to Off in the Privacy & security section, believing that was enough to minimize your digital trail, you may be surprised to learn that Edge could still be sending browsing-related telemetry to Microsoft unless you deliberately adjust Edge’s own privacy controls.

The change, while unwelcome news for those who thought they had everything locked down, is ultimately a win for transparency. It forces clarity: Windows telemetry and browser telemetry are different things, and they should be managed separately. The move also underlines how much data collection is baked into modern operating systems and browsers—and why a simple on/off fantasy is unrealistic.

Behind the scenes, Windows itself still classifies diagnostic data into several tiers. The most basic level, “Required diagnostic data” (previously called Basic), includes a fixed set of information critical for device health, such as hardware specs, crash dumps, and basic performance metrics. This level cannot be turned off on consumer editions of Windows 11; only Enterprise, Education, and Server editions can set the data to “Diagnostic data off (Security),” which sends nothing. The next level, “Optional diagnostic data” (formerly Full), adds detailed app usage, browsing history in Microsoft browsers, and enhanced error reporting—data that can feel highly personal.

That’s where the practical tension lies. Many users want to reduce the detail sent to Microsoft without breaking essential services like Windows Update or the Microsoft Store. And that tension is exactly what a recent, well-structured guide on WindowsForum addresses head-on, recommending a measured, reversible approach before anyone starts disabling system services.

The bigger picture: Windows diagnostic data settings explained

To make smart choices, you need to understand what each setting actually controls. Microsoft’s documentation—and the WindowsForum community guide—both highlight a hierarchy:

  • Diagnostic data off (Security): Available only on Enterprise, Education, and Server editions. Sends nothing. Windows Update information is also cut off, so if you rely on updates, this isn’t practical.
  • Required diagnostic data (Basic): The default on Windows 11 and Windows 10 version 1903 and later. Includes device attributes, basic quality metrics, crash dumps, and a list of installed apps. This data is essential for Microsoft to provide security patches and compatibility checks.
  • Optional diagnostic data (Full): Everything from Required plus detailed app and browser activity, device health logs, and in-depth error reports that may include memory contents when a crash occurs. This is the setting that most privacy-focused users want to dial back.

Importantly, Windows 11 no longer offers the “Enhanced” level that existed in older Windows 10 versions. For most home users, the choice is binary: Required vs. Optional. And while turning off Optional diagnostic data reduces the detail sent, it does not stop the Connected User Experiences and Telemetry service (internally called DiagTrack) from running. That service is the engine that ships all diagnostic data—both Required and Optional—to Microsoft’s servers.

That’s why some power users consider disabling DiagTrack outright. But as the WindowsForum guide wisely cautions, doing so can have unintended consequences. Services that depend on DiagTrack may fail to start, and some connected features might break. The guide’s core recommendation: always start with the least invasive change and work up only if you have a specific, measurable problem.

How to take control: a practical three-step approach

The WindowsForum decision tree offers a sensible path that balances privacy and functionality. Here’s how to put it into practice on your Windows 11 PC, with the news about Edge woven in.

Step 1: Turn off optional diagnostic data and tailored experiences

These are the easiest, safest adjustments—and they should always be your first move.

  1. Open Settings (Windows key + I) and go to Privacy & security > Diagnostics & feedback.
  2. Under Diagnostic data, look for Send optional diagnostic data. Toggle it Off.
  3. Just below that, find Tailored experiences. Toggle Let Microsoft use your diagnostic data, excluding info about websites you browse, to enhance your product experiences with personalized tips, ads, and recommendations to Off.

Turning off Optional diagnostic data strips away the extra detail—browsing history, app usage patterns, extended error logs—while leaving Required data untouched. Tailored experiences is a separate setting that stops Microsoft from using the diagnostic data it already collects to personalize tips, ads, and recommendations. They are two distinct toggles; switch both off for the broadest privacy gain without touching system services.

Now, about Edge: Because of the March 6 split, you must also adjust the browser’s own settings. In Edge, click the three-dot menu, go to Settings > Privacy, search, and services, and scroll to the Optional diagnostic data section. Here, you can turn off Send optional diagnostic data for the browser independently. Additionally, configure other privacy options like Send “Do Not Track” requests and manage which data Edge syncs with your Microsoft account. The exact wording may vary between Edge builds, but the principle is clear: Edge now has its own telemetry toggle, and you need to visit it.

Step 2: Measure before you break anything

If you’re still concerned about resource usage—CPU spikes, disk churn, or network activity—and you suspect DiagTrack is the culprit, don’t rush to disable it. First, quantify the problem. The WindowsForum guide recommends a controlled before-and-after measurement:

  • Restart your PC and let it idle for a few minutes.
  • Open Task Manager (Ctrl+Shift+Esc) and note overall CPU, disk, and network activity under normal conditions.
  • For a closer look, press Windows key + R, type resmon, and hit Enter to launch Resource Monitor. Watch the CPU, Disk, and Network tabs while you reproduce the workload that you suspect is slow.
  • Record the figures: which processes are active, how much of your resources they consume, and for how long.

This step is critical. Without measurements, any perceived improvement after disabling a service could be placebo. And if you later need to justify the change to an IT administrator (or yourself), numbers carry more weight than feelings.

Step 3: Disable DiagTrack only as a reversible test

If your measurements point to the Connected User Experiences and Telemetry service as a genuine drag, you can disable it temporarily—but treat this as an experiment, not a permanent fix.

  1. Press Windows key + R, type services.msc, and press Enter.
  2. Scroll down to Connected User Experiences and Telemetry (its internal name, DiagTrack, may not appear).
  3. Double-click the service and record its current Startup type (usually “Manual” or “Automatic”). You’ll need this to restore it later.
  4. Click Stop to halt the service immediately.
  5. From the Startup type dropdown, select Disabled.
  6. Click Apply and then OK.
  7. Restart your PC, repeat the same workload you measured earlier, and compare the numbers.

Now test your daily workflows. Open the Microsoft Store, check for Windows Updates, launch the Photos app, and see if anything misbehaves. Some connected experiences—like the “Timeline” feature or certain Cortana functions—rely on DiagTrack. If you hit a roadblock, don’t panic; just restore the original startup type, restart, and confirm the feature returns.

If the before-and-after comparison shows no meaningful benefit, re-enable DiagTrack immediately. The small privacy gain isn’t worth a potentially unstable system. Conversely, if you do see a measurable improvement and all your essential apps still work, you might choose to leave it disabled. But keep an eye on future Windows updates, which could reintroduce dependencies.

A word to admins and organization-managed devices: If any of the above toggles are grayed out or show “managed by your organization,” don’t hack the registry or apply unsanctioned Group Policy changes. Record the setting as is and talk to your IT department. Enterprise environments have approved configurations for a reason, and bypassing them can violate compliance policies.

What to watch for next

Microsoft’s decision to unbundle Edge telemetry in the EEA is almost certainly a reaction to tightening EU regulations, most notably the Digital Markets Act and the evolving GDPR enforcement climate. It wouldn’t be surprising to see similar splits for other Microsoft applications—Teams, OneDrive, or even Microsoft 365—in the near future. For now, the move underscores a simple truth: the days of one-switch-fits-all privacy are fading.

Keep an eye on the Windows 11 24H2 update, expected later this year. While Microsoft hasn’t announced further diagnostic data changes, the trend is toward more granular controls. Until then, the playbook is straightforward: toggle off Optional diagnostic data and Tailored experiences, manage Edge’s own data settings separately, and only venture into the Services console when you have hard evidence that DiagTrack is causing a real performance hit. Your privacy deserves a measured defense, not a scorched-earth one.