Skip to main content
Watch: I Built an AI App Without Leaving Databricks

Cline error

Cline: Command failed with exit code 1: powershell (Get-CimInstance -ClassName...

Error message
Command failed with exit code 1: powershell (Get-CimInstance -ClassName Win32_OperatingSystem).caption
'powershell' is not recognized as an internal or external command,
operable program or batch file.

Status: WorkaroundLast verified 1 documented fix2 sources

What it means

Windows cannot find the PowerShell executable when Cline queries the OS. The extension links errors mentioning PowerShell to the official wiki troubleshooting guide.

Causes

  • The user or system PATH environment variable does not contain the directory where the PowerShell executable lives, per the official wiki.

How to fix it

  1. Fix 1.

    Open System > Advanced system settings > Environment Variables, edit "Path" (User or System), click New and add the Windows PowerShell directory, click OK on all windows, then restart the computer.

    Snippet
    %SYSTEMROOT%\System32\WindowsPowerShell\v1.0\

More Cline errors

All 17 Cline errors

FAQ

What does "Command failed with exit code 1: powershell (Get-CimInstance -ClassName..." mean in Cline?

Windows cannot find the PowerShell executable when Cline queries the OS. The extension links errors mentioning PowerShell to the official wiki troubleshooting guide.

How do I fix "Command failed with exit code 1: powershell (Get-CimInstance -ClassName..."?

Open System > Advanced system settings > Environment Variables, edit "Path" (User or System), click New and add the Windows PowerShell directory, click OK on all windows, then restart the computer.

Is this Cline error fixed?

Status: Workaround. No release removes the cause. The documented fixes work around it.

Sources

Last verified against 2 sources: official docs, maintainer replies and release notes.

Newsletter

Fixes for the tools you use, weekly

One email per week. New coding agent releases, what broke, and how developers are working around it.