Skip to content
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

The Get-WinGetPackage and Get-WinGetPackageUpdate cmdlets do not report anymore the package name #4488

Closed
marticliment opened this issue May 16, 2024 · 3 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. PowerShell Issue related to WinGet PowerShell Module or cmdlet
Milestone

Comments

@marticliment
Copy link

Brief description of your issue

The Get-WinGetPackage and Get-WinGetPackageUpdate cmdlets do not report anymore the package name. Therefore, it is not possible to obtain the package name for certain entries where the IDs are not representative of the package.

The PSObject representing packages do not appear to have anymore the $Name attributes.

Get-WinGetPackageUpdate:
image

Get-WinGetPackage:
image

Steps to reproduce

Update the PowerShell module and WinGet to the latest stable version

Expected behavior

Have the $Name attribute exposed as before

Actual behavior

The $Name attribute is not available

Environment

[winget --info]
Windows Package Manager v1.7.11261
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22635.3570
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.22.11261.0

Winget Directories
-------------------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
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

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                        Enabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled

[Get-WinGetVersion]
v1.7.11261

[Get-InstalledModule]

Version              Name                                Repository           Description
-------              ----                                ----------           -----------
1.7.11132            Microsoft.WinGet.Client             PSGallery            PowerShell Module for the Windows Package Manager Client. Due to https://github.com/PowerShell/PSResourceGet/issues/85 this mod...
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage Issue need to be triaged label May 16, 2024
@denelon denelon added Issue-Bug It either shouldn't be doing this or needs an investigation. PowerShell Issue related to WinGet PowerShell Module or cmdlet and removed Needs-Triage Issue need to be triaged labels May 16, 2024
@denelon
Copy link
Contributor

denelon commented May 16, 2024

Does the same thing happen with the 1.8.1133 version of the module?

image

I don't know where the Get-WinGetPackageUpdate cmdlet is coming from.

I'm getting the Name column:

image

@marticliment
Copy link
Author

Yes, v1.8.1133 also seems to be affected.

Uh, in theory Microsoft.WinGet.Client is the only PS package I have installed, but I will try to reset my whole powershell environment and try again.

@marticliment
Copy link
Author

My excuses, I somehow had Cobalt (an alternative WinGet pwsh interface) installed on my machine.

@marticliment marticliment closed this as not planned Won't fix, can't repro, duplicate, stale May 17, 2024
@denelon denelon added this to the 1.8 Client milestone May 28, 2024
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. PowerShell Issue related to WinGet PowerShell Module or cmdlet
Projects
None yet
Development

No branches or pull requests

2 participants