Provision WinGet

[ElliotKillick]

WinGet is the new package manager from Microsoft. In the long-term we want it to replace Chocolatey (there's hope for this even going as far back as Windows 7 due to MSIX Core). This will have numerous advantages one of which is security (one less third-party to trust), package installation behind Tor, and a few other issues I've had with Chocolatey.

I have a branch working on adding this but I want the dust to settle more on the Winget side of things before I implement it (see linked issues): master...feat-winget

In the interim, I recommend just opening the Microsoft Store and updating App Installer. That will give you the WinGet command and then you can get any packages you want.

[ElliotKillick]

One other way (not mentioned in the branch) of getting WinGet programmatically would be to trigger a Microsoft Store update and then poll until the wingetcommand exists. Unfortunately, I can't immediately find a way to only update a single package from PowerShell, you have to update them all and you can't wait on it (hence the polling). Since App Installer start with an "A" though I'm pretty sure it would be one of the first packages installed (assuming it goes alphabetically; haven't tested) so it may actually work alright: https://social.technet.microsoft.com/Forums/windows/en-US/5ac7daa9-54e6-43c0-9746-293dcb8ef2ec/how-to-force-update-of-windows-store-apps-without-launching-the-store-app?forum=win10itprosetup

[ElliotKillick]

Microsoft official installation documentation: https://github.com/microsoft/winget-cli#installing-the-client

Note the message regarding Windows Server compatibility.