# Fix VS Code Terminal Profile Not Found PowerShell Error

You open the integrated terminal in VS Code and get an error:

bash
The terminal process "C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe" failed to launch (exit code: 1).

Or:

bash
Terminal profile "powershell" not found. Available profiles: ...

VS Code cannot find or launch the configured terminal shell.

Step 1: Check Terminal Profile Configuration

Open settings (Ctrl+,) and search for "terminal integrated default profile". On Windows, you should see:

json
{
    "terminal.integrated.defaultProfile.windows": "PowerShell",
    "terminal.integrated.profiles.windows": {
        "PowerShell": {
            "source": "PowerShell",
            "icon": "terminal-powershell"
        },
        "Command Prompt": {
            "path": [
                "${env:windir}\\Sysnative\\cmd.exe",
                "${env:windir}\\System32\\cmd.exe"
            ],
            "args": [],
            "icon": "terminal-cmd"
        },
        "Git Bash": {
            "source": "Git Bash"
        }
    }
}

If the PowerShell profile is missing or misconfigured, VS Code cannot find it.

Step 2: PowerShell Not Installed

On some Windows installations (especially Windows 10 N editions or minimal installs), PowerShell may not be at the expected path. Check:

powershell
where.exe powershell

If this returns nothing, PowerShell is not in the PATH. Install or reinstall it:

```powershell # Check if PowerShell is installed Get-Command powershell -ErrorAction SilentlyContinue

# If not, install via winget winget install Microsoft.PowerShell ```

Step 3: Execution Policy Blocking

PowerShell's execution policy may prevent VS Code from launching it:

powershell
Get-ExecutionPolicy -List

If the policy is Restricted, PowerShell cannot run any scripts. Set it to RemoteSigned:

powershell
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

This allows locally created scripts to run while requiring downloaded scripts to be signed.

Step 4: 32-bit vs 64-bit Path Issue

On 64-bit Windows, VS Code (if running as a 32-bit process) may look for PowerShell in the wrong system directory. The path ${env:windir}\\Sysnative\ is the correct redirection for 32-bit processes on 64-bit Windows.

Fix the profile path:

json
{
    "terminal.integrated.profiles.windows": {
        "PowerShell": {
            "path": [
                "C:\\WINDOWS\\Sysnative\\WindowsPowerShell\\v1.0\\powershell.exe",
                "C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\powershell.exe"
            ],
            "args": ["-NoLogo", "-NoProfile"]
        }
    }
}

The array provides fallback paths. VS Code tries each one until it finds an executable that exists.

Step 5: Windows Terminal Integration

If you have Windows Terminal installed, VS Code may try to use it as the terminal backend:

json
{
    "terminal.integrated.windowsEnableConpty": true
}

If this causes issues, disable it:

json
{
    "terminal.integrated.windowsEnableConpty": false
}

ConPTY (Consecutive Pseudo Console) is the modern Windows terminal API. It provides better compatibility but may not work correctly with some security software.

Step 6: Antivirus Interference

Some antivirus software blocks PowerShell execution from VS Code. Check your antivirus quarantine log for blocked powershell.exe launches.

Add VS Code and PowerShell to the antivirus whitelist:

bash
# Common paths to whitelist:
C:\Program Files\Microsoft VS Code\Code.exe
C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe

Step 7: Using PowerShell 7 Instead of Windows PowerShell

For a better experience, use PowerShell 7 (the cross-platform version):

json
{
    "terminal.integrated.defaultProfile.windows": "PowerShell 7",
    "terminal.integrated.profiles.windows": {
        "PowerShell 7": {
            "path": "pwsh.exe",
            "args": ["-NoLogo", "-NoProfile"],
            "icon": "terminal-powershell"
        }
    }
}

Install PowerShell 7:

powershell
winget install Microsoft.PowerShell

PowerShell 7 provides better cross-platform compatibility, improved performance, and newer language features compared to Windows PowerShell 5.1.

Step 8: Alternative Terminal Profiles

If PowerShell continues to fail, use an alternative:

json
{
    "terminal.integrated.defaultProfile.windows": "Git Bash",
    "terminal.integrated.profiles.windows": {
        "Git Bash": {
            "path": "C:\\Program Files\\Git\\bin\\bash.exe",
            "args": ["--login"],
            "icon": "terminal-bash"
        }
    }
}

Git Bash provides a Unix-like shell environment and works well for most development tasks.