WinGet install fails without elevation about winobjex64

[sharpjs]

@w3lld0ne: I discovered it. I have WinGet configured to prefer per-machine installs. When I change that to per-user, WinGet installs WinObjEx64 from a non-elevated terminal without error.

I think this is bug/gotcha in WinGet's install-from-ZIP support: WinGet would need to self-elevate to create the machine-scope install directory in $env:ProgramFiles\WinGet\Packages, but it does not. This is plausible, as for MSI- and EXE- based installs, the installer does the elevation, not WinGet. The appropriate place for me to report this, then, is microsoft/winget-cli, not here. Apologies for the false alarm and wasted time.

For reference, my WinGet configuration includes:

{
    "installBehavior": {
        "preferences": {
            "scope": "machine" <-- what caused the problem
        }
    }
}

[hfiref0x]

WinObjEx64 doesn't require elevation to start. Show properties of this file please.

[sharpjs]

@hfiref0x: WinObjEx64 does not fail. The WinGet install is what fails.

[hfiref0x]

I've never produced any winget installs for this program and have no idea who did that. Guess this is not my fault.

[sharpjs]

Fair enough. Yeah, looking at the manifests, it was @w3lld0ne, not you. I'll close this and see if there's any way to raise the issue with @w3lld0ne or just submit a PR for it myself. Sorry for the bother.

[w3lld0ne]

@sharpjs this seems like not an issue with the package (it installs perfectly fine for me on clean VM from unelevated terminal), but with your WinGet instance or smth.