How to Completely Disable ‘App Diagnostics’ via Group Policy in Windows 11

App Diagnostics is a privacy setting in Windows 11 that allows applications to access diagnostic information about other running applications. This data can include the names of running processes, user account information associated with those processes, and potentially metrics regarding app usage. While designed for specialized debugging tools or complex interwoven software suites, allowing standard applications to freely poll the system for this telemetry is a significant privacy concern. In an enterprise environment, a compromised or overly aggressive application utilizing App Diagnostics could silently map out the security software (like EDR agents) or proprietary internal tools currently running in a user’s session.

This guide explains how to completely disable App Diagnostics system-wide using the Group Policy Editor in Windows 11, ensuring applications remain strictly isolated from one another’s telemetry.

Disable App Diagnostics via Group Policy

To enforce a strict block that prevents any application from accessing diagnostic data about other apps, and to lock the setting so users cannot override it, we must deploy an administrative template. Note that this requires Windows 11 Pro, Enterprise, or Education editions.

  1. Log into Windows 11 with an Administrator account.
  2. Press the Windows Key + R to open the Run dialogue box.
  3. Type gpedit.msc and press Enter to launch the Local Group Policy Editor.
  4. In the left-hand navigation pane, strictly follow this exact path:
    Computer Configuration > Administrative Templates > Windows Components > App Privacy
  5. In the right-hand pane, locate the policy named Let Windows apps access app diagnostics.
  6. Double-click the policy to open its configuration window.
  7. Select the radio button next to Enabled. (Note: You must enable the policy to configure the restriction).
  8. In the Options pane below, click the “Default for all apps” drop-down menu and explicitly select Force Deny.
  9. Click Apply, then click OK.

Verify the Privacy Lockdown

To enforce the change immediately across the system, open an elevated Command Prompt and execute gpupdate /force.

To verify the restriction is active, open the Windows 11 Settings app (Win + I) and navigate to Privacy & security > App diagnostics. You will observe that the master toggle switch for “Let apps access your app’s diagnostic info” is completely greyed out and locked in the ‘Off’ position. A small message indicating that “Some of these settings are managed by your organization” will be visible. You have successfully enforced strict inter-process privacy on the endpoint.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.