Repository navigation
Unable to install PowerShell 7.7.0 from the NuGet feed as it is not found. #28392
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues.
- Refer to the FAQ.
- Refer to Differences between Windows PowerShell 5.1 and PowerShell.
Steps to reproduce
Ref. #25446
Our CI jobs are failing as they attempt to install PowerShell as a .NET Global Tool.
Run dotnet tool install --global PowerShell to reproduce.
I have reproduced across Linux and macOS, but have not tried Windows as I don't have access to a Windows machine.
Expected behavior
You can invoke the tool using the following command: pwsh
Tool 'powershell' (version '7.7.0') was successfully installed.Actual behavior
Version 7.7.0 of package powershell.linux-x64 is not found in NuGet feeds https://api.nuget.org/v3/index.json.
Error: Process completed with exit code 1.Error details
Environment data
GitHub Actions Ubuntu-based runnerVisuals
No response
Reacted by Milan Gardian, Jia Yuan Lo and Brad
Activity
chomsky69 commentedon Nov 11, 2026
Facing the same issue. There seems to be a workaround with winget however, at least for Windows.
kilasuit commentedon Nov 11, 2026
Justin Chung (@jshigetomi) - looking at the 7.7.0 package on nuget.org this is showing as being (31.02 KB) vs the 7.6.10 package (41.3 MB) so looks to be an issue related to the build of the package that's submitted to nuget that's caused this. Looking at https://nuget.info/packages/PowerShell/7.7.0 & comparing vs https://nuget.info/packages/PowerShell/7.6.10 you can see the lacking of the package contents between those versions. I couldn't find where exactly the build of the .NET global tool and it's submission to nuget takes place.
milang commentedon Nov 11, 2026
Ryan Yates (@kilasuit) PowerShell 7.7 changed the
PowerShellNuGet package to only be a thin "redirection layer" that points to platform-and-architecture-specific package:The actual binaries should be in e.g.
PowerShell.win-x64orPowerShell.linux-x64orPowerShell.osx-arm64. The issue is that none of those binary packages have been published to NuGet, only the top-level package.Compare this to the latest 7.6 (also released yesterday) where the top level contains the binaries directly without a redirection layer:
