Get-WinGetPackage has different results for package query elevated vs non-elevated

Brief description of your issue

Both instances of my terminal can find the package when directly querying by ID. However, when just running Get-WinGetPackage and using filters like Where-Object, the results are different

Steps to reproduce

Expected behavior

If a package can be found in a non-elevated session, it should be found in an elevated session. I understand that if a package is found in an elevated session it might not be found in a non-elevated session due to permissions. The behavior here just seems weird

Actual behavior

See screenshot

Environment

PS C:\Users\kaleb> winget --info
Windows Package Manager v1.11.430
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.26100.4770
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.26.430.0

Winget Directories
-----------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bb…
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bb…
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       D:\kaleb\WinGet\Packages\
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads
Configuration Modules              %LOCALAPPDATA%\Microsoft\WinGet\Configuration\Modules

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Enabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled
ProxyCommandLineOptions                   Disabled
DefaultProxy                              Disabled
PS C:\Users\kaleb>

Start by reproducing the issue with Get-WinGetPackage in elevated and non-elevated PowerShell sessions, then compare the filtered results and the direct package-ID queries. The payload names no source file or test; done means the same package is discoverable consistently in the relevant sessions and regression coverage verifies the behavior.