Telemetry.md

Easy Telemetry Disable for 10/11

Prerequisites

1. Upgrade to Enterprise edition of Windows 10/11 if you are running Home or Pro.
   • You can do this through the Change Edition option in the Extras menu in MAS.

Disabling Telemetry via Group Policy

1. Open the Group Policy Editor. Search for "Edit Group Policy" in search or run gpedit.msc.

2. In the Group Policy Editor, navigate to the following path: Computer Configuration -> Administrative Templates -> Windows Components -> Data Collection and Preview Builds

3. Double-click on Allow Telemetry (Windows 10) or Allow Diagnostic Data (Windows 11) in the right pane.

4. In the properties window, select Enabled. Then select Security [Enterprise Only] (Win10) or Diagnostic data off (Win11), which disables all telemetry.

5. Select OK. Telemetry should now be disabled.

Optional: Disable Windows Error Reporting

While disabling telemetry should be enough to prevent diagnostic data from being sent to Microsoft, to be extra safe you can also explicitly disable Windows Error Reporting:

1. In the Group Policy Editor, navigate to: Computer Configuration -> Administrative Templates -> Windows Components -> Windows Error Reporting

2. Double-click on Disable Windows Error Reporting in the right pane.

3. Select Enabled and click OK.

Verify the Changes

To verify that the changes have been applied, you can check the registry.

1. Open regedit.
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection.
3. On the right side, you should see AllowTelemetry with a value of 0. This means that telemetry has been disabled.
4. For Error Reporting, check HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Error Reporting. The Disabled value should be set to 1.

thx

Thank you

THX

thanks for this

Thank you

Hey, I did everything mentioned here but when I go to regedit to confirm the changes there is no dword called AllowTelemetry in DataCollection but there is a dword for windows error reporting which shows that it worked properly, what am I doing wrong?

try running gpupdate.exe /force and see if that helps

nope, same result

idk then, works on my machine. are you using a working edition?

I actually managed to fix it by rebooting and following the guide again, I have no clue what was wrong but it's fixed now.
thanks for the guide btw very cool

Did you check the registry keys after rebooting but before following the guide again? It's possible the keys were set during reboot.

My 0.02:
I followed the guide and checked the reg keys right after (no reboot). Keys were present for me. ¯\_(ツ)_/¯