winget update shows different results if run locally vs remotely

[dteusner]

Relevant area(s)

WinGet CLI

Relevant command(s)

locally

winget update --source winget

remotely

Invoke-Command -ComputerName "SOME_SERVER_NAME" -ScriptBlock { winget update --source winget }

Brief description of your issue

Via Powershell the command "winget update" shows different results when run locally on a server as to run via "invok-command"

Steps to reproduce

Running "winget update" directly on a server shows the following options:

While running the same command via invoke command, gives these results:

The update for "MS Teams" is missing

Expected behavior

Both ways should produce the same results

Actual behavior

Different ways different results

Environment

PS C:\Windows\System32> winget -v
v1.28.190

PS C:\Windows\System32> winget --info
WindowsPackageManager
MainCopyrightNotice

Windows: Windows.Server v10.0.17763.8511
SystemArchitecture

KeyDirectoriesHeader
----------------------------------------------------------------------------------------
Logs                 %TEMP%\WinGet\defaultState
UserSettings         %LOCALAPPDATA%\Microsoft\WinGet\Settings\defaultState\settings.json
PortableLinksUser    %LOCALAPPDATA%\Microsoft\WinGet\Links
PortableLinksMachine C:\Program Files\WinGet\Links
PortableRootUser     %LOCALAPPDATA%\Microsoft\WinGet\Packages
PortableRoot         C:\Program Files\WinGet\Packages
PortableRoot86       C:\Program Files (x86)\WinGet\Packages
InstallerDownloads   %USERPROFILE%\Downloads
ConfigurationModules %LOCALAPPDATA%\Microsoft\WinGet\Configuration\Modules

Links
--------------------------------------------------------------------------------
PrivacyStatement         https://aka.ms/winget-privacy
LicenseAgreement         https://aka.ms/winget-license
ThirdPartSoftwareNotices https://aka.ms/winget-3rdPartyNotice
MainHomepage             https://aka.ms/winget
WindowsStoreTerms        https://www.microsoft.com/en-us/storedocs/terms-of-sale

AdminSettingHeader                        StateHeader
-------------------------------------------------------
LocalManifestFiles                        StateDisabled
BypassCertificatePinningForMicrosoftStore StateDisabled
InstallerHashOverride                     StateDisabled
LocalArchiveMalwareScanOverride           StateDisabled
ProxyCommandLineOptions                   StateDisabled
DefaultProxy                              StateDisabled

[denelon]

Is the "Teams" instance Win32 installed or MSIX installed?
Is the logged in user the same in both cases (running locally and calling in remotely)?

There are subtle distinctions between how Win32 applications get installed "machine-wide" vs. "per user", and how MSIX packaged applications get registered and provisioned.

[dteusner]

@denelon

Is the "Teams" instance Win32 installed or MSIX installed?

It is MSIX installed

Is the logged in user the same in both cases (running locally and calling in remotely)?

No, they are two different users. For the local check I use my admin account, for the remote check I use a special service account, which cannot log on to the server via RDP directly, but run scripts via remote Powershell.

[denelon]

WinGet "runs" as the logged in user with respect to how packages get detected as installed. Session 0 / System Context / NTAuthority are "special" cases where your mileage will vary based on the installer type and the installer scope. In those cases, MSIX packages may not be both provisioned and registered for that "account".

[dteusner]

HI denelon,

thanks for the reply and the explanation. I will have a closer look at this.

Yours David