{"version":"2.1.299","anchor":"windows-shell-snapshot-path-probe-reports-failures","canonical_anchor":"windows-shell-snapshot-path-probe-reports-failures","heading":"Windows shell snapshots handle a failed PATH lookup better","tier":"notice","area":"Windows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/windows-shell-snapshot-path-probe-reports-failures","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Windows shell snapshots handle a failed PATH lookup better\n\nOn Windows, if Claude Code cannot read your shell's PATH, it now warns and uses the current PATH instead of silently keeping a stale one\n\n**What**\n\nOn Windows, Claude Code takes a snapshot of your shell setup, including PATH, the list of folders searched for programs. If asking the shell for its PATH gives nothing usable, Claude Code now logs a warning and takes PATH from the shell creating the snapshot. Extra folders are no longer checked for duplicates against the failed value. Before, a failed lookup silently kept the old PATH.\n\n**Why**\n\nThis fixes cases where the PATH in a Windows snapshot came out wrong, which could stop commands being found.\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}