Closed marticliment closed 1 month ago
Does the same thing happen with the 1.8.1133 version of the module?
I don't know where the Get-WinGetPackageUpdate cmdlet is coming from.
I'm getting the Name column:
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.
My excuses, I somehow had Cobalt (an alternative WinGet pwsh interface) installed on my machine.
Brief description of your issue
The
Get-WinGetPackage
andGet-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
:Get-WinGetPackage
: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