{"version":"2.1.229","anchor":"windows-guard-for-self-hosted-runner-hooks-is-present-but-ne","canonical_anchor":"windows-guard-for-self-hosted-runner-hooks-is-present-but-ne","heading":"Windows guard for self-hosted runner hooks is present but never fires","tier":"soon","area":"Self-Hosted Runner","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/windows-guard-for-self-hosted-runner-hooks-is-present-but-ne","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Windows guard for self-hosted runner hooks is present but never fires\n\nRunner hook errors saying hooks need Linux or macOS exist but can never trigger.\n\n**What**\n\nNew errors were added saying that lifecycle hooks and orchestrator mode need a Linux or macOS host, because hooks are POSIX executables spawned directly. In this build the check cannot trigger: both call sites pass only the feature name, and the platform argument defaults to `linux`, so the guard always returns without throwing.\n\n**Details**\n\n- One message reads `--hooks-dir is not supported on Windows`.\n- Whether it ever fires depends on a caller passing a real platform value, which nothing in this build does.\n\n**Evidence**\n\n`--hooks-dir is not supported on Windows`\n\n- Area: Self-Hosted Runner\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}