Davyd McColl

I am on a domain, but our devops people tend not to enforce arbitrary constraints on the users. If they did, it's odd that I can launch the installer manually,...

I've been through this stuff, so unless the "custom level" UI is lying to me, this is not the droid I'm seeking (mine is set to "confirm" for unknown sources)....

somehow, this is not affecting me any more; `winget` now "just works" (mostly). I'm not at all sure what changed.

aaand... it's back, trying to `winget upgrade --all` and failing on the gvim installer that it got from github. I've reset all security zones, I've tried elevating, nothing. I'll have...

yup, tracked it down within the %LOCALAPPDATA%\Temp\Winget folder, and the installer works just fine :|

whilst I get that this issue (probably) isn't directly winget's fault, it's really annoying; something that would make it slightly less-so would be if winget printed out the full path...

Another thought I've had is perhaps it's related to install type? VIM has a .exe installer, so does Discord (that I had issues with). OTOH, so does the Humble Bundle...

I think that the location of the downloaded artifact may be the problem - changing the environment variable `TMP` to point at another temp location (`C:\tmp`), I could install things...

It's not a permissions issue, since I could run the installer manually. This was so long ago and, iirc, on a different machine. I don't have the issue now, so...

I agree - something marked `[Obsolete]` can go, something that still works, even if it's only for a few users, can stay. And we should be very judicial about deprecations...