Troubleshoot installation and login changedtroubleshoot-install
Nearest release: v2.1.247, published under an hour before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+25added
Lines−0removed
From line
15
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits23to this page, all time
### `Raw mode is not supported` during install
The whole hunk
from line 15, old and new numbered
/
from line 15
1515| `curl: (22) The requested URL returned error: 403` | [Install script returned 403](#install-script-returns-html-instead-of-a-shell-script) |
1616| `curl: (23)` or `curl: (56) Failure writing output to destination` | [Check connectivity or use an alternative installer](#curl-56-failure-writing-output-to-destination) |
1717| `Killed` during install on Linux, or `Installation was killed before it could finish (exit code 137)` | [Free memory or add swap space](#install-killed-on-low-memory-linux-servers) |
18| `Raw mode is not supported` during install | [Rerun the installer](#raw-mode-is-not-supported-during-install) |
1819| `TLS connect error` or `SSL/TLS secure channel` | [Update CA certificates](#tls-or-ssl-connection-errors) |
1920| `Failed to fetch version` or can't reach download server | [Check network and proxy settings](#check-network-connectivity) |
2021| `irm is not recognized` or `&& is not valid` | [Use the right command for your shell](#wrong-install-command-on-windows) |
from line 634
633634 ```
634635
6356362. **Give Docker more memory** if using Docker Desktop. Build containers share the memory allocated to the Docker Desktop virtual machine, so open **Settings > Resources** in Docker Desktop, raise the memory limit, and rerun the build.
637
638### `Raw mode is not supported` during install
639
640When your organization's [server-managed settings](/docs/en/server-managed-settings) include changes that need [security approval](/docs/en/server-managed-settings#security-approval-dialogs), Claude Code versions before 2.1.246 try to show the approval dialog during `claude install`. The dialog needs a terminal on stdin. When the installer runs `claude install` from a pipe, as `curl -fsSL https://claude.ai/install.sh | bash` does, stdin is the pipe rather than a terminal, so the install fails with an error containing `Raw mode is not supported`.
641
642Claude Code v2.1.246 and later don't show the dialog during `claude install` or `claude update`. The command runs with the settings you last approved, and Claude Code shows the dialog in your next interactive session. If your organization's startup configuration [waits for the settings fetch](/docs/en/server-managed-settings#enforce-fail-closed-startup), such as when it sets `forceRemoteSettingsRefresh`, the dialog still appears during these commands, and an install run from a pipe still fails.
643
644In every other configuration, rerunning the installer gets past this error, because the script runs the latest release's `install` command even when you ask it to install an older version. Rerun the command for your platform:
645
646<Tabs>
647 <Tab title="macOS/Linux">
648 ```bash theme={null}
649 curl -fsSL https://claude.ai/install.sh | bash
650 ```
651 </Tab>
652
653 <Tab title="Windows PowerShell">
654 ```powershell theme={null}
655 irm https://claude.ai/install.ps1 | iex
656 ```
657 </Tab>
658</Tabs>
659
660`claude --version` prints the version the rerun installed.
636661
637662### `claude update` or `claude doctor` hangs
638663
No line in this hunk matches that.