I have been looking for a method for running #winget as #System (because many #RemoteMonitoringandManagement programs run scripts as System on endpoints) to update third party applications on computers. This is a commonly requested feature by #ITDepartments and there are a number of discussions surrounding the desire and potential issues related to changing how winget is packaged to allow it to run using the System account (https://github.com/microsoft/winget-cli/discussions?discussions_q=system+account).

After reading https://github.com/microsoft/winget-cli/issues/1861 and https://github.com/microsoft/winget-cli/discussions/962, I came up with a method to have winget run as System.

```$exeFilename = get-childitem -Path "C:\program files\windowsapps\" -filter winget.exe -Recurse | %{$_.FullName}
New-Alias -Name sysget -Value $exeFilename

sysget upgrade --all -e --accept-package-agreements --accept-source-agreements```

I have been looking for a method for running #winget as #System (because many #RemoteMonitoringandManagement programs run scripts as System on endpoints) to update third party applications on computers. This is a commonly requested feature by #ITDepartments and there are a number of discussions surrounding the desire and potential issues related to changing how winget is packaged to allow it to run using the System account (https://github.com/microsoft/winget-cli/discussions?discussions_q=system+account).

After reading https://github.com/microsoft/winget-cli/issues/1861 and https://github.com/microsoft/winget-cli/discussions/962, I came up with a method to have winget run as System.

$exeFilename = get-childitem -Path "C:\program files\windowsapps\" -filter winget.exe -Recurse | %{$_.FullName}
New-Alias -Name sysget -Value $exeFilename

sysget upgrade --all -e --accept-package-agreements --accept-source-agreements

I have been looking for a method for running #winget as #System (because many #RemoteMonitoringandManagement programs run scripts as System on endpoints) to update third party applications on computers. This is a commonly requested feature by #ITDepartments and there are a number of discussions surrounding the desire and potential issues related to changing how winget is packaged to allow it to run using the System account (https://github.com/microsoft/winget-cli/discussions?discussions_q=system+account).

After reading https://github.com/microsoft/winget-cli/issues/1861 and https://github.com/microsoft/winget-cli/discussions/962, I came up with a method to have winget run as System.

```
$exeFilename = get-childitem -Path "C:\program files\windowsapps\" -filter winget.exe -Recurse | %{$_.FullName}
New-Alias -Name sysget -Value $exeFilename

sysget upgrade --all -e --accept-package-agreements --accept-source-agreements```

I have been looking for a method for running #winget as #System (because many #RemoteMonitoringandManagement programs run scripts as System on endpoints) to update third party applications on computers. This is a commonly requested feature by #ITDepartments and there are a number of discussions surrounding the desire and potential issues related to changing how winget is packaged to allow it to run using the System account (https://github.com/microsoft/winget-cli/discussions?discussions_q=system+account).

After reading https://github.com/microsoft/winget-cli/issues/1861 and https://github.com/microsoft/winget-cli/discussions/962, I came up with a method to have winget run as System.

```
$exeFilename = get-childitem -Path "C:\program files\windowsapps\" -filter winget.exe -Recurse | %{$_.FullName}
New-Alias -Name sysget -Value $exeFilename

sysget upgrade --all -e --accept-package-agreements --accept-source-agreements```