Open iCanHazConfetti opened 1 week ago
Was about to create this issue to.
I suggest the package manifest for PowerShell in WinGet should automatically define POWERSHELL_UPDATECHECK=Off when installed. Then leave it to WinGet to do the update when it is ready and avoid the pointless nagging message.
Hello I seem to have a similar issue. Albeit with mine, winget does say there is a new powershell update, but it fails to actually perform the updating.
Prompt from Powershell stating there's an Update
Winget update shows that there is a new version of PowerShell available. v7.4.3.0 and the source is Winget:
Winget fails to update Powershell citing No installed package found matching input criteria.
and even fails when you specify the version number.
Prerequisites
Steps to reproduce
(v7.4.3) Release of PowerShell (Latest) - NOT YET AVAILABLE - via --source winget (PLEASE FIX) Attempt via ' PS (v7.4.2) ' in ' Windows Terminal (v1.20.11381.0) ' from ' --source (winget) ' It is (2024-06-16 @ 11:55 PDT) currently.
Receive NOTICE when I open a New Tab in Windows Terminal (v1.20.11381.0) that is PowerShell (v.7.4.2) (both are the latest available via WinGet on my System. Yes. Did a : 'winget source update' prior to a : 'winget upgrade -r -u --force --verbose --wait -s winget' ...
NOTICE LISTS : '' A new PowerShell stable release is available: v7.4.3 Upgrade now, or check out the release page at: https://aka.ms/PowerShell-Release?tag=v7.4.3 '' ...
WinGet can NOT find PowerShell (v7.4.3) via ' --name ' , ' --id ' , OR ' --version ' in the ' --source winget ' ?Repo? (is that the correct term)?
PLEASE FIX the winget source so that ' PowerShell --tag v7.4.3 can be located/installed/upgraded via WinGet
FYI ' App Installer is already installed ' , ' (v1.22.11261.0) on Windows 10.
THANKS in advance!
Expected behavior
Actual behavior
Error details
Environment data
Visuals