Allow Winget to run as another user, or at least disable UAC

[overtech-nc]

Description of the new feature / enhancement

We are using a RMM tool and want to run a periodic script that would launch winget on workstations, but we can't find a way to make it work like we need to.

If we run it with the logged-on user credentials, UAC will pop up each time an app wants to upgrade, even with the -h or --silent option (I'm assuming it has nothing to do with the UAC prompt then, but more with the actual program window)

If we try to run it with other admin credentials, it will say that the winget command is not recognized (even if it actually works if we log into that particular account).

Having winget run on another admin account (without any prompt appearing on the screen) would be perfect, as it would allow us to upgrade apps easily even on workstations on which users are using a standard account, without disturbing them.

Is there already a way of doing this that we are not aware of ?

Thank a lot !

Proposed technical implementation details

No response

[jedieaston]

If we try to run it with other admin credentials, it will say that the winget command is not recognized (even if it actually works if we log into that particular account).

This is most likely related to #1474, I'm not sure what the ongoing status is of that issue (besides that it isn't fixed).

[o-l-a-v]

You could run it as SYSTEM though, right?

Examples running from Intune:

• https://github.com/o-l-a-v/winget-intune-win32

[overtech-nc]

You could run it as SYSTEM though, right?

Examples running from Intune:

• https://github.com/o-l-a-v/winget-intune-win32

Sadly not, it gives me that kind of error : "Program 'winget.exe' failed to run: The file cannot be accessed by the system.At line..."

Thank you very much for your link, I will have a look :)

[jedieaston]

I think Intune copies the script and runs it locally vs opening a remote shell and putting commands in, like PsExec or other RMM tools do. That will cause different behavior in this instance due to the AEA issue.

[o-l-a-v]

Sadly not, it gives me that kind of error : "Program 'winget.exe' failed to run: The file cannot be accessed by the system.At line..."

Thank you very much for your link, I will have a look :)

Well, you don't run "winget" from system context, but AppInstallerCli.exe. I still think it's possible from an RMM.

#962 (comment)

[jedieaston]

Oh, yes, that works. AppInstallerCLI.exe is a real executable as opposed to a funny one.

[overtech-nc]

I also tried with AppInstallerCLI.exe and got the same error.

In the end, we will use PatchMyPC, which works correctly in all cases and doesn't even require to be installed!

[dreaddr]

Still using PatchMyPC here as well, as this is not properly implemented here. Would be very convenient if it was possible with winget though.

[denelon]

#2338 (comment)