[BUG] PowerShellGet 1.x (Update-Module) has no -Scope parameter (Microsoft.WinGet.Client can't be updated) #2814
Comments
Apparently 1.6.0 is so old it can't update itself anymore After running Note: My Win10 is an upgraded Win7 from 2009. Apparently it stopped 2017 |
|
I will investigate, but Windows 10/11 is supposed to come with PowerShellGet v2 by default, perhaps the fact that your pc is a Win7 upgrade could explain why this issue is happening |
|
Noticed I had the same issue, so I came here. Tried updating it: Looking at the folder listed above it seems I have version 1.0.0.1.
Tried it. Had to remove the folder by hand. Then I noticed uniget was running in a completly different powershell. The one from While the regular powershell I use: So I had to rerun the same command in the older powershell that gets used by uniget. No idea why they seem to not share packages..... |
|
PowerShell 5.1 is the one inside of Windows which will remain as-is, because Microsoft doesn't want to break existing users (and leverage Windows-only-features) So UniGet supports both, but apparently 5.1 can be broken (by something). |
|
Same thing here. I'm on a Windows 11 install that was a clean install at the time. I had powershellget 1.0.0.1 and no matter what I tried I couldn't get to to upgrade. The only thing that worked was replacing PowerShellGet and PackageManagement in program files with manually downloaded versions. Looking back in the console of all the things I tried, i just noticed I missed this error about the -AllowClobber parameter so no idea if it would have helped: So maybe something like this would have helped: I'm available to do more testing or try to reproduce this more if it would help. |
|
Indeed, I have installed Win 11 24H2, as new as it gets, and it has version |
|
And also interesting, it seems to be on purpose |
|
And 3rd update 😄 The It would require some mechanism of detecting a "Locked down version 1" and keep it. Or notify about an outdated "installable" version. |
|
For anyone looking for a temporary workaround, you can go into the installation options and add an additional parameter similar to the following: Alternatively, you could remove the null suppression so any errors do bubble up: |
marticliment
changed the title
Thanks, it worked for me! |
Is this where you enter the additional parameter or Why do I keep getting prompted for Launching subprocess.-- |
|
I have fixed the issue. Please wait for the next beta release and test if the issue gets resolved for you. I will let you know when a new beta release is available. |
Danke, auch bei mir wurde das Problem behoben. |
|
Please try this new release: https://github.com/marticliment/UniGetUI/releases/tag/3.1.4-beta1 |
Please confirm these before moving forward
UniGetUI Version
3.1.2.beta3
Windows version, edition, and architecture
Windows 10
Describe your issue
I am not making sure all my PowerShell 5.x modules are up to date. So apparently I "only" have PowerShellGet 1.x and get the following error
https://learn.microsoft.com/en-us/powershell/module/powershellget/update-module?view=powershellget-1.x
Has noscope (pun intended)
While
https://learn.microsoft.com/en-us/powershell/module/powershellget/update-module?view=powershellget-2.x
or 3.x has
Can UniGet update "PowerShellGet", too?!
Or at least check if 2.x+ is installed?!
Steps to reproduce the issue
No response
UniGetUI Log
Package Managers Logs
Relevant information
No response
Screenshots and videos
No response
The text was updated successfully, but these errors were encountered: