{"version":"2.1.285","anchor":"powershell-hooks-abort-early-if-the-signal-is-aborted-proje","canonical_anchor":"powershell-hooks-abort-early-if-the-signal-is-aborted-proje","heading":"Cancelled PowerShell hooks no longer report a missing PowerShell","tier":"notice","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/powershell-hooks-abort-early-if-the-signal-is-aborted-proje","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Cancelled PowerShell hooks no longer report a missing PowerShell\n\nA PowerShell hook cancelled while Claude Code looks for PowerShell now ends as cancelled instead of a not-found error\n\n**Unclear.** What pinning project hooks does is not explained.\n\n**What**\n\nA hook is a command you set up to run automatically at certain points while Claude Code works. For hooks that run in PowerShell, Claude Code first has to find PowerShell on your computer. If the hook is cancelled during that search, it now ends as cancelled. Before, it carried on and reported that no PowerShell executable could be found.\n\nSeparately, a step that pins project hooks is now skipped when Claude Code could not read the Windows settings.\n\n**Why**\n\nOn Windows you should see fewer misleading errors, such as being told PowerShell is missing when the hook was simply cancelled.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}