[main] `aspire doctor` taking 15 secs to run

[afscrome]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

On my machine, running aspire doctor takes roughly 15 secs. It seems to get stuck making calls to api.nuget.org which are blocked as my company runs our own internal mirror. when looking for updated to Aspire.Cli

I think this is new in 13.5 - I don't recall encountering this with 13.4.

Expected Behavior

aspire doctor should complete within a few seconds.

Steps To Reproduce

Run aspire doctor

Exceptions (if any)

snippet of logs

[17:58:10] [dbug] BundleNuGetPackageCache: NuGet search args: nuget search --query Aspire.Cli --take 1000 --format json --prerelease --working-dir S:\REDACTED --verbose
[17:58:10] [dbug] BundleNuGetPackageCache: Working directory: S:\REDACTED
                                
⠳ Checking Aspire environment...
                                [17:58:11] [dbug] InstallationDiscovery: Discovery: dotnet-tool store 'C:\Users\alexanderc\.dotnet\tools\.store\aspire.cli' does not exist; skipping.
                                scovery: Discovery: walk complete. Considered 3 candidate(s); produced 2 row(s) total (including self).
⠴ Checking Aspire environment... Discovered 2 Aspire CLI installation(s) for doctor output.
                                [17:58:22] [dbug] BundleNuGetPackageCache: NuGetHelper stderr: Using source from config: Nexus (https://REDACTED/repository/nuget/index.json)
Using source from config: https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9/nuget/v3/index.json (https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9/nuget/v3/index.json)
Using source from config: https://api.nuget.org/v3/index.json (https://api.nuget.org/v3/index.json)
Searching 3 source(s) for 'Aspire.Cli'
Searching Nexus (https://REDACTED/repository/nuget/index.json)...
Found 1 search endpoints.
Querying https://REDACTED/repository/nuget/v3/query/beta?q=Aspire.Cli&skip=0&take=1000&prerelease=true&semVerLevel=2.0.0
Searching https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9/nuget/v3/index.json (https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9/nuget/v3/index.json)...
Found 1 search endpoints.
Querying https://pkgs.dev.azure.com/dnceng/9ee6d478-d288-47f7-aacc-f6e6d082ae6d/_packaging/a54510f9-4b2c-4e69-b96a-6096683aaa1f/nuget/v3/query2/?q=Aspire.Cli&skip=0&take=1000&prerelease=true&semVerLevel=2.0.0
Searching https://api.nuget.org/v3/index.json (https://api.nuget.org/v3/index.json)...
Warning: Failed to search https://api.nuget.org/v3/index.json: Unable to load the service index for source https://api.nuget.org/v3/index.json.

Aspire doctor output

Aspire Environment Check

Aspire
⚠️ Aspire CLI version 13.5.0-preview.1.26405.1 (channel: daily) is out of date. Latest version is 13.5.0-preview.1.26405.2 (channel: prerelease)
Run 'aspire update' to update Aspire CLI.
✅ Developer Control Plane (DCP) connection health checks succeeded

AppHost
✅ AppHost version 13.5.0-preview.1.26405.1 (app\Trayport.Aspire.AppHost\Trayport.Aspire.AppHost.csproj)

.NET SDK
✅ .NET 10.0.302 installed (x64)

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

Environment
✅ Operating system: Windows 10.0.26100.0
✅ HTTPS development certificate is trusted

Development Tools
✅ Aspire extension for VS Code is installed

Summary: 7 passed, 1 warnings, 0 failed
For detailed prerequisites: https://aka.ms/aspire-prerequisites

Aspire CLI Installations

╭───────────────────────────────────────────────────────┬──────────────────────────────────────────────────────┬──────────┬───────────┬─────────────╮
│ Path │ Version │ Channel │ Route │ PATH status │
├───────────────────────────────────────────────────────┼──────────────────────────────────────────────────────┼──────────┼───────────┼─────────────┤
│ C:\Users\alexanderc.aspire\bin\aspire.exe (current) │ 13.5.0-preview.1.26405.1+0182d1671498df3020eea7af5b0 │ daily │ (unknown) │ active │
│ │ 06eb0bddbafc9 │ │ │ │
│ C:\Users\alexanderc.aspire\dogfood\pr-18906\bin\aspi │ 13.5.0-pr.18906.gba3f0960 │ pr-18906 │ pr │ not on PATH │
│ re.exe │ │ │ │ │
╰───────────────────────────────────────────────────────┴──────────────────────────────────────────────────────┴──────────┴───────────┴─────────────╯

Anything else?

No response

[joperezr]

🤖 Aspire triage pass — 2026-08-05 17:57 UTC

Area: area-cli
Kind: bug (performance; suspected regression — unconfirmed)
Repro: yes-minimal — run aspire doctor (see log snippet in body)
Affected version(s): 13.5.0-preview.1 (daily); reporter believes 13.4 was unaffected but is not certain
Severity: S3 — aspire doctor takes ~15s because the CLI update check searches api.nuget.org, which stalls in environments using an internal-only NuGet mirror; completes eventually

Urgency: ⚪ backlog — no milestone
Reason: reporter's "new in 13.5" claim is uncertain, so it does not clear the confirmed-regression bar for 13.5; routed to backlog for a human to pull up if the regression is confirmed

Suggested owner(s): James Newton-King (@JamesNK) (score 12), backup Mitch Denny (@mitchdenny) (score 5)
Evidence:

• JamesNK merged Show status while preparing dashboard bundle #18985, Bound aspire doctor checks with timeouts #18969, Make CLI package metadata prefetching opt-in #18968 and many more in area-cli (last 30d)
• mitchdenny merged Remove duplicated profiles block from empty C# AppHost aspire.config.json #17781, fix(cli): restore implicit-channel discovery + guard non-interactive fuzzy auto-pick (#17724, #17725) #17728, Forward IdentityChannel to TemplateInputs.Channel for dotnet-runtime templates #17637 in area-cli
• CODEOWNERS lists Mitch Denny (@mitchdenny) James Newton-King (@JamesNK) David Fowler (@davidfowl) for src/Aspire.Cli

Confidence: medium
Needs human?: no

[adamint]

I can reproduce the ~15 second delay on current main with an isolated NuGet configuration containing one reachable feed and one controlled blocked source.

The CLI update check took about 1.5 seconds with only the reachable feed and about 12 seconds after adding the blocked source; full aspire doctor moved from a 2–3 second update phase to 12–13 seconds, roughly 15 seconds wall-clock. The blocked source was retried six times while the reachable source still returned the current Aspire CLI version.

The cause is the update check searching every configured source via Task.WhenAll with SearchAsync(..., CancellationToken.None). A single blocked source therefore stalls the entire doctor command through NuGet retries. The same no-timeout path exists in 13.4.6, so I do not think this is new in 13.5.

This remains current; the update check needs to be bounded or made best-effort so one unavailable source cannot block aspire doctor.