GitHub Desktop doesn't appear to install correctly about winget-pkgs

[shiftkey]

@spencerwooo the machine-wide installer is based on the framework the team uses (Squirrel.Windows) and that probably explains the behaviour you're seeing:

Squirrel's Releasify command generates an MSI file suitable for installation via Group Policy. This MSI isn't a general-purpose installer, this means that once you run the MSI, users from now on will get the app installed, on next Login.

• Docs

This is because GitHub Desktop doesn't need admin rights to install, and everything it needs lives under %LOCALAPPDATA% and %APPDATA%.

I had a shot at alternatives a while ago, but didn't really get to a point where it could be switched over.

The Chocolatey approach here is to use the normal installer which may be different to what winget is willing to support.

[denelon]

microsoft/winget-cli#178

[shiftkey]

@denelon are there any logs or verbose commands that can run to see what winget is trying to do?

[spencerwooo]

I believe winget downloaded GitHub Desktop Machine-Wide installer and simply didn't execute it. I found the installer lying around inside "C:\Program Files (x86)\GitHub Desktop Installer\GitHubDesktop.exe"

[denelon]

@shiftkey there are logs. I'm working on a better solution to locate where they land. I'm looking to add the path to the --info command.

[denelon]

microsoft/winget-cli#390

[denelon]

The log location is now output via winget --info