Disable Windows 11 Telemetry: The Ultimate 2026 Guide

Albert BarnosellEditor and publisher of Tecnoyfoto

“`html

Updated September 25, 2026

If you landed here looking for how to disable Windows 11 telemetry, there is something important to clarify right from the start: on consumer editions of Windows, we cannot completely disable all data collection using the normal methods officially supported by Microsoft.

What we can do is turn off optional diagnostic data, reduce the amount of information Windows sends, prevent that data from being used for personalized recommendations and ads, and control several other privacy-related settings.

That is the goal of this guide: improve privacy without blindly disabling Windows services, without breaking features, and without promising results we cannot actually achieve.

Important: the video above was made for an older version of this guide. Windows has changed over time, so if there is any difference between the video and this article, consider the updated written information below to be the current version.

What We Are Actually Going to Do

Turn off optional diagnostic data.
Keep only required diagnostic data on Windows 11 Home and Pro.
Prevent diagnostic data from being used for personalized recommendations and offers.
Review handwriting and typing data collection.
Disable the Windows advertising ID if we do not need it.
See what diagnostic data our PC is actually collecting.
Delete diagnostic data stored for the device if we want to.
Apply the same settings using Group Policy, Registry Editor, or PowerShell on supported Windows editions.

This guide is mainly intended for Windows 11. Windows 10 Home and Pro reached the end of general support on October 14, 2025. If you are still using Windows 10, many of these settings may still exist, but keeping your operating system supported should take priority over any privacy optimization.

What Is Windows Telemetry?

Windows automatically collects certain diagnostic information about your device and how the operating system is working. Microsoft uses this data, among other things, to help keep Windows updated, check compatibility, detect errors, and analyze stability and performance problems.

The term telemetry is commonly used to describe this communication, although Microsoft now generally refers to it as diagnostic data.

On a normal computer, this information may include data related to:

The device: hardware characteristics, Windows version, configuration, and connected peripherals.
Compatibility: installed applications and drivers and potential issues during an update.
Errors: Windows crashes, applications that stop responding, or failures during updates.
Performance: certain information about how the device and applications are performing.
Feature usage: the optional level may collect additional information about how applications and Windows features are used.
Advanced error reports: optional diagnostic data may include additional information and memory dumps associated with certain failures.

So the point is not to claim that all of this collection is necessarily bad. The real question is how much information we want to share.

Required vs. Optional Diagnostic Data: The Difference That Matters

In current versions of Windows, the classification that really matters to a home user is much simpler than it used to be.

Required Diagnostic Data

This is the minimum data Windows uses to help keep the operating system secure, updated, and working properly.

It is enabled on Windows 11 Home and Pro.
It cannot be completely disabled using the normal options available on these editions.
It includes information about the device, configuration, compatibility, updates, and certain errors.

Optional Diagnostic Data

This is additional information that we can choose whether or not to send.

Additional information about application and feature usage.
Additional data about device health and performance.
Enhanced error reports.
Certain memory dumps related to crashes.
Other additional information used to diagnose problems and improve Windows.

For most Tecnoyfoto readers, my recommendation is simple: keep required diagnostic data enabled and turn optional diagnostic data off.

What About Microsoft Edge Browsing Data?

This is one of the points that has changed compared with older versions of this guide.

In the European Economic Area, since March 6, 2024, Microsoft Edge diagnostic data has been managed separately from Windows diagnostic data on Windows 11 23H2 and later.

That means turning off optional Windows diagnostic data does not necessarily change Microsoft Edge privacy settings. The browser has its own privacy controls, and they should be reviewed separately if you use Microsoft Edge.

Method 1: Windows 11 Settings — What I Recommend for Almost Everyone

For a home PC, this is the easiest, safest, and in most cases sufficient option.

Press Win + I to open Settings.
Go to Privacy & security.
Select Diagnostics & feedback.
Find Send optional diagnostic data.
Turn this option off.

Windows will continue sending required diagnostic data, but it will stop using the optional diagnostic level.

You do not need to disable Windows services to achieve this result.

Turn Off Improve Inking & Typing as Well

Inside Diagnostics & feedback, you may see an option called:

Improve inking & typing

If you would rather Microsoft not use handwriting or typing samples to improve recognition systems and suggestions, you can turn it off.

Turn Off Personalized Offers

Microsoft has changed the name and location of this setting in different Windows releases.

In recent versions, you may find a section called Personalized offers, Recommendations and offers, or, on slightly older versions, Tailored experiences.

Look under:

Settings → Privacy & security

and turn off the option that allows Windows activity and diagnostic data to be used for personalized suggestions, ads, or recommendations.

Turn Off the Advertising ID

Another setting that is separate from telemetry is the Windows advertising ID.

Depending on your Windows version, you may find it under:

Settings → Privacy & security → General

or inside the newer Recommendations and offers section.

If you do not want applications to use the Windows advertising ID to personalize ads, you can turn it off.

This does not remove ads. It simply prevents this specific identifier from being used to personalize them.

Review Suggested Content Too

In the same privacy area, you may also find settings related to:

suggested content inside Settings;
app launch tracking used to improve Start and search results;
website access to your language list;
Windows recommendations and offers.

Not all of these settings are telemetry, but they are part of the broader set of options worth reviewing if we want a less personalized Windows experience based on our activity.

See What Diagnostic Data Windows Is Collecting

One especially useful option is the Diagnostic Data Viewer.

In Windows 11, go to:

Settings → Privacy & security → Diagnostics & feedback

Temporarily enable View diagnostic data and open the viewer.

This tool lets you inspect the diagnostic information your PC is actually generating while the viewer is active, instead of relying entirely on assumptions.

Delete Diagnostic Data From the Device

On the same page, you will find the Delete diagnostic data option.

You can use it to request deletion of diagnostic data associated with the device.

Keep in mind that:

deleting this data does not turn off future data collection;
it does not replace turning off optional diagnostic data;
data linked to your Microsoft account may require separate management.

Method 2: Group Policy on Windows 11 Pro, Enterprise, and Education

If you use Windows 11 Pro, Enterprise, or Education, you can set the diagnostic level through the Group Policy Editor.

On a home computer running Windows Pro, I do not recommend trying to use the old value 0 to completely disable diagnostics. On these editions, the goal should be to configure Windows to use required diagnostic data only.

Press Win + R.
Type gpedit.msc and press Enter.
Navigate to:

Computer Configuration
→ Administrative Templates
→ Windows Components
→ Data Collection and Preview Builds
→ Allow Diagnostic Data

Open Allow Diagnostic Data.
Select Enabled.
Configure the policy to send only required diagnostic data.
Apply the changes.
Restart Windows or update Group Policy.

Important: if you find guides recommending 0 - Security on Windows Pro to “disable all telemetry,” keep in mind that Microsoft officially reserves the diagnostic data off setting for certain Enterprise, Education, and Server editions. On Pro, the minimum supported level corresponds to required diagnostic data.

Prevent Tailored Experiences Through Group Policy

You can also configure:

User Configuration
→ Administrative Templates
→ Windows Components
→ Cloud Content
→ Do not use diagnostic data for tailored experiences

Enabling this policy prevents Windows from using diagnostic data to customize certain recommendations and experiences.

Method 3: Registry Editor

The Windows Registry lets you configure the same policies directly.

Warning: this method is intended for advanced users. If you use Windows Home, my recommendation is to use Method 1 through Settings instead of copying policies intended for other editions and expecting behavior that Microsoft does not officially guarantee.

Before modifying the Registry, create a restore point or back up the values you are going to change.

Limit Diagnostic Data to Required Only

Open regedit and navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection

Create or edit the 32-bit DWORD value:

AllowTelemetry

and set it to:

On supported editions, this value configures required diagnostic data.

Disable Diagnostic Data for Tailored Experiences

Go to:

HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Windows\CloudContent

Create a DWORD named:

DisableTailoredExperiencesWithDiagnosticData

with the value:

Disable the Advertising ID Through Policy

The current policy path is:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\AdvertisingInfo

Create the DWORD:

DisabledByGroupPolicy

with the value:

Disable Data Collection Used to Improve Typing and Input

Go to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\TextInput

Create the DWORD:

AllowLinguisticDataCollection

and set it to:

After applying policies through the Registry, restart Windows to make sure all changes are loaded correctly.

Method 4: PowerShell — Automate the Same Settings Without Disabling Services

This is the biggest change compared with older versions of this guide.

I no longer recommend disabling services such as Connected Devices Platform, device management services, or scheduled tasks simply because they appear in old “telemetry” lists.

Some of these components perform other functions, and disabling them can break Windows features without giving us any meaningful privacy benefit.

The following script takes a much simpler and more transparent approach:

sets diagnostic data to Required;
disables the use of diagnostic data for tailored experiences;
disables the advertising ID through policy;
disables data collection used to improve typing;
does not disable any Windows services;
does not disable any scheduled tasks;
backs up the previous values before changing them.

It is intended for Windows 11 Pro, Enterprise, and Education. If it detects a Home edition, the script will stop automatically.

Save it as:

Tecnoyfoto-Windows-Privacy-2026.ps1

<#
    Tecnoyfoto-Windows-Privacy-2026.ps1

    Applies documented Windows privacy policies.
    Does not disable services.
    Does not disable scheduled tasks.
    Creates a backup of previous values.

    Run as Administrator.
#>

Write-Host ""
Write-Host "=== Tecnoyfoto - Windows Privacy Settings 2026 ===" -ForegroundColor Cyan
Write-Host ""

# ------------------------------------------------------------
# 1. Check administrator privileges
# ------------------------------------------------------------

$identity = [Security.Principal.WindowsIdentity]::GetCurrent()
$principal = New-Object Security.Principal.WindowsPrincipal($identity)

if (-not $principal.IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)) {
    Write-Host "ERROR: You must run PowerShell as Administrator." -ForegroundColor Red
    exit 1
}

# ------------------------------------------------------------
# 2. Detect Windows edition
# ------------------------------------------------------------

$windowsInfo = Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion'
$editionId = $windowsInfo.EditionID
$productName = $windowsInfo.ProductName

Write-Host "Detected system: $productName"
Write-Host "Edition: $editionId"
Write-Host ""

# Home editions usually use EditionID Core, CoreN,
# CoreSingleLanguage, etc.

if ($editionId -like 'Core*') {
    Write-Warning "Windows Home has been detected."
    Write-Warning "Microsoft does not officially support these policies in the same way as Pro/Enterprise/Education."
    Write-Warning "Use Settings > Privacy & security > Diagnostics & feedback instead."
    exit 1
}

# ------------------------------------------------------------
# 3. Define settings to modify
# ------------------------------------------------------------

$settings = @(

    [pscustomobject]@{
        Path  = 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection'
        Name  = 'AllowTelemetry'
        Value = 1
    },

    [pscustomobject]@{
        Path  = 'HKCU:\SOFTWARE\Policies\Microsoft\Windows\CloudContent'
        Name  = 'DisableTailoredExperiencesWithDiagnosticData'
        Value = 1
    },

    [pscustomobject]@{
        Path  = 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\AdvertisingInfo'
        Name  = 'DisabledByGroupPolicy'
        Value = 1
    },

    [pscustomobject]@{
        Path  = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\TextInput'
        Name  = 'AllowLinguisticDataCollection'
        Value = 0
    }
)

# ------------------------------------------------------------
# 4. Create backup
# ------------------------------------------------------------

$backupDir = Join-Path $env:ProgramData 'Tecnoyfoto\WindowsPrivacyBackup'

if (-not (Test-Path $backupDir)) {
    New-Item -Path $backupDir -ItemType Directory -Force | Out-Null
}

$timestamp = Get-Date -Format 'yyyyMMdd-HHmmss'
$backupFile = Join-Path $backupDir "WindowsPrivacy-$timestamp.json"

$backup = foreach ($setting in $settings) {

    $existed = $false
    $currentValue = $null

    if (Test-Path $setting.Path) {
        try {
            $property = Get-ItemProperty `
                -Path $setting.Path `
                -Name $setting.Name `
                -ErrorAction Stop

            $currentValue = $property.($setting.Name)
            $existed = $true
        }
        catch {
            $existed = $false
        }
    }

    [pscustomobject]@{
        Path    = $setting.Path
        Name    = $setting.Name
        Existed = $existed
        Value   = $currentValue
    }
}

$backup |
    ConvertTo-Json -Depth 4 |
    Set-Content -Path $backupFile -Encoding UTF8

Write-Host "Backup created:" -ForegroundColor Green
Write-Host $backupFile
Write-Host ""

# ------------------------------------------------------------
# 5. Apply settings
# ------------------------------------------------------------

foreach ($setting in $settings) {

    if (-not (Test-Path $setting.Path)) {
        New-Item -Path $setting.Path -Force | Out-Null
    }

    New-ItemProperty `
        -Path $setting.Path `
        -Name $setting.Name `
        -Value $setting.Value `
        -PropertyType DWord `
        -Force | Out-Null

    Write-Host "Applied: $($setting.Name) = $($setting.Value)" -ForegroundColor Green
}

# ------------------------------------------------------------
# 6. Update Group Policy
# ------------------------------------------------------------

Write-Host ""
Write-Host "Updating Windows policies..."

gpupdate /force | Out-Null

Write-Host ""
Write-Host "Process completed." -ForegroundColor Green
Write-Host ""
Write-Host "Only documented privacy policies have been applied."
Write-Host "No services or scheduled tasks have been disabled."
Write-Host ""
Write-Host "Restart Windows to make sure all changes are applied."
Write-Host ""

How to Run the Script

Save the file as Tecnoyfoto-Windows-Privacy-2026.ps1.
Search for PowerShell from the Start menu.
Select Run as administrator.
To temporarily allow script execution for that session, run:

Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned -Force

Then navigate to the folder where you saved the file. For example:

cd C:\Scripts

And run it:

.\Tecnoyfoto-Windows-Privacy-2026.ps1

When it finishes, restart Windows.

Script to Restore the Exact Previous Values

The previous script saves the current state of each policy before making any changes.

This allows for a much cleaner restoration than simply forcing every value back to what we assume is the default.

Save the following script as:

Tecnoyfoto-Restore-Windows-Privacy-2026.ps1

<#
    Tecnoyfoto-Restore-Windows-Privacy-2026.ps1

    Restores the most recent backup created by
    Tecnoyfoto-Windows-Privacy-2026.ps1.

    Run as Administrator.
#>

Write-Host ""
Write-Host "=== Tecnoyfoto - Restore Windows Privacy Settings ===" -ForegroundColor Yellow
Write-Host ""

# ------------------------------------------------------------
# 1. Check administrator privileges
# ------------------------------------------------------------

$identity = [Security.Principal.WindowsIdentity]::GetCurrent()
$principal = New-Object Security.Principal.WindowsPrincipal($identity)

if (-not $principal.IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)) {
    Write-Host "ERROR: You must run PowerShell as Administrator." -ForegroundColor Red
    exit 1
}

# ------------------------------------------------------------
# 2. Locate the most recent backup
# ------------------------------------------------------------

$backupDir = Join-Path $env:ProgramData 'Tecnoyfoto\WindowsPrivacyBackup'

if (-not (Test-Path $backupDir)) {
    Write-Host "Backup folder not found." -ForegroundColor Red
    exit 1
}

$backupFile = Get-ChildItem `
    -Path $backupDir `
    -Filter 'WindowsPrivacy-*.json' |
    Sort-Object LastWriteTime -Descending |
    Select-Object -First 1

if (-not $backupFile) {
    Write-Host "No backup file was found." -ForegroundColor Red
    exit 1
}

Write-Host "Restoring backup:" -ForegroundColor Cyan
Write-Host $backupFile.FullName
Write-Host ""

$backup = Get-Content `
    -Path $backupFile.FullName `
    -Raw |
    ConvertFrom-Json

# ------------------------------------------------------------
# 3. Restore values
# ------------------------------------------------------------

foreach ($item in $backup) {

    if ($item.Existed) {

        if (-not (Test-Path $item.Path)) {
            New-Item -Path $item.Path -Force | Out-Null
        }

        New-ItemProperty `
            -Path $item.Path `
            -Name $item.Name `
            -Value ([int]$item.Value) `
            -PropertyType DWord `
            -Force | Out-Null

        Write-Host "Restored: $($item.Name) = $($item.Value)" -ForegroundColor Green
    }
    else {

        if (Test-Path $item.Path) {
            Remove-ItemProperty `
                -Path $item.Path `
                -Name $item.Name `
                -ErrorAction SilentlyContinue
        }

        Write-Host "Removed policy that did not exist before: $($item.Name)" -ForegroundColor Green
    }
}

# ------------------------------------------------------------
# 4. Update Group Policy
# ------------------------------------------------------------

Write-Host ""
Write-Host "Updating Windows policies..."

gpupdate /force | Out-Null

Write-Host ""
Write-Host "Restore completed." -ForegroundColor Green
Write-Host "Restart Windows to finish."
Write-Host ""

To run it, use the same process as with the previous script:

Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned -Force

cd C:\Scripts

.\Tecnoyfoto-Restore-Windows-Privacy-2026.ps1

Comparison of the Four Methods

Method	Difficulty	Windows Edition	What It Does	My Recommendation
Windows Settings	Very easy	Home / Pro / Enterprise / Education	Turns off optional diagnostic data and adjusts privacy settings	Recommended for almost everyone
Group Policy Editor	Intermediate	Pro / Enterprise / Education	Enforces settings through system policies	Very useful on Pro or managed devices
Registry Editor	Advanced	Mainly editions that support these policies	Applies the same policies manually	Only if you know exactly what you are changing
PowerShell	Intermediate-advanced	Pro / Enterprise / Education	Automates the same policies and creates a backup	Useful for repeatable or documented setups

Which Method Would I Use?

For a normal home computer, I would use Method 1.

I would turn off optional diagnostic data, review personalized offers and the advertising ID, and leave everything else alone unless I had a specific reason to change it.

If I were using Windows Pro and wanted to make sure the configuration remained enforced through system policies, then I would use Group Policy.

I would reserve Registry Editor and PowerShell for advanced users, administrators, or situations where we want to automate the process.

More aggressive does not necessarily mean better. Disabling services at random can remove Windows functionality without giving you a proportional privacy improvement.

Does Turning Off Optional Diagnostic Data Improve Performance?

I would not treat telemetry settings as a major Windows performance optimization.

Reducing unnecessary background activity and communications may have a small effect in some situations, but on a modern computer the main reason to make these changes should be privacy and control over your data, not the expectation of a dramatic speed boost.

If your computer feels slow, you will usually get much better results by reviewing startup programs, storage, RAM, temperatures, background processes, or the overall condition of the operating system.

Frequently Asked Questions

Can I Completely Disable Telemetry on Windows 11 Home or Pro?

Not through the normal supported mechanisms available on those editions.

What we can do is disable optional diagnostic data and keep only the required diagnostic data, which is exactly what I recommend in this guide.

Why Aren’t We Using AllowTelemetry = 0?

Because the value that disables diagnostic data is officially reserved for certain Enterprise, Education, and Server editions.

On a normal Windows Pro installation, setting 0 does not mean we have successfully eliminated all telemetry. That is why we use 1, which corresponds to the supported required diagnostic level.

Does Turning Off Optional Diagnostic Data Break Windows Update?

No. Windows can operate normally using required diagnostic data only.

Does It Affect Microsoft Defender?

Turning off optional diagnostic data does not disable Microsoft Defender or its security updates.

Do I Need to Run the PowerShell Script?

No.

The script does not provide some magical additional layer of privacy. It simply automates some of the same policies that can be configured manually.

Why Don’t We Disable DiagTrack, CDPSvc, and Other Services Anymore?

Because not every service that appears in older “debloat” or “telemetry” guides exists only to send diagnostic data.

Some of them are involved in communication between devices, management, diagnostics, or other Windows features.

I prefer to limit data collection using the specific policies designed for that purpose instead of disabling complete system components.

Does Deleting Diagnostic Data Stop Windows From Collecting More?

No.

The delete option removes the relevant diagnostic data associated with the device, but you must also change the diagnostic settings if you want to limit future collection.

What About Microsoft Edge?

In the European Economic Area, modern versions of Windows handle Microsoft Edge diagnostic data separately from Windows diagnostic data.

If you use Edge and want to improve your privacy, you should review the browser’s own privacy settings as well.

Conclusion: Less Telemetry Without Breaking Windows

Reducing the amount of data Windows shares still makes sense in 2026, but we do not need to turn it into a war against every service running on the operating system.

For most users, the configuration I consider the best balance is:

Required diagnostic data: enabled.
Optional diagnostic data: disabled.
Improve inking and typing: disabled if you do not want to share that data.
Personalized offers or tailored experiences: disabled.
Advertising ID: disabled.
Windows services and internal scheduled tasks: leave them alone unless you have a specific reason to change them.

This gives us more privacy and more control without blindly disabling features or applying modifications whose behavior may change in future Windows versions.

And above all, remember something important: privacy and security do not always mean disabling as many things as possible. The best configuration is one where we know exactly what we changed, why we changed it, and how to undo it if we ever need to.

If you have just installed Windows or want to review more system settings, you can also continue with our guide to getting started with Windows 11 and setting up your PC properly.

“`