{"version":"2.1.239","anchor":"powershell-path-checks-distinguish-a-timeout-from-an-error","canonical_anchor":"powershell-path-checks-distinguish-a-timeout-from-an-error","heading":"PowerShell path checks distinguish a timeout from an error","tier":"notice","area":"Windows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/powershell-path-checks-distinguish-a-timeout-from-an-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### PowerShell path checks distinguish a timeout from an error\n\nOn Windows, a PowerShell path check that times out now says so with the timeout value.\n\n**What**\n\nOn Windows, when Claude Code checks the PowerShell interpreter path for policy purposes, a check that times out now reports \"cannot stat path (timed out after ...\" with the timeout value, rather than looking like an ordinary failure.\n\n**Details**\n\n- The result of checking each path is cached in a shared map, so repeated checks of the same path do not re-run the stat.\n- Windows-only code path.\n\n**Evidence**\n\n`cannot stat path (timed out after`\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}