VS Code Terminal Not Working
Workaround available Windows, macOS, Linux Updated November 13, 2026Based on 3 user reportsHow we research
Quick answer
The integrated terminal usually fails because of a bad shell path, a missing working directory, a broken startup file or shell integration. Switch shell, then test startup files and disable shell integration.
Most likely fix: Pick a different shell
How to fix it
Try these in order — the most common fix is first.
1. Pick a different shell
- Click the dropdown next to the + in the Terminal panel
- Choose another installed shell
- Run Terminal: Select Default Profile to make it permanent
Did this fix it?2. Check profile and cwd settings
- Open Settings and search terminal.integrated.profiles
- Confirm each executable path exists
- Check terminal.integrated.cwd and terminal.integrated.env for your platform
Did this fix it?3. Test the shell without startup files
- In an external terminal run bash --noprofile --norc, zsh -f, or pwsh -NoProfile
- If it works, inspect .bashrc, .zshrc or your PowerShell profile for lines that exit or error
Did this fix it?4. Disable shell integration to test
- Note the current value of terminal.integrated.shellIntegration.enabled
- Set it to false and open a new terminal
- Restore it afterwards if it was not the cause
Did this fix it?5. Fix Windows and WSL cases
- Right-click Code.exe > Properties > Compatibility and clear compatibility mode
- For WSL exit code 1 run wsl --status and wsl --list --verbose
- Use wsl --set-default so the default is not docker-desktop-data
Did this fix it?6. Capture trace logs
- Run Developer: Set Log Level and choose Trace
- Reproduce the failure
- Run Developer: Open Log and check Terminal and Pty Host logs
Did this fix it?
Symptoms
The terminal shows 'The terminal process failed to launch', exits with a code, or closes right after opening.
Why it happens
- Invalid shell path in terminal.integrated.profiles
- Missing terminal.integrated.cwd directory
- terminal.integrated.env overrides breaking PATH
- Shell startup file exits or errors
- Shell integration conflict
- Untrusted workspace
- Windows compatibility mode or broken WSL default distro
This guide also covers
- vscode terminal not working
- terminal process failed to launch vscode
- vs code terminal not opening
Still not working?
If VS Code keeps failing, you're not alone. See every VS Code problem users report or the alternatives people switch to.
Need a custom web app or internal tool? Our small team builds it, on your domain or hosted by us. Price agreed together.
Get a quote