Skip to content

[Package Issue]: Microsoft.PowerShell #254388

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
2 tasks done
simkoG opened this issue May 6, 2025 · 5 comments
Open
2 tasks done

[Package Issue]: Microsoft.PowerShell #254388

simkoG opened this issue May 6, 2025 · 5 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention This work item needs to be reviewed by a member of the core team.

Comments

@simkoG
Copy link

simkoG commented May 6, 2025

Please confirm these before moving forward

  • I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
  • I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue

No applicable update found.

Brief description of your issue

I am unable to update Microsoft.PowerShell package from version 7.4.7.0 to the latest (7.5.1.0 right now) version.

winget list -q powershell
Name                   Id                        Version      Available Source
------------------------------------------------------------------------------
PowerShell 7.4.7.0-x64 Microsoft.PowerShell      7.4.7.0      7.5.1.0   winget

Steps to reproduce

Run one of these commands from a CMD window (not powershell):

winget upgrade powershell --silent
winget upgrade --id "Microsoft.PowerShell" --silent

Actual behavior

winget upgrade powershell --silent
No available upgrade found.
No newer package versions are available from the configured sources.

winget upgrade --id "Microsoft.PowerShell" --silent
No installed package found matching input criteria.

Expected behavior

Upgrade package to the lastest version.

Environment

Windows Package Manager v1.10.390
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.26100.3915
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.25.390.0

Winget Directories
----------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Dia…
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\set…
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads
Configuration Modules              %LOCALAPPDATA%\Microsoft\WinGet\Configuration\Modules

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled
ProxyCommandLineOptions                   Disabled
DefaultProxy                              Disabled

Screenshots and Logs

No response

@simkoG simkoG added the Issue-Bug It either shouldn't be doing this or needs an investigation. label May 6, 2025
Copy link

We've found some similar issues:

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage This work item needs to be triaged by a member of the core team. label May 6, 2025
@Utesgui
Copy link
Contributor

Utesgui commented May 6, 2025

Can't reproduce 🙁 I have tested multiple Windows 11 installations as well as Windows Server 2025 with different Powershell-Versions to upgrade from, but in any case the update went through without issue:

Image

@Trenly
Copy link
Contributor

Trenly commented May 6, 2025

@simkoG - There may be a difference between the version of PowerShell that ships with Windows, and the version that is distributed through their GitHub. Does it work if you use winget install Microsoft.PowerShell --force ?

@microsoft-github-policy-service microsoft-github-policy-service bot removed the Needs-Triage This work item needs to be triaged by a member of the core team. label May 6, 2025
@ItzLevvie
Copy link
Contributor

[Policy] Needs-Author-Feedback

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Author-Feedback This needs a response from the author. label May 19, 2025
@simkoG
Copy link
Author

simkoG commented May 19, 2025

@Trenly tried --force, did not help. I've upgraded the package via standalone installer, that fixed it.

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention This work item needs to be reviewed by a member of the core team. and removed Needs-Author-Feedback This needs a response from the author. labels May 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention This work item needs to be reviewed by a member of the core team.
Projects
None yet
Development

No branches or pull requests

4 participants