Running this executable directly works just fine under SYSTEM. In my script, I check for both WinGet.exe and AppInstallerCLI.exe The executable is found under C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller_1.0_圆4_8wekyb3d8bbweĮDIT: As of writing this, it seems for the latest version of WinGet, WinGet.exe is now located in the DesktopAppInstaller folder, AppInstallerCLI.exe is no longer here. There was a crafty user on Github however that found that WinGet.exe is a proxy application for “AppInstallerCLI.exe” which can be ran as system. There is an open issue on GitHub currently and many admins, myself included, would really like WinGet to be designed with enterprise use in mind.
It was designed to be run under a user account. After doing some research and testing, I found that WinGet was unfortunately not designed to be run in SYSTEM context.
Ever since the WinGet package manager was announced, I wanted to find ways to leverage the package manager to simplify deploying software to endpoints.
0 kommentar(er)
