Add WinGet

[NatoBoram]

• Have you signed the Contributor License Agreement?
• Have you checked that there aren't other open pull requests for the same manifest update/change?
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• Does your manifest conform to the 1.0 schema?

---

Any good package manager must at least be able to install itself ;)

cc ScoopInstaller/Extras#4107 microsoft/winget-cli#505 #825 #19425

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

This submission has moved to manual review.

[jos3s]

Valid manifest

[denelon]

Unfortunately, this suffers from lack of dependencies. We're working on a solution for VCLibs also related to the Sandbox PowerShell script #827 .

[NatoBoram]

Couldn't those problems just be solved afterwards? After all, one might already have the necessary dependencies, otherwise an error message can be equally helpful, and it's normal for a fairly new installer-executor to not have dependency awareness at first. And now that I think about it, anyone trying to install WinGet via WinGet probably have most dependencies already.

[KevinLaMS]

Deployment wants to shut down old winget to deploy new winget, deployment sends the old winget a ctrl-c signal, the old winget cancels all it’s doing(including the ongoing “install new winget”).

[denelon]

microsoft/winget-cli#505

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @NatoBoram,
The package manager bot determined that the metadata was not compliant.

Please verify the manifest file is compliant with the package manager 1.0 manifest specification.
Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.
Note: The path and "PackageIdentifier" are case sensitive.
Be sure to use a tool like VSCode (https://code.visualstudio.com/) to make sure the manifest YAML syntax is correct.

You could also try our Windows Package Manager Manifest Creator Preview.

For details on the specific error, see the details link below in the build pipeline.

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[NatoBoram]

Unfortunately, this suffers from lack of dependencies. We're working on a solution for VCLibs also related to the Sandbox PowerShell script #827.

Hold on a second, I remember installing from github.com/microsoft/winget-cli/releases on brand new instances of Windows 10 like last week without missing any dependencies. Are the dependencies in newer builds of Windows?

[ghost]

Hello @NatoBoram,
The package manager bot determined there was an issue with installing the application correctly. Please check the application installs correctly. Once repaired, please push an update to your pull request.

[denelon]

I think we're still blocked on the fact that the install cancels our active installation. We're looking at a delayed registration via MSIX which would unblock this one. I hope we get to that soon 😊

[ItzLevvie]

cc @denelon: could you please add the "Blocking-Issue" label on this PR?

[denelon]

Just an "FYI" here. It's now possible to winget install "App Installer" with the connectivity to the "msstore" source. One of the things the Microsoft Store does is handle some of the dependencies related to MSIX packages in the store. We've been talking about the fact that the Windows Package Manager dependencies "must" have been available in order to run winget upgrade winget in the first place. The bigger challenge here is that the package is actually the "App Installer" package. We could use winget as the moniker though.

[ItzLevvie]

Close with reason: Replaced by PR 56841;

[NatoBoram]

Here's a link to it for mobile users:

• Microsoft.DesktopAppInstaller version 1.17.10271.0 #56841