{"version":"2.1.229","anchor":"windows-guards-for-runner-hooks-that-may-not-be-reachable","canonical_anchor":"windows-guards-for-runner-hooks-that-may-not-be-reachable","heading":"Windows guards for runner hooks that may not be reachable","tier":"soon","area":"Self-Hosted Runner","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/windows-guards-for-runner-hooks-that-may-not-be-reachable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Windows guards for runner hooks that may not be reachable\n\nThe runner now has Windows errors for hooks and orchestrator mode, but they never fire.\n\n**What**\n\nThe self-hosted runner gained errors saying `--hooks-dir`, the matching `SELF_HOSTED_RUNNER_HOOKS_DIR` variable, and orchestrator mode are unsupported on Windows, because lifecycle hooks are POSIX executables spawned directly. Whether the guard can fire is unresolved in the code: the platform argument defaults to the literal \"linux\" and neither call site passes it.\n\n**Evidence**\n\n`--hooks-dir is not supported on Windows: lifecycle hooks currently require a Linux or macOS host`\n\n- Area: Self-Hosted Runner\n- Names: `--hooks-dir`, `SELF_HOSTED_RUNNER_HOOKS_DIR`\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}