Aspire VS Code extension cannot launch CLI on Windows when Aspire is installed as a global .NET tool and resolves to aspire.cmd

[kbkjeldsen]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

On Windows, the Aspire VS Code extension reports that the Aspire CLI is not installed or does not support the required feature, even though the CLI is installed and works from PowerShell.

In my environment I cannot use the official install script or install a standalone .exe because of enterprise security constraints. I installed the CLI with:

dotnet tool install --global Aspire.Cli

After that, aspire --version works in PowerShell, but the Aspire extension still fails and the Aspire sidebar shows:

The Aspire CLI is not installed or does not support this feature. Install or update the Aspire CLI and restart VS Code to get started.

PowerShell can resolve and run the aspire command successfully, but the extension fails to launch it.

Safe log excerpt from the Aspire extension log:

[warning] aspire describe --follow error: spawn aspire ENOENT
[warning] Error fetching running AppHosts: spawn aspire ENOENT

Expected Behavior

The Aspire VS Code extension finds the installed Aspire CLI and loads without any issues.

Steps To Reproduce

1. On Windows, install Aspire CLI as a global .NET tool:
   dotnet tool install --global Aspire.Cli
2. Restart VS Code or the machine.
3. Confirm the CLI works in PowerShell:
   aspire --version
4. Open VS Code with the Aspire extension installed.
5. Open the Aspire sidebar / Running AppHosts view.

Exceptions (if any)

No response

Aspire doctor output

Aspire Environment Check

.NET SDK
✅ .NET 10.0.300 installed (x64)

Container Runtime
✅ Docker v29.3.1: running (auto-detected (default)) ← active

Environment
✅ HTTPS development certificate is trusted

Summary: 3 passed, 0 warnings, 0 failed

Anything else?

No response

[joperezr]

🤖 Aspire triage pass — 2026-05-20 08:44 UTC

Area: area-extension
Kind: bug
Repro: yes-minimal — see the numbered "Steps To Reproduce" in the issue body
Affected version(s): Aspire CLI installed via dotnet tool install --global Aspire.Cli on Windows; .NET SDK 10.0.300
Severity: S3 — VS Code extension cannot spawn aspire on Windows when the CLI is a global .NET tool (resolves to aspire.cmd); spawn aspire ENOENT is logged. Workaround exists (use the install script / standalone exe), but is blocked for users under enterprise constraints.

Urgency: 🟡 vNext — recommend milestone 13.4
Reason: clean repro in area-extension, S3 with workaround, not a confirmed regression vs 13.2 (so does not meet the servicing bar).

Suggested owner(s): @adamint (score ~43)
Evidence:

• @adamint authored 14 merged PRs labeled area-extension in the last 90 days (e.g. Add Simple Browser option for dashboard launch #15896, Use deny list for non-linkable endpoint URLs in extension #15894, Use PR-specific version for dogfood VS Code extension #15892, VS Code extension: Improve gutter, code lens, and tree view resource state indicators #15688, VS Code extension: Auto-restore on workspace open and config change #15546)
• @adamint is the assignee on 36 completed area-extension issues in the last 180 days
• .github/CODEOWNERS lists @adamint as the owner of /extension

Confidence: medium
Needs human?: no

Dry-run mode — no labels or milestone applied. Reply /triage apply to promote, or edit and reapply.

[adamint]

There's overlap with #15363