Is there a proper way to change from Microsoft Store WinGet to GitHub releases?

[Infinitay]

I believe I had installed WinGet either manually or thru Windows 10 itself as a part of the App Installer app found on the Microsoft Store. According to UniGetUI

Package Name: Windows Package Manager Source (winget) v2
Package ID: MSIX\Microsoft.Winget.Source_2025.915.2128.16_neutral_8wekyb3d8bbwe
Version: 2025.915.2128.16
Source: Microsoft Store

I would like to change from the MSFT Store version to instead use the releases found here (particularly latest builds/commits). Is there a proper way to do so without breaking anything such as configuration or existing package installs, or causing conflicts in someway such as two existing versions of WinGet?

Also, I read the article shared by Microsoft on WinGet and they say you can do so either by downloading the release builds (what I want to do), joining the Windows Insider program, or join the Windows Package Manager Insiders Program - however that link is invalid when I tried.

[florelis]

The packages in the Microsoft Store and GitHub releases are the same. You can upgrade to a package from GitHub at any time; and even if you install from GitHub you will continue to receive updates from the Store.

The easiest way to install a release from GitHub is with the Repair-WinGetPackageManager cmdlet from the Microsoft.WinGet.Client module. You can select whether to install a preview or a stable build.

To receive preview builds automatically from the Store, you can join the Windows Insiders program in the Canary or Dev channels.

@denelon is there a new link to join the winget Insiders program?

[denelon]

No, the WinGet insiders program has been decommissioned. It was originally designed to help us get enough use on preview builds. We're getting plenty of coverage coming from the Windows Insiders builds.

I'd suggest putting a 👍 on:

• Support different release channels [released, beta, alpha] #147

[Infinitay]

The packages in the Microsoft Store and GitHub releases are the same. You can upgrade to a package from GitHub at any time; and even if you install from GitHub you will continue to receive updates from the Store.

The easiest way to install a release from GitHub is with the Repair-WinGetPackageManager cmdlet from the Microsoft.WinGet.Client module. You can select whether to install a preview or a stable build.

Thank you for the reply! Pardon the ignorance, I didn't realize the releases was an actual installer. This makes this much more simpler. Appreciate the help and the command. I'll go ahead and get Microsoft.WinGet.Client to keep thing simple.

EDIT: I got around to updating it just now successfully via the following: Repair-WinGetPackageManager -Force -IncludePrerelease

No, the WinGet insiders program has been decommissioned. It was originally designed to help us get enough use on preview builds. We're getting plenty of coverage coming from the Windows Insiders builds.

I'd suggest putting a 👍 on:

• Support different release channels [released, beta, alpha] #147

I did so. thanks for letting me know. Multiple versions would be amazing for many reasons. Personally, so I wouldn't have to wait for fixes for issues I deal with such as waiting for 9ac99d2 to make it to preview or stable release. I hope the team reconsiders that request some time in the future, but it already being 5 years sounds rough.

[denelon]

Yeah, building a package manager for Windows is an order of magnitude harder than for Linux where "everything is just a file". It's a constellation of services for us to keep everything running smoothly, and there are lots of competing demands. I do have channels on the roadmap. Once we get WinGet 1.12 out, I'll move that issue to the WinGet Project for tracking.

[Infinitay]

Oh of course. Pardon any tone that sounding demanding or of the sort.

[denelon]

No worries. 😊
I default to assuming folks mean well.

[Infinitay]

For anyone coming to this in the future, I realized that despite running with -Force and IncludePrerelease it was always saying WinGet is in a good state, yet there was a new latest pre-release. However, it was using what I assume to be the latest non-pre-release (to be honest I did this all ~30 minutes ago and I forgot the exact version). However, I was able to manual specify the pre-release version to update to via the following command: Repair-WinGetPackageManager -Version 1.12.250-preview -Force -Verbose. To find the version via Releases tab and copy the tag you want to install.