You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Corrupt dotnet binary exits with exit code 137 after installing .NET 10 #662
Bug / issue When using dotnet-install.sh to install .NET 10, the script installs version 10.0.100.
curl -sSL https://dot.net/v1/dotnet-install.sh | bash /dev/stdin --channel LTS
After the installation has complete, I try list the installed SDKs on my machine:
~/.dotnet/dotnet --list-sdks
The operation fails with zsh terminating the shell. The ~/.dotnet/dotnet binary exited with exit code 137.
zsh: killed ~/.dotnet/dotnet --list-sdks
Operating system: macOS 15.7.2 Architecture: Apple silicon / ARM / arm64
Expected behavior
The ~/.dotnet/dotnet --list-sdks command lists all versions of .NET installed on the machine.
@chrishaland what other versions do you have in ls ~/.dotnet/sdk?
I was experiencing problems attempting to install 9 and/or 10 alongside 8.0.404 (still needed due to xunit v3 shenanigans in a particular solution) until I installed 8.0.416 first, ie:
I tried installing the newest version of .NET 8 as suggested by @anaerobic (though our starting points seems to differ) and still experienced the same issue:
Activity
ellahathaway commentedon Nov 19, 2025
Exit code 137 usually means the process was killed due to running out of memory (OOM). Can you try doing a fresh install with the following steps:
anaerobic commentedon Nov 21, 2025
@chrishaland what other versions do you have in
ls ~/.dotnet/sdk?I was experiencing problems attempting to install 9 and/or 10 alongside 8.0.404 (still needed due to xunit v3 shenanigans in a particular solution) until I installed 8.0.416 first, ie:
hopefully this helps!
-MWM
chrishaland commentedon Nov 21, 2025
I have the following versions installed:
ls ~/.dotnet/sdk 10.0.100 8.0.415 9.0.306I tried installing the newest version of
.NET 8as suggested by @anaerobic (though our starting points seems to differ) and still experienced the same issue:After the failed attempt I removed the previously installed SDKs and reinstalled them, which resolved the issue:
Even though this resolved the issue, I prefer doing a clean install and I'm not prevented from doing so. Following @ellahathaway suggestion: