CLI and PowerShell module for the same package show different versions

[denis-komarov]

Brief description of your issue

CLI and PowerShell module for the same package show different versions.

Steps to reproduce

winget search --id QuestSoft.QTranslate --source winget

Name       Id                   Version
---------------------------------------
QTranslate QuestSoft.QTranslate 6.10.0

Find-WinGetPackage -Id QuestSoft.QTranslate -Source winget

Name       Id                   Version Source
----       --                   ------- ------
QTranslate QuestSoft.QTranslate 6.9.0   winget

Expected behavior

CLI and PowerShell module for the same package show the same versions

Actual behavior

CLI and PowerShell module for the same package show different versions

Environment

Windows Package Manager v1.6.3482
Windows: Windows.Desktop v10.0.19045.2604
System Architecture: X64

[denelon]

Could you reproduce this?

What version of WinGet and what version of Microsoft.WinGet.Client is on the device?

I just tested and I got the same version for both:

 denelon  winget search --id QuestSoft.QTranslate --source winget
Name       Id                   Version
---------------------------------------
QTranslate QuestSoft.QTranslate 6.10.0
 denelon 
 denelon  Find-WinGetPackage -Id QuestSoft.QTranslate -Source winget

Name       Id                   Version Source
----       --                   ------- ------
QTranslate QuestSoft.QTranslate 6.10.0  winget

[denis-komarov]

@denelon It seems the latest version of the PowerShell module comes with an outdated version of the kernel (v1.4.10173).

winget --version

v1.6.3482

Get-Module -Name 'Microsoft.WinGet.Client'

Name              : Microsoft.WinGet.Client
Path              : D:\d\run\powershell\modules\Microsoft.WinGet.Client\1.6.3133.0\net6.0-windows10.0.22000.0\Microsoft.WinGet.Client.Cmdlets.dll
Description       : PowerShell Module for the Windows Package Manager Client. Due to https://github.com/PowerShell/PowerShellGet/issues/85 this module is not marked as pre
                    release but should be treated as such.
Guid              : e11157e2-cd24-4250-83b8-c6654ea4926a
Version           : 1.6.3133.0
ModuleBase        : D:\d\run\powershell\modules\Microsoft.WinGet.Client\1.6.3133.0
ModuleType        : Binary
PrivateData       : {[CrescendoVersion, 1.0.0], [CrescendoGenerated, 07/07/2022 00:00:00], [PSData, System.Collections.Hashtable]}
AccessMode        : ReadWrite
ExportedAliases   : {}
ExportedCmdlets   : {[Add-WinGetSource, Add-WinGetSource], [Assert-WinGetPackageManager, Assert-WinGetPackageManager], [Disable-WinGetSetting, Disable-WinGetSetting], [Ena
                    ble-WinGetSetting, Enable-WinGetSetting]…}
ExportedFunctions : {}
ExportedVariables : {}
NestedModules     : {}

Get-WinGetVersion

v1.4.10173

[Trenly]

@denis-kmarov - There has been a new release of both the client and the PowerShell module. Can you please check if this issue still occurs after updating both?

[denis-komarov]

@Trenly The problem also occurs on the new version of Microsoft.WinGet.Client 1.7.10661 :

Get-Module -Name 'Microsoft.WinGet.Client' | Format-List -Property 'Name', 'Version'
Find-WinGetPackage -Id QuestSoft.QTranslate -Source winget

Name    : Microsoft.WinGet.Client
Version : 1.7.10661


Name       Id                   Version Source
----       --                   ------- ------
QTranslate QuestSoft.QTranslate 6.9.0   winget