Winget Manifest Issue: Sidekick-Poe/Sidekick Package Shows Upgrade Available When Already Latest

Offen
#6,566 9 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
42/100
Issue-Typ
Bug
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
cpp
Bereich
cli

Rechercherichtung

Start by reproducing the behavior with winget source, winget upgrade, and winget export, using the reported Sidekick-Poe.Sidekick package and WinGet environment details. Compare how the installed Gigabyte Sidekick is identified with the package metadata and the linked Sidekick issue; done means the unrelated package is no longer reported as an upgrade for that installation.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Command-Source Command-Upgrade Issue-Bug
Relevant area(s)

WinGet CLI

Relevant command(s)

winget source, winget upgrade

Brief description of your issue

The installed program name Sidekick that I have is a add-on program that comes with Gigabyte Control Center, and was installed along with it about 6-7 months ago.

Then today I ran winget upgrade, and the "Sidekick-Poe.Sidekick" package was showing as installed with an update. Had no clue what it was and knew I never installed it.

No clue how it got there. But it's even showing up in winget export

It turns out the Gigabyte Sidekick program had an actual update as well.

So I ran the installer from the new GCC, updated that Sidekick. Refreshed winget, and the version that is showing as installed under your package has now been bumped up to the version I just installed.

I created an issue here as well https://github.com/Sidekick-Poe/Sidekick/issues/1277

Steps to reproduce

No clue. Just showed up.

Expected behavior

To not do this? Lol

Actual behavior

Incorrect identifying the wrong program and/or package to upgrade.

Environment
C:\>winget --info --verbose
    Windows Package Manager (Preview) v1.30.140-preview
    © 2026 Microsoft. All rights reserved.

Windows: Windows.Desktop v10.0.26340.9482
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.30.140.0

WinGet Directories
---------------------------------------------------------------------------------------------------------------------------------------------
Logs                               C:\Users\Owner\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings                      C:\Users\Owner\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
Portable Links Directory (User)    C:\Users\Owner\AppData\Local\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       C:\PORTABLE-APPS
Portable Package Root              C:\PORTABLE-APPS
Portable Package Root (x86)        C:\PORTABLE-APPS
Installer Downloads                C:\Users\Owner\Downloads
Configuration Modules              C:\Users\Owner\AppData\Local\Microsoft\WinGet\Configuration\Modules

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


Group Policy                                           State
--------------------------------------------------------------
Enable Windows Package Manager                         Enabled
Enable Windows Package Manager Settings                Enabled
Enable Windows App Installer Experimental Features     Enabled
Enable Windows Package Manager command line interfaces Enabled
Enable Windows Package Manager Configuration           Enabled

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled
ProxyCommandLineOptions                   Disabled
ConfigurationProcessorPath                Disabled
DefaultProxy                              Disabled

{
	"$schema" : "https://aka.ms/winget-packages.schema.2.0.json",
	"CreationDate" : "2026-09-25T10:41:01.767-00:00",
	"Sources" : 
	[
		{
			"Packages" : 
			[
				{
					"PackageIdentifier" : "Streamlabs.Streamlabs",
					"Version" : "1.21.9"
				},
				............................ // cut out huge section of export to shorten the thread.
				{
					"PackageIdentifier" : "Rufus.Rufus",
					"Version" : "4.15"
				},
				{
					"PackageIdentifier" : "Sidekick-Poe.Sidekick",
					"Version" : "25.09.30.01"
				...............................

			],
			"SourceDetails" : 
			{
				"Argument" : "https://storeedgefd.dsx.mp.microsoft.com/v9.0",
				"Identifier" : "StoreEdgeFD",
				"Name" : "msstore",
				"Type" : "Microsoft.Rest"
			}
		}
	],
	"WinGetVersion" : "1.30.140-preview"
}
Vorherrschende Sprache
C++
Sterne
26.6k
Forks
1.8k
Ø Merge
3 T. 10 Std.
Gemergte PRs (30 T.)
41

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus microsoft/winget-cli

Alle Issues in microsoft/winget-cli

Ähnliche Issues

Weitere Issues zu C++

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.