Telemetry in Windows sends diagnostic and usage data to Microsoft to improve reliability, driver compatibility, and update quality. Reducing telemetry tightens privacy controls, helps meet organizational compliance requirements, and makes outbound diagnostics traffic easier to document and audit.

Diagnostic data collection is controlled by Diagnostics & feedback settings and can be enforced via policy on supported editions. Policy-based configuration writes telemetry level settings under the /Policies/ branch and can override the Settings UI when a device is managed locally, by domain policy, or by MDM.

Telemetry cannot be fully disabled on most consumer editions, and some diagnostic traffic remains required for security and servicing. Settings may appear locked with “managed by your organization” messaging when a policy is applied, and incorrect Registry edits can cause system instability.

Method 1: Using Windows Settings:

The Settings app controls optional diagnostic data, tailored experiences, and feedback prompts on Windows 11, and it is the safest way to reduce telemetry on unmanaged devices.

  1. Open Settings.

    Win+I opens Settings directly.

  2. Select Privacy & security.
  3. Open Diagnostics & feedback.
  4. Turn off Send optional diagnostic data.

    Required diagnostic data cannot be disabled on most editions.

  5. Turn off Improve inking & typing.
  6. Turn off Tailored experiences.
  7. Set Feedback frequency to Never.
  8. Select Delete diagnostic data.

    This clears locally stored diagnostic data associated with the device.

  9. Confirm Optional diagnostic data and Tailored experiences are disabled.

Method 2: Using Group Policy Editor:

The Local Group Policy Editor is available on Windows Pro, Enterprise, and Education editions and can enforce the lowest telemetry level supported by the installed edition.

  1. Open the Run dialog with Win+R.
  2. Enter gpedit.msc and select OK.
  3. Browse to Computer ConfigurationAdministrative TemplatesWindows ComponentsData Collection and Preview Builds.
  4. Open the Allow Telemetry policy.
  5. Select Enabled.
  6. Set Telemetry to the lowest available value.

    0 - Security is typically honored only on Enterprise and Education.

  7. Select Apply.
  8. Refresh policy from an elevated Command Prompt.
    C:\> gpupdate /force
    Updating policy...
    Computer Policy update has completed successfully.
    User Policy update has completed successfully.

  9. Confirm the applied value in the policy registry key.
    C:\> reg query HKLM\SOFTWARE\Policies\Microsoft\Windows\DataCollection /v AllowTelemetry
    
    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection
        AllowTelemetry    REG_DWORD    0x1

Method 3: Using Windows Registry:

Editing the policy registry key applies the same telemetry level control used by Group Policy and is useful when the Local Group Policy Editor is unavailable.

  1. Open the Run dialog with Win+R.
  2. Enter regedit and select OK.
  3. Select Yes on the User Account Control prompt.

    Incorrect changes in the Registry can break applications or prevent normal startup.

  4. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection.
  5. Create the DataCollection key if missing.
  6. Create a new DWORD (32-bit) value named AllowTelemetry.
  7. Set AllowTelemetry to the minimum value supported by the installed edition.

    1 is commonly the minimum honored on Home and Pro, while 0 is reserved for Enterprise and Education.

  8. Restart Windows.
  9. Confirm the value after restart.
    C:\> reg query HKLM\SOFTWARE\Policies\Microsoft\Windows\DataCollection /v AllowTelemetry
    
    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection
        AllowTelemetry    REG_DWORD    0x1