{"version":"2.1.260","anchor":"essentialnonessential-telemetry-policy-settings-now-apply-u","canonical_anchor":"essentialnonessential-telemetry-policy-settings-now-apply-u","heading":"Essential\/nonessential telemetry policy settings now apply unverified and fail closed","tier":"notice","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/essentialnonessential-telemetry-policy-settings-now-apply-u","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Essential\/nonessential telemetry policy settings now apply unverified and fail closed\n\nTelemetry-disable settings now apply before verification completes and fail closed.\n\nThe `disableEssentialTelemetry` and `disableNonessentialTelemetry` managed settings now carry `remotePolicy.applyUnverified: true` and `failClosedValue: true`, so they are honored even before signature verification completes and default to the blocking (`true`) value if verification fails.\n\n- Area: Telemetry\n- Names: `disableEssentialTelemetry`, `disableNonessentialTelemetry`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}