How to Disable Windows 11 Telemetry in 2026: The Ultimate Privacy Guide

Updated on May 6, 2026

Even in 2026, learning how to disable Windows 11 telemetry (and on older versions) is one of the most critical tweaks you can make to protect your privacy and boost system performance. While Microsoft uses this diagnostic data to fix bugs and improve the user experience, the amount of “optional” data it collects can be excessive—gathering intel on your app usage, browsing history, and even snippets of your voice and text input.

For users who put a premium on privacy or want to squeeze every last drop of performance out of their rig, reining in this data collection is a must. This definitive guide will walk you through four distinct methods to turn off Windows telemetry, from the dead-simple UI-based approach to a comprehensive automated script, so you can pick the one that best fits your needs and technical comfort level.

In this updated 2026 guide, you’ll discover:

• What telemetry is and what data each level collects in the latest versions of Windows.
• Four methods to disable telemetry: from Windows Settings to the Group Policy Editor, the Registry Editor, and a powerful PowerShell script.
• A side-by-side comparison table to help you decide which method is right for you.
• How to reverse the changes if you ever need to restore the original settings for advanced diagnostics.

Disclaimer: The content in this article is for informational and educational purposes only. We do not develop or distribute any of the software or services mentioned and have no affiliation with their creators. The user is solely responsible for how they use the information provided.

What Exactly *Is* Windows Telemetry in 2026?

Windows telemetry is the automated process where your operating system collects and sends usage and diagnostic data back to Microsoft’s servers. The main goal is to improve the stability, security, and compatibility of the Windows ecosystem. Thanks to this data, Microsoft can push out more effective security patches, fix application crashes, and ensure driver updates don’t cause system-wide chaos.

In my experience, telemetry primarily monitors events like:

• Critical System Errors: The infamous Blue Screen of Death (BSOD), application freezes, and service failures.
• Hardware Configuration: CPU model, RAM amount, BIOS/UEFI version, and connected peripherals.
• System Performance: Boot times, CPU and disk usage, and application responsiveness.
• Feature and Software Usage: Which Windows features and applications you use most often, which is key for developing future versions like the rumored Windows 12.

This data is sent anonymously or pseudonymously, but the level of detail depends entirely on your settings. While it’s useful for the overall health of the OS, it’s completely legitimate to want to limit the collection of optional data to protect your privacy.

Understanding Windows 11’s Telemetry Levels

Windows categorizes data collection into several levels. Understanding them is key to knowing what you’re disabling. For home users with Windows 11 Home or Pro, the choice boils down to two main tiers:

Level 1 – Required (Formerly “Basic”)

• Can you disable it? Not on Home/Pro editions. This is the bare minimum.
• What it collects: Basic device info (Windows version, hardware type), quality data (critical crash reports), and compatibility information.
• Why it’s necessary: This level ensures your PC gets security updates, critical patches, and compatible drivers. Disabling it would compromise your system’s security and stability. Our guide will not touch this level.

Level 3 – Optional (Formerly “Full”)

• Can you disable it? Yes, and this is the main goal of this guide.
• What it collects: Everything from the Required level, plus:
  • Detailed data on how you use apps and features.
  • Browsing history from Microsoft Edge.
  • Inking and typing data to improve Cortana and other AI tools.
  • Advanced error reports, including memory dumps that can contain fragments of the files you had open during a crash.
  • A complete inventory of installed software and drivers.
• Why disable it: This is the level that raises the most privacy flags. It sends a massive amount of data about your usage habits that, while helpful to Microsoft, isn’t necessary for the daily, secure operation of your PC.

The Bottom Line: Our goal is to completely disable the Optional (Level 3) telemetry, leaving only the Required (Level 1) data collection to keep the system secure and up-to-date.

The 2026 Guide: 4 Proven Methods to Disable Telemetry

I’m laying out four ways to take back control, ordered from simplest to most comprehensive. You can use just one or combine several for a more robust block.

Method 1: The Quick Fix (via Windows 11 Settings)

This is the easiest and most accessible method for any user, as you can do it right from the Windows Settings interface.

1. Open Settings (you can use the Win + I shortcut).
2. Navigate to Privacy & security in the left-hand menu.
3. Click on Diagnostics & feedback.
4. Toggle off the switch for Send optional diagnostic data. This will limit telemetry to the Required level.
5. (Optional but recommended) On the same screen, expand the Tailored experiences section and turn that switch off too. This stops Microsoft from using your diagnostic data to serve you personalized ads and recommendations.

[Screenshot: “Diagnostics & feedback” window in Windows 11 showing the optional data switch turned off.]

Method 2: For Pro Editions (Using Group Policy Editor)

If you have Windows 11 Pro, Education, or Enterprise, the Group Policy Editor (`gpedit.msc`) gives you more granular and persistent control.

1. Press Win + R, type gpedit.msc, and hit Enter.
2. Navigate down the left-hand tree to the following path:

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

3. In the right pane, find and double-click the Allow Telemetry policy.
4. Select Enabled.
5. Under the “Options” dropdown menu, choose 0 – Security [Enterprise Only]. Even though it says “Enterprise Only,” in my testing, this option forces the lowest possible level on Pro editions too. If you prefer to be more conservative, choose 1 – Required.
6. Click Apply, then OK. Reboot your computer for the changes to take full effect.

[Screenshot: Group Policy Editor showing the “Allow Telemetry” policy set to “0 – Security”.]

Method 3: For All Editions (Using the Registry Editor)

This method accomplishes the same goal as the one above but is for Windows 11 Home users who don’t have `gpedit.msc`. It requires modifying the registry, so proceed with caution.

Warning: Editing the registry incorrectly can cause system instability. Before you proceed, it’s highly recommended to create a system restore point or back up your registry.

1. Press Win + R, type regedit, and hit Enter.
2. Navigate to the following key in the left pane:

   HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection

   (If the `DataCollection` key doesn’t exist, you’ll need to create it by right-clicking on `Windows` > New > Key).

3. With the `DataCollection` key selected, right-click in the right-hand pane and select New > DWORD (32-bit) Value.
4. Name the new value AllowTelemetry.
5. Double-click on AllowTelemetry and ensure its Value data is set to 0.
6. Click OK and restart your PC.

Just like with the Group Policy Editor, this modification is a robust way to force the minimum telemetry level.

Method 4: The Nuclear Option (The PowerShell Script)

This is the most thorough method. It doesn’t just tweak the telemetry level via the registry; it also disables the underlying telemetry services and related scheduled tasks. This is for power users who want a deep clean.

Copy the following code into a text editor (like Notepad or VS Code) and save it as Disable-Telemetry-2026.ps1 in an easy-to-find folder, like C:\Scripts.

<#  ─────────────────────────────────────────────────────────────
    Disable-Telemetry-2026.ps1
    The Ultimate Windows 11 Guide - Updated for 2026
    Always run PowerShell as an **Administrator**.

      Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process
      .\Disable-Telemetry-2026.ps1
    ───────────────────────────────────────────────────────────── #>

Write-Host "--- Starting telemetry disabling script (2026 version) ---" -ForegroundColor Cyan

# 1. Disable telemetry services
$services = @(
    'DiagTrack',                                        # Connected User Experiences & Telemetry
    'dmwappushservice',                                 # Device Management WAP Push
    'CDPSvc',                                           # Connected Devices Platform Service
    'diagnosticshub.standardcollector.service'          # Diagnostics Hub Standard Collector
)

foreach ($s in $services) {
    Write-Host "➜ Disabling service: $s..."
    Stop-Service $s -Force -ErrorAction SilentlyContinue
    Set-Service  $s -StartupType Disabled -ErrorAction SilentlyContinue
}

# 2. Disable data collection scheduled tasks
$tasks = @(
    '\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser',
    '\Microsoft\Windows\Application Experience\ProgramDataUpdater',
    '\Microsoft\Windows\Customer Experience Improvement Program\Consolidator',
    '\Microsoft\Windows\Customer Experience Improvement Program\UsbCeip',
    '\Microsoft\Windows\DiskDiagnostic\Microsoft-Windows-DiskDiagnosticDataCollector'
)

foreach ($t in $tasks) {
    Write-Host "➜ Disabling scheduled task: $t..."
    schtasks /Change /TN $t /Disable 2>$null
}

# 3. Apply registry keys for a robust block
Write-Host '➜ Applying Windows Registry tweaks...'
$regs = @(
    @{Path='HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection';     Name='AllowTelemetry';                 Value=0; Type='DWord'},
    @{Path='HKLM:\SOFTWARE\Policies\Microsoft\Windows\CloudContent';       Name='DisableWindowsConsumerFeatures'; Value=1; Type='DWord'},
    @{Path='HKLM:\SOFTWARE\Policies\Microsoft\SQMClient\Windows';          Name='CEIPEnable';                     Value=0; Type='DWord'},
    @{Path='HKCU:\Software\Policies\Microsoft\Windows\WindowsCopilot';     Name='TurnOffWindowsCopilot';          Value=1; Type='DWord'},
    @{Path='HKLM:\SOFTWARE\Policies\Microsoft\Windows\System';             Name='DisableAdvertisingId';           Value=1; Type='DWord'}
)

foreach ($r in $regs) {
    if (-not (Test-Path $r.Path)) { New-Item -Path $r.Path -Force | Out-Null }
    New-ItemProperty -Path $r.Path -Name $r.Name -Value $r.Value -PropertyType $r.Type -Force | Out-Null
}

Write-Host "`n✅ Process complete. Please restart your computer to apply all changes." -ForegroundColor Green

How to Run the Script

1. Search for “PowerShell” in the Start Menu, right-click it, and select “Run as administrator”.
2. Allow script execution for this session with the following command:

   Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned -Force

3. Navigate to the folder where you saved the script:

   cd C:\Scripts

4. Execute the script:

   .\Disable-Telemetry-2026.ps1

5. Restart your PC to finalize the process.

Comparison: Which Method Is Best for You?

To help you decide, here’s a quick breakdown of the pros and cons of each approach.

How to Revert The Changes (Reversal Script)

If you ever need to re-enable optional telemetry (for example, to let Microsoft support diagnose a complex bug), you can use this script to undo all the changes made by Method 4.

Save it as Revert-Telemetry-2026.ps1 in the same C:\Scripts folder.

<# ─────────────────────────────────────────────────────────────
   Revert-Telemetry-2026.ps1
   Restores optional telemetry to its default settings.
   Always run PowerShell as an **Administrator**.
───────────────────────────────────────────────────────────── #>

Write-Host "--- Starting telemetry restoration script (2026 version) ---" -ForegroundColor Yellow

# 1. Re-enable services
$services = @('DiagTrack', 'dmwappushservice', 'CDPSvc', 'diagnosticshub.standardcollector.service')
foreach ($s in $services) {
    Write-Host "➜ Re-enabling service: $s..."
    Set-Service -Name $s -StartupType Automatic -ErrorAction SilentlyContinue
    Start-Service -Name $s -ErrorAction SilentlyContinue
}

# 2. Re-enable scheduled tasks
$tasks = @(
    '\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser',
    '\Microsoft\Windows\Application Experience\ProgramDataUpdater',
    '\Microsoft\Windows\Customer Experience Improvement Program\Consolidator',
    '\Microsoft\Windows\Customer Experience Improvement Program\UsbCeip',
    '\Microsoft\Windows\DiskDiagnostic\Microsoft-Windows-DiskDiagnosticDataCollector'
)
foreach ($t in $tasks) {
    Write-Host "➜ Re-enabling task: $t..."
    schtasks /Change /TN $t /Enable 2>$null
}

# 3. Remove registry block policies
Write-Host '➜ Removing registry lockdown policies...'
$registryEntries = @(
    @{ Path = 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection';   Name = 'AllowTelemetry' },
    @{ Path = 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\CloudContent';     Name = 'DisableWindowsConsumerFeatures' },
    @{ Path = 'HKLM:\SOFTWARE\Policies\Microsoft\SQMClient\Windows';        Name = 'CEIPEnable' },
    @{ Path = 'HKCU:\Software\Policies\Microsoft\Windows\WindowsCopilot';   Name = 'TurnOffWindowsCopilot' },
    @{ Path = 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\System';           Name = 'DisableAdvertisingId' }
)
foreach ($r in $registryEntries) {
    if (Test-Path $r.Path) {
        Remove-ItemProperty -Path $r.Path -Name $r.Name -ErrorAction SilentlyContinue
    }
}

Write-Host "`n✅ Reversal process complete. Please restart your computer." -ForegroundColor Green

To run it, follow the same steps as the disable script, but use the new filename: .\Revert-Telemetry-2026.ps1.

Frequently Asked Questions (FAQ) for 2026

Will Disabling Telemetry Break Windows Update or Microsoft Defender?

No. All the methods in this guide keep Level 1 (Required) telemetry active, which is essential for Windows Update to function correctly and for Defender to receive its signature updates. You’re only blocking the optional data collection, which doesn’t affect critical security and update functions.

What’s the Real Difference Between Group Policy and Registry Editor?

Functionally, for this specific task, they achieve the same result: setting a system-level policy that overrides the user’s settings. The key difference is that the Group Policy Editor (`gpedit.msc`) is only available in Pro, Enterprise, or Education editions of Windows, while the Registry Editor (`regedit`) is available on all versions, including Home.

If I Use the Settings App, Do I Still Need the PowerShell Script?

It’s not strictly necessary, but it’s highly recommended if you’re aiming for maximum privacy. The Settings app method only adjusts the telemetry level; it doesn’t disable the underlying services that are still running in the background. The PowerShell script stops and disables these telemetry services, further reducing background activity and data collection.

Will This Affect My Windows License or the Microsoft Store?

Not at all. Telemetry is a diagnostic service and is not tied to your Windows license activation or the functionality of the Microsoft Store. You can continue to install and update apps without any issues.

Why Use a Script Instead of Tools like O&O ShutUp10++?

Third-party tools are convenient, but a PowerShell script offers three key advantages: transparency (you can read every line of code and know exactly what it’s doing), lightweight (it doesn’t install any extra software), and control (you can easily customize it). It’s a clean solution that uses the operating system’s own native tools.

Conclusion

Controlling your data in Windows 11 is more manageable than ever in 2026. Whether you prefer the simplicity of the Settings app, the power of Group Policy, or the thoroughness of a PowerShell script, you now have all the tools you need to decide what you share with Microsoft.

In my experience, combining the native Settings toggle with the PowerShell script offers the perfect balance of privacy, performance, and security. By following this guide, you’ll not only safeguard your data but also help your system run a little leaner and more efficiently.

Pro-Tip: Remember to re-check these settings after major annual Windows feature updates, as Microsoft has been known to reset some of them to their default values.