Cursor crashes/gets connection error when using dotnet Windows 11

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When cursor tries to use the terminal and call dotnet --version, it gets Connection failed. If the problem persists, please check your internet connection or VPN. This is from a fresh install of windows 11. dotnet 10 is installed. The last thing cursor sees is "The command could not be loaded, possibly because:

  • You intended to execute a .NET application:
    The application ‘–version’ does not exist.
  • You intended to execute a .NET SDK command:
    No .NET SDKs were found.

Download a .NET SDK:

Learn about SDK resolution:
Select which .NET version to use - .NET | Microsoft Learn"

Request ID: f7b778fd-086a-4026-840a-5adf26adb85b

Steps to Reproduce

This is on auto mode, ask cursor to install or build an executable and it will use dotnet --version on windows 11 and it will get Connection Error. This is reproducible for me.

Expected Behavior

Cursor should not have a connection error from running dotnet --version.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.44 (system setup)
VSCode Version: 1.105.1
Commit: 20adc1003928b0f1b99305dbaf845656ff81f5d0
Date: 2025-12-24T21:41:47.598Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Auto

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, thanks for the report.

I see two things here:

  1. .NET SDK issue:
    Your terminal output shows “No .NET SDKs were found”, which means the .NET SDK isn’t installed correctly on your system. Please install the SDK from Download .NET (Linux, macOS, and Windows) | .NET and make sure dotnet --version works in a normal PowerShell or CMD.

  2. “Connection failed” error:
    This might be related to HTTP/2. Please try:

  • Open Settings Ctrl+,, search for HTTP/2, enable “Disable HTTP/2”, then restart Cursor
  • Settings > Network > Run Diagnostics, then send a screenshot

Also please share:

  • The output of dotnet --version in a normal Windows Terminal (not inside Cursor)
  • Console errors: Help > Toggle Developer Tools > Console

Docs: Common Issues | Cursor Docs

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.