Appearance

Policy Troubleshooting ​

Diagnose issues related to policy loading, authorization/visibility, and modifications.

Policy Not Loading ​

Problem

  • Policy changes are not taking effect or you see “Policy file is not configured.”

Solutions

  • Validate JSON syntax using a validator or jq.
  • Check file permissions and that the file is readable by the user.
  • Confirm the file path is correct:
    • System-wide: %PROGRAMDATA%\Turbo\Launcher\policy.json
    • User-specific: %LOCALAPPDATA%\Turbo\Launcher\policy.json
  • Use the Retry button or restart the Launcher after updates.
  • Review launcher logs for policy loading errors.

Policy Modifications Not Applied ​

Problem

  • Flags or arguments defined in policy are not taking effect.

Solutions

  • Ensure at least one enabled application policy with action: "allow" matches the executable (the deprecated “modify” action does not authorize).
  • Check precedence:
    • Profile > Policy > Global (a profile may override a policy or global flag/value).
    • arguments.replace overrides prepend/append.
  • Verify per‑app vs global placement of flags/arguments.
  • Confirm that unkeyed flags are not being de‑duplicated and keyed flags aren’t overridden later.

Visibility/Authorization Issues ​

Problem

  • An app is missing from the Applications tab or a hidden app appears unexpectedly.

Solutions

  • Verify the app has at least one matching policy with action: "allow".
  • Check visibility:
    • visible to show in Applications.
    • hidden to hide from Applications (still usable by file handlers).
  • Confirm the shortcut is in discovery scope (Start Menu, Desktop top‑level).
  • If multiple policies match, confirm priority/id tie‑breaks produce the expected effective result.

File Handlers Ignored ​

Problem

  • Centralized handlers or Open With entries do not appear.

Solutions

  • Ensure the referenced application is authorized:
    • There must be an enabled app policy with action: "allow" that matches the executable.
  • Verify the handler match aligns with the file (extension, patternType).
  • Check that rules and handlers are enabled, and defaults are set where intended.

Quick Checks ​

  • Use a visible flag (e.g., --skin-border-color) to confirm flags are applied.
  • Use arguments.append with a visible behavior (e.g., Chrome --incognito) to validate arguments.
  • Adjust priority values to verify tie‑break behavior.

See Also ​

Turbo.net © 2025