3 ms·

If you have winget and powershell installed, try `Get-WingetPackage` and see what comes out. Or even better: gcm | ? noun -like winget* help Install-Wi

If you have winget and powershell installed, try `Get-WingetPackage` and see what comes out. Or even better: gcm | ? noun -like winget* help Install-WinGetPackage The "usual" winget cli tool is indeed not powershell compatible. But winget also ships with all the necessary cmdlets. You don't have to install anything extra.

gecko 2y ago
I was super excited to see this comment, but I don't seem to have those cmdlets, even though I'm on Windows 11, fully updated. Are you sure you didn't install something extra?
- easton 2y ago
  If I recall correctly, they only work in PowerShell 7. If you don’t even have them in there, you can install them from https://github.com/microsoft/winget-cli https://github.com/microsoft/winget-cli (which is bad UX, but if you just need them on one system it’s a way to do it).
  - gecko 2y ago
    I'm in PowerShell 7.4.2 and they're definitely absent. I hadn't thought to install directly from GitHub, given part of the whole shtick of winget is it's The One True Package Manager and bundled, but I can't say I'm surprised, either...
    - Uvix 2y ago
      Probably better off installing from PowerShell Gallery instead. https://www.powershellgallery.com/packages/Microsoft.WinGet.Client/ https://www.powershellgallery.com/packages/Microsoft.WinGet....
- deleted 2y ago
  [deleted]
- g15jv2dp 2y ago
  I don't remember. Maybe I did install the modules. https://www.powershellgallery.com/packages/Microsoft.WinGet.Client https://www.powershellgallery.com/packages/Microsoft.WinGet.... Install-Module -Name Microsoft.WinGet.Client
feldrim 2y ago
The Winget module is a wreck. The way it is designed, unfortunately, neither fits the object oriented approach of PowerShell nor follows the PowerShell guidelines for cmdlets. For instance https://github.com/microsoft/winget-cli/issues/3820 https://github.com/microsoft/winget-cli/issues/3820 or https://github.com/microsoft/winget-cli/issues/3231 https://github.com/microsoft/winget-cli/issues/3231. Also, even though it does not completely work with PowerShell 5, it is marked as compatible. https://github.com/microsoft/winget-cli/issues/2881 https://github.com/microsoft/winget-cli/issues/2881 The design choices made makes it weird. I hope it would be a good one in the future. But it is now problematic.

gecko 2y ago

I was super excited to see this comment, but I don't seem to have those cmdlets, even though I'm on Windows 11, fully updated. Are you sure you didn't install something extra?

easton 2y ago
If I recall correctly, they only work in PowerShell 7. If you don’t even have them in there, you can install them from https://github.com/microsoft/winget-cli https://github.com/microsoft/winget-cli (which is bad UX, but if you just need them on one system it’s a way to do it).
- gecko 2y ago
  I'm in PowerShell 7.4.2 and they're definitely absent. I hadn't thought to install directly from GitHub, given part of the whole shtick of winget is it's The One True Package Manager and bundled, but I can't say I'm surprised, either...
  - Uvix 2y ago
    Probably better off installing from PowerShell Gallery instead. https://www.powershellgallery.com/packages/Microsoft.WinGet.Client/ https://www.powershellgallery.com/packages/Microsoft.WinGet....
deleted 2y ago
[deleted]
g15jv2dp 2y ago
I don't remember. Maybe I did install the modules. https://www.powershellgallery.com/packages/Microsoft.WinGet.Client https://www.powershellgallery.com/packages/Microsoft.WinGet.... Install-Module -Name Microsoft.WinGet.Client

feldrim 2y ago

The Winget module is a wreck. The way it is designed, unfortunately, neither fits the object oriented approach of PowerShell nor follows the PowerShell guidelines for cmdlets. For instance https://github.com/microsoft/winget-cli/issues/3820 https://github.com/microsoft/winget-cli/issues/3820 or https://github.com/microsoft/winget-cli/issues/3231 https://github.com/microsoft/winget-cli/issues/3231. Also, even though it does not completely work with PowerShell 5, it is marked as compatible. https://github.com/microsoft/winget-cli/issues/2881 https://github.com/microsoft/winget-cli/issues/2881 The design choices made makes it weird. I hope it would be a good one in the future. But it is now problematic.