{"version":"2.1.287","anchor":"warning-when-denying-bash-also-removes-the-powershell-tool","canonical_anchor":"warning-when-denying-bash-also-removes-the-powershell-tool","heading":"Windows warning when blocking Bash also turns off PowerShell","tier":"notice","area":"Windows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/warning-when-denying-bash-also-removes-the-powershell-tool","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Windows warning when blocking Bash also turns off PowerShell\n\nOn Windows, Claude Code now warns that a Bash deny rule also removes the PowerShell tool, leaving Claude with no shell\n\n**Unclear.** One further condition for showing the warning could not be identified.\n\n**What**\n\nOn Windows, Claude Code can add a PowerShell tool automatically so Claude can run commands. A deny rule is a setting that blocks Claude from using a tool. If you have a deny rule for Bash, it also turns off that automatically added PowerShell tool, and Claude Code now shows a warning about it. The warning says Claude has neither shell tool, and that to use PowerShell you can set `CLAUDE_CODE_USE_POWERSHELL_TOOL=1`.\n\nThe warning is not shown when the deny rule comes from policy settings, which are settings managed by an administrator.\n\n**Why**\n\nIt explains why Claude suddenly cannot run any commands on Windows, and tells you how to get PowerShell back.\n\n- Area: Windows\n- Names: `CLAUDE_CODE_USE_POWERSHELL_TOOL`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}