How to Disable DiagTrack in Windows 11 — Safe Step-by-Step Guide (2026)

DiagTrack, hidden behind a friendlier name since 2015, is still quietly running on almost every Windows 11 PC.

If you opened Task Manager after a fresh boot and noticed a background process spiking your CPU or disk for no obvious reason, there's a decent chance it was DiagTrack — officially called Connected User Experiences and Telemetry. It's been part of Windows since Windows 7, it's still present and unchanged in every Windows 11 release through 24H2 (the latest as of August 2026), and it runs on your machine right now whether you asked for it or not. Most users have no idea it exists.

I want to be straightforward with you before we go further: you'll find articles claiming this single service is quietly cooking your laptop and shaving years off its lifespan. From my own testing across a handful of laptops — old and new, Home and Pro — I couldn't reproduce that. DiagTrack runs at low process priority by design, it wakes up briefly (usually once a day, often right after startup), and on a healthy system its footprint is small. What is true, and worth acting on, is that it's a telemetry pipe sending usage data to Microsoft that you can turn off, it can occasionally misbehave (corrupted log files, conflicts with other services), and disabling it is one small, legitimate piece of a broader Windows privacy and lean-system routine.

In this guide I'll show you exactly what DiagTrack does, walk through the actual evidence around the "overheating" claim, and give you four different ways to disable it depending on your Windows edition and comfort level — GUI, Registry, Group Policy, and PowerShell. I'll also cover what most guides skip: what breaks when you turn it off, whether it actually helps gaming performance, and why it sometimes turns itself back on after an update.

I'm Mostafa Amaan, and on Valley4Techs I write practical, hands-on guides for people who actually manage their own PCs. Let's get into it.

Quick Reference: DiagTrack at a Glance

What DiagTrack Actually Is

DiagTrack has existed since Windows 7, where Microsoft added it to collect diagnostic data about how the OS was being used — crash reports, feature usage, hardware and driver status, and general system health. In 2015, Microsoft quietly renamed it to Connected User Experiences and Telemetry in the Services list, without a public announcement. It was tech communities, not a Microsoft blog post, that first noticed the rename — which didn't do much for user trust at the time.

Functionally, nothing changed with the rename. The underlying service name in the registry and via PowerShell is still DiagTrack. What it collects, according to Microsoft's own documentation and what shows up in Diagnostic Data Viewer, includes:

• Device and driver data — hardware specs, driver versions, peripheral connections
• OS and app usage — which built-in features and apps you open, how long you use them
• Performance and reliability data — crash dumps, error codes, boot times
• Connectivity data — Wi-Fi and network configuration status (not your browsing activity)
• Inking and typing data — only if you've opted into "tailored experiences," and it's about handwriting/typing patterns for feature improvement, not the content of what you type

DiagTrack appears in Task Manager's Details tab as utc.app.exe — you'll usually spot it consuming a brief CPU or disk spike shortly after boot.

Does DiagTrack Really Overheat Your Laptop and Shorten Its Life?

This is the claim that gets the clicks, so let's actually examine it instead of repeating it. The theory goes: DiagTrack wakes up, uploads data, causes a brief CPU/disk spike, your fans ramp up, and repeated heat cycles over years supposedly degrade your hardware faster.

Here's what I found when I actually watched this happen. On every laptop I tested — a five-year-old Core i5 ultrabook and a current-gen Ryzen machine — DiagTrack's scheduled upload runs briefly after boot or during idle periods, typically for a few seconds to low tens of seconds, and Microsoft deliberately runs it at below-normal process priority so it yields to whatever you're actually doing. That's simply not enough sustained load to meaningfully raise average operating temperature, and it's nowhere close to the kind of sustained thermal stress that actually degrades components over time — things like poor airflow, dust buildup, worn-out thermal paste, or running demanding workloads for hours on end. If you want to know what's genuinely shortening a laptop's usable life, our guide on common bad habits that shorten PC lifespan covers the factors that actually matter, and a background telemetry service isn't one of them.

Where the "spikes and heat" complaint has some truth to it is a specific edge case: if DiagTrack's ETL log files become corrupted, or if it's fighting for resources alongside SysMain (the old Superfetch) on a machine with a slow mechanical hard drive, you can see repeated, unusually long spikes. That's a real, fixable problem — but it's a symptom of misconfiguration or aging hardware, not evidence that DiagTrack itself is inherently dangerous to run.

So why bother disabling it at all? Two honest reasons: it's telemetry you may simply not want leaving your machine on principle, and on genuinely low-end or aging hardware, trimming every unnecessary background process adds up even if no single one is dramatic. Neither of those is "your laptop will die sooner" — but both are legitimate.

Does Disabling DiagTrack Improve FPS or Gaming Performance?

This is one of the most common questions in gaming forums and optimization communities, and it deserves a direct, evidence-based answer rather than the vague "disable everything for more FPS" advice that fills most Windows tweaking guides.

The short answer: disabling DiagTrack alone will not give you a meaningful, measurable FPS increase. On a healthy system, DiagTrack's CPU and memory footprint is negligible during gameplay — we're talking fractions of a percent of CPU time on any modern processor. If you're benchmarking a game and hoping to see your average FPS jump by 5 or 10 frames after disabling a single telemetry service, that's not going to happen.

Where it can make a noticeable difference for gamers is in a specific, narrow scenario: micro-stutter and frame-time spikes caused by background disk or CPU activity. If DiagTrack decides to flush its diagnostic data to disk or upload telemetry during a gaming session, that brief I/O burst can cause a single dropped frame or a hitch — the kind of stutter that shows up as a spike on a frame-time graph even if your average FPS looks fine. This is most noticeable on systems with a slow hard drive (not an SSD), limited RAM (8 GB or less), or an older dual-core CPU where a single background spike can actually compete for resources.

If you're serious about optimizing your gaming setup, disabling DiagTrack is one small piece of a much larger puzzle. The real gains come from driver updates, proper GPU settings, ensuring your power plan is set to High Performance, and — most importantly — making sure your hardware isn't thermally throttling. Disabling one background service won't compensate for a GPU running at 95°C because of dust-clogged fans.

Start Here: Reduce Telemetry Through Windows Settings

Before reaching for the Registry or PowerShell, there's a built-in, officially supported way to minimize what DiagTrack collects — and it's the method Microsoft actually intends you to use. It won't fully disable the service, but it reduces the telemetry data sent to Microsoft to the absolute minimum that your Windows edition allows.

1. Open Settings (Win + I)
2. Go to Privacy & security → Diagnostics & feedback
3. Turn off "Send optional diagnostic data"
4. Expand "Tailored experiences" and turn it off
5. Expand "Delete diagnostic data" and click Delete
6. Turn off "Improve inking and typing" if it's enabled

The Diagnostics & feedback page in Windows 11 Settings lets you limit telemetry to "Required" only — the easiest first step before using more advanced methods.

This sets your diagnostic data level to "Required" (previously called "Basic"), which limits collection to essential device info, error reports, and basic hardware data that Microsoft says it needs for security updates and driver compatibility. The "Optional" (previously "Full") level adds detailed app usage, browsing data within Microsoft apps, enhanced error reporting, and device activity history — all of which you almost certainly don't need to share.

For most users who just want to limit what Microsoft knows about their usage without touching system services, this is a perfectly valid stopping point. But if you want the service completely stopped, read on.

4 Ways to Disable DiagTrack (Pick Based on Your Edition)

All four methods below achieve the same result. Which one you should use depends mostly on your Windows edition and whether you want the change to stick through updates.

Method 1: Services.msc (Home & Pro)

The most direct method, and the one most guides lead with:

1. Press Win + R, type services.msc, press Enter
2. Scroll to "Connected User Experiences and Telemetry"
3. Right-click → Properties
4. Click "Stop"
5. Set "Startup type" to Disabled
6. Click Apply → OK

Setting the Startup type to "Disabled" in Services.msc stops DiagTrack immediately, but this change can be silently reset by major Windows feature updates.

This works immediately, but it's also the method most likely to get quietly reset. Feature updates (the big yearly/semi-annual Windows 11 upgrades) frequently reset service startup types back to their defaults, which is why several readers report the service "turning itself back on" after doing exactly this.

Method 2: Registry Editor (works on Home)

This is the method I'd actually recommend for Windows 11 Home users, since Home edition doesn't include the Group Policy Editor:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection

Create (or edit) a DWORD (32-bit) value:
Name:  AllowTelemetry
Value: 0

The AllowTelemetry DWORD set to 0 under the DataCollection key — this policy-level change survives routine updates better than a simple service toggle.

If the DataCollection key doesn't exist yet, right-click Windows → New → Key, name it DataCollection, then create the DWORD inside it. Restart afterward. Because this sets an actual telemetry policy rather than just flipping a service switch, it tends to survive updates better than Method 1 alone — though it's still worth re-checking after major feature updates.

Method 3: Group Policy (Pro, Enterprise, Education only)

If you're on Windows 11 Pro or higher, Group Policy is the cleanest option because it's designed exactly for this and is what IT admins use to manage telemetry across a fleet of machines:

1. Press Win + R, type gpedit.msc, press Enter
2. Navigate to:
   Computer Configuration → Administrative Templates →
   Windows Components → Data Collection and Preview Builds
3. Double-click "Allow Diagnostic Data"
4. Set to Enabled, then choose the lowest option
   (Security / Diagnostic data off, depending on edition)
5. Apply → OK, then restart

Group Policy enforces telemetry settings on every boot, making it the most update-resistant method available on Windows 11 Pro and Enterprise editions.

Group Policy settings are enforced on every boot, which makes this the most update-resistant method of the four — Windows re-checks the policy rather than relying on a one-time toggle.

Method 4: PowerShell (fastest, scriptable)

If you're comfortable with the command line, or you're doing this across multiple machines, PowerShell as Administrator gets it done in two lines:

Stop-Service -Name DiagTrack -Force
Set-Service -Name DiagTrack -StartupType Disabled

To verify it actually took effect:

Get-Service -Name DiagTrack | Select-Object Status, StartType

The verification output should show Status: Stopped and StartType: Disabled — confirming the service is fully off.

You want to see Status: Stopped and StartType: Disabled. This is also the method I'd use if you're managing several family or office PCs — you can drop it into a script and run it remotely instead of clicking through Services.msc on each machine.

Don't Stop There: The Companion Service Most Guides Skip

Here's a gap I noticed in most coverage of this topic, including the article that prompted this guide: DiagTrack has a lesser-known companion, dmwappushservice (WAP Push Message Routing Service), which handles push notification-based data routing and works alongside DiagTrack for some telemetry and provisioning tasks. Disabling DiagTrack alone leaves this one running.

Stop-Service -Name dmwappushservice -Force
Set-Service -Name dmwappushservice -StartupType Disabled

It's a low-impact service on its own, but if your goal is genuinely minimizing what Windows reports back to Microsoft rather than just chasing a CPU graph, this is the piece that actually completes the job.

Third-Party Privacy Tools: Are They Worth Using?

If you've searched for "disable Windows telemetry" before, you've almost certainly come across tools like O&O ShutUp10++, Privatezilla, or W10Privacy — free utilities that promise to disable dozens of Windows telemetry and privacy settings with a few clicks. They have massive followings, and the appeal is obvious: why navigate the Registry and Group Policy manually when a single tool can flip 50 switches at once?

Here's my honest take after using several of these tools over the years: they do work, and the reputable ones (particularly O&O ShutUp10++, which has been consistently maintained and is from a well-known German software company) are generally safe to use. The problem isn't whether the tool does what it says — it's that most users click the "apply all recommended settings" button without understanding what each toggle actually does.

The Risks of Blind One-Click "Privacy" Tweaks

These tools don't just disable DiagTrack. They can also:

• Disable Windows Update delivery optimization — which can slow down how quickly your machine gets security patches
• Block Microsoft Store functionality — breaking app installs and updates
• Disable cloud clipboard, timeline, and activity history — features some users actually rely on across devices
• Interfere with Cortana or Windows Search indexing — leading to broken Start Menu search, which is one of the most common complaints after running these tools aggressively
• Modify firewall rules or hosts file entries — potentially breaking Microsoft 365, Teams, or OneDrive sync

None of this means you shouldn't use them. It means you should use them selectively: open the tool, read what each toggle does, and apply only the settings you actually understand and want. The "recommended" defaults in most of these tools are chosen by the developer's personal preference, not by what's universally safe for every user.

What Actually Breaks When You Disable It

This is the section every DiagTrack article should have and almost none do. Disabling DiagTrack is reversible and low-risk, but it isn't consequence-free. Here's the honest trade-off breakdown:

For nearly every home user, none of this matters day to day. The one scenario where I'd tell you to think twice: if you regularly rely on Feedback Hub to report bugs to Microsoft, or you're troubleshooting a hardware issue under warranty support, temporarily re-enable the service first so diagnostics can actually be collected.

How to Re-Enable DiagTrack If You Change Your Mind

Every disable guide should tell you how to undo it — and almost none do. Whether you need to temporarily re-enable DiagTrack for a Microsoft support session, because you've run into unexpected issues, or simply because you changed your mind, here's how to reverse each method cleanly.

Revert via PowerShell (fastest)

Set-Service -Name DiagTrack -StartupType Automatic
Start-Service -Name DiagTrack

# If you also disabled the companion service:
Set-Service -Name dmwappushservice -StartupType Automatic
Start-Service -Name dmwappushservice

Revert the Registry change

Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection and either delete the AllowTelemetry DWORD entirely, or change its value from 0 to 1 (Required/Basic) or 3 (Optional/Full). Restart afterward.

Revert Group Policy

Open gpedit.msc, navigate back to Computer Configuration → Administrative Templates → Windows Components → Data Collection and Preview Builds, double-click "Allow Diagnostic Data," and set it to Not Configured (which returns to Windows defaults). Restart afterward.

Revert Services.msc

Open services.msc, find "Connected User Experiences and Telemetry," set the Startup type back to Automatic (Delayed Start), click Start, then Apply → OK.

Why DiagTrack Sometimes Turns Itself Back On

If you've disabled DiagTrack before and found it running again weeks later, you're not imagining it. Major feature updates in Windows 11 (the annual or semi-annual version upgrades, not routine patches) reinstall and reconfigure a number of default services, including DiagTrack, and can silently reset its startup type back to Automatic. This has been a recurring complaint since the Windows 10 era — it happened after the "Threshold 2" update years ago, and similar resets still occur on Windows 11 today.

Practical takeaway: if you disable DiagTrack, add a quick check to your post-update routine. After any major Windows 11 feature update, re-run the PowerShell verification command from earlier in this guide, or just glance at Services.msc. It takes ten seconds and saves you from wondering why your "disabled" service is suddenly active again.

5 Mistakes I See People Make With This

1. Blaming DiagTrack for every performance issue. If your PC is genuinely slow, disabling one lightweight background service almost never fixes it. Run a proper diagnostic first — our guide on why your PC is getting slower even though the hardware hasn't changed covers the usual real culprits.
2. Only disabling DiagTrack and skipping dmwappushservice. If your goal is minimizing telemetry, not just chasing a process in Task Manager, disable both.
3. Assuming it's permanent. As covered above, feature updates can quietly re-enable it. Check again after each major Windows 11 update.
4. Editing the wrong Registry key. Double-check you're under Policies\Microsoft\Windows\DataCollection, not a similarly-named key elsewhere. A misplaced value does nothing useful and adds clutter.
5. Confusing "telemetry off" with "invisible online." Disabling DiagTrack reduces what Windows itself reports to Microsoft — it does nothing for your browsing activity, your ISP's visibility, or tracking by websites and apps. If broader online privacy is the actual goal, that's a separate project involving your browser and network settings. Our VPN and browser privacy settings guide is the right next step if that's what you're after.

Final Thoughts

DiagTrack is worth disabling if you value keeping usage telemetry off your machine — that's a completely reasonable position on its own, and it takes about two minutes with any of the four methods above. What I'd push back on is the idea that this one service is meaningfully cooking your hardware or cutting years off its life. I couldn't find evidence for that when I actually watched it run, and the mechanism doesn't hold up under scrutiny for a properly functioning system. Disable it for privacy and a marginally leaner background footprint — not because you're rescuing your laptop from an early grave.

If you're doing a broader Windows 11 privacy pass, this is a good first stop, but not the last one. Pair it with a look at your firewall rules if you want tighter control over what leaves your network in general — our comprehensive firewall and network security guide is a solid next read.

Frequently Asked Questions