Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.microsoft.windows > #3580 > unrolled thread
| Started by | Maria Sophia <mariasophia@comprehension.com> |
|---|---|
| First post | 2026-10-12 02:17 -0700 |
| Last post | 2026-10-12 15:43 -0400 |
| Articles | 4 — 4 participants |
Back to article view | Back to alt.comp.microsoft.windows
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: How can we get an ACCURATE list of unique programs installed on WIndows? Maria Sophia <mariasophia@comprehension.com> - 2026-10-12 02:17 -0700
Re: How can we get an ACCURATE list of unique programs installed on WIndows? Andy Burns <usenet@andyburns.uk> - 2026-10-12 11:54 +0100
Re: How can we get an ACCURATE list of unique programs installed on WIndows? Paul <nospam@needed.invalid> - 2026-10-12 07:33 -0400
Re: How can we get an ACCURATE list of unique programs installed on WIndows? Zaidy036 <Zaidy036@air.isp.spam> - 2026-10-12 15:43 -0400
| From | Maria Sophia <mariasophia@comprehension.com> |
|---|---|
| Date | 2026-10-12 02:17 -0700 |
| Subject | Re: How can we get an ACCURATE list of unique programs installed on WIndows? |
| Message-ID | <11ai8ir$22eq$1@nnrp.usenet.blueworldhosting.com> |
Andy Burns wrote:
> get-wingetPackage -name windowsAppRuntime
This is a good discussion because "accurate" is a primary operative.
And "installed" apps is the second main operative in this discussion.
Apparently, the output from Get-WinGetPackage lists the Windows App
Runtime packages that are currently installed on the computer.
PS> get-wingetPackage -name windowsAppRuntime
get-wingetPackage : The term 'get-wingetPackage' is not recognized
as the name of a cmdlet, function, script file, or operable program.
PS> Install-Module -Name Microsoft.WinGet.Client -Force -AllowClobber
PS> get-wingetPackage -name windowsAppRuntime
Name Id Version Available Source
Windows App Runtime Microsoft.WindowsAppRuntime.1.3 1.3.3 winget
Windows App Runtime 1.5 Microsoft.WindowsAppRuntime.1.5 1.5.9 winget
Windows App Runtime 1.6 Microsoft.WindowsAppRuntime.1.6 1.6.9 winget
Windows App Runtime 1.7 Microsoft.WindowsAppRuntime.1.7 1.7.4 1.7.9 winget
Windows App Runtime 1.8 Microsoft.WindowsAppRuntime.1.8 > 1.... winget
Apparently, winget search "Windows App Runtime" queries the online
repository (the global store), showing every version of the runtime
that is available to download from Microsoft.
PS> winget search "Windows App Runtime"
Name Id Version Source
----------------------------------------------------------------------
Windows App Runtime Microsoft.WindowsAppRuntime.1.3 1.3.3 winget
Windows App Runtime Microsoft.WindowsAppRuntime.1.4 1.4.7 winget
Windows App Runtime 1.5 Microsoft.WindowsAppRuntime.1.5 1.5.9 winget
Windows App Runtime 1.6 Microsoft.WindowsAppRuntime.1.6 1.6.9 winget
Windows App Runtime 1.7 Microsoft.WindowsAppRuntime.1.7 1.7.9 winget
Windows App Runtime 1.8 Microsoft.WindowsAppRuntime.1.8 1.8.10 winget
Windows App Runtime 2.0 Microsoft.WindowsAppRuntime.2 2.4.0 winget
Windows App Runtime 2.0 Microsoft.WindowsAppRuntime.2.0 2.0.1 winget
PS> winget install Microsoft.WindowsAppRuntime.1.6
Found an existing package already installed.
Trying to upgrade the installed package...
No available upgrade found.
No newer package versions are available from the configured sources.
Are your results similar?
[toc] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2026-10-12 11:54 +0100 |
| Message-ID | <nj3sjiF8psvU1@mid.individual.net> |
| In reply to | #3580 |
Maria Sophia wrote: > > Apparently, winget search "Windows App Runtime" queries the online > repository (the global store), showing every version of the runtime > that is available to download from Microsoft. > > PS> winget search "Windows App Runtime" > Name Id Version Source > ---------------------------------------------------------------------- > Windows App Runtime Microsoft.WindowsAppRuntime.1.3 1.3.3 winget > Windows App Runtime Microsoft.WindowsAppRuntime.1.4 1.4.7 winget > Windows App Runtime 1.5 Microsoft.WindowsAppRuntime.1.5 1.5.9 winget > Windows App Runtime 1.6 Microsoft.WindowsAppRuntime.1.6 1.6.9 winget > Windows App Runtime 1.7 Microsoft.WindowsAppRuntime.1.7 1.7.9 winget > Windows App Runtime 1.8 Microsoft.WindowsAppRuntime.1.8 1.8.10 winget > Windows App Runtime 2.0 Microsoft.WindowsAppRuntime.2 2.4.0 winget > Windows App Runtime 2.0 Microsoft.WindowsAppRuntime.2.0 2.0.1 winget > > PS> winget install Microsoft.WindowsAppRuntime.1.6 > Found an existing package already installed. > Trying to upgrade the installed package... > No available upgrade found. > No newer package versions are available from the configured sources. > > Are your results similar? similar but not identical Sticking with the 'pure' powershell cmdlet way, rather then spawning out to winget.exe find-wingetPackage -id "microsoft.windowsAppRuntime" Name Id Version Source ---- -- ------- ------ Windows App SDK Microsoft.WindowsAppRuntime.1.0 1.0.4 winget Windows App SDK Microsoft.WindowsAppRuntime.1.1 1.1.5 winget Windows App SDK Microsoft.WindowsAppRuntime.1.2 1.2.5 winget Windows App Runtime Microsoft.WindowsAppRuntime.1.3 1.3.3 winget Windows App Runtime Microsoft.WindowsAppRuntime.1.4 1.4.7 winget Windows App Runtime 1.5 Microsoft.WindowsAppRuntime.1.5 1.5.9 winget Windows App Runtime 1.6 Microsoft.WindowsAppRuntime.1.6 1.6.9 winget Windows App Runtime 1.7 Microsoft.WindowsAppRuntime.1.7 1.7.9 winget Windows App Runtime 1.8 Microsoft.WindowsAppRuntime.1.8 1.8.10 winget Windows App Runtime 2.0 Microsoft.WindowsAppRuntime.2 2.4.0 winget Windows App Runtime 2.0 Microsoft.WindowsAppRuntime.2.0 2.0.1 winget but calling winget.exe winget search "Windows App Runtime" Name Id Version Source ----------------------------------------------------------------------- Windows App Runtime Microsoft.WindowsAppRuntime.1.3 1.3.3 winget Windows App Runtime Microsoft.WindowsAppRuntime.1.4 1.4.7 winget Windows App Runtime 1.5 Microsoft.WindowsAppRuntime.1.5 1.5.9 winget Windows App Runtime 1.6 Microsoft.WindowsAppRuntime.1.6 1.6.9 winget Windows App Runtime 1.7 Microsoft.WindowsAppRuntime.1.7 1.7.9 winget Windows App Runtime 1.8 Microsoft.WindowsAppRuntime.1.8 1.8.10 winget Windows App Runtime 2.0 Microsoft.WindowsAppRuntime.2 2.4.0 winget Windows App Runtime 2.0 Microsoft.WindowsAppRuntime.2.0 2.0.1 winget Are you on win10 or win11 ?
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2026-10-12 07:33 -0400 |
| Message-ID | <11aigi0$3hj5f$1@dont-email.me> |
| In reply to | #3580 |
On Mon, 10/12/2026 5:17 AM, Maria Sophia wrote:
> Andy Burns wrote:
>> get-wingetPackage -name windowsAppRuntime
>
> This is a good discussion because "accurate" is a primary operative.
> And "installed" apps is the second main operative in this discussion.
>
> Apparently, the output from Get-WinGetPackage lists the Windows App
> Runtime packages that are currently installed on the computer.
>
>
> PS> get-wingetPackage -name windowsAppRuntime
> get-wingetPackage : The term 'get-wingetPackage' is not recognized
> as the name of a cmdlet, function, script file, or operable program.
>
> PS> Install-Module -Name Microsoft.WinGet.Client -Force -AllowClobber
>
> PS> get-wingetPackage -name windowsAppRuntime
> Name Id Version Available Source
> Windows App Runtime Microsoft.WindowsAppRuntime.1.3 1.3.3 winget
> Windows App Runtime 1.5 Microsoft.WindowsAppRuntime.1.5 1.5.9 winget
> Windows App Runtime 1.6 Microsoft.WindowsAppRuntime.1.6 1.6.9 winget
> Windows App Runtime 1.7 Microsoft.WindowsAppRuntime.1.7 1.7.4 1.7.9 winget
> Windows App Runtime 1.8 Microsoft.WindowsAppRuntime.1.8 > 1.... winget
>
> Apparently, winget search "Windows App Runtime" queries the online
> repository (the global store), showing every version of the runtime
> that is available to download from Microsoft.
>
> PS> winget search "Windows App Runtime"
> Name Id Version Source
> ----------------------------------------------------------------------
> Windows App Runtime Microsoft.WindowsAppRuntime.1.3 1.3.3 winget
> Windows App Runtime Microsoft.WindowsAppRuntime.1.4 1.4.7 winget
> Windows App Runtime 1.5 Microsoft.WindowsAppRuntime.1.5 1.5.9 winget
> Windows App Runtime 1.6 Microsoft.WindowsAppRuntime.1.6 1.6.9 winget
> Windows App Runtime 1.7 Microsoft.WindowsAppRuntime.1.7 1.7.9 winget
> Windows App Runtime 1.8 Microsoft.WindowsAppRuntime.1.8 1.8.10 winget
> Windows App Runtime 2.0 Microsoft.WindowsAppRuntime.2 2.4.0 winget
> Windows App Runtime 2.0 Microsoft.WindowsAppRuntime.2.0 2.0.1 winget
>
> PS> winget install Microsoft.WindowsAppRuntime.1.6
> Found an existing package already installed.
> Trying to upgrade the installed package...
> No available upgrade found.
> No newer package versions are available from the configured sources.
>
> Are your results similar?
>
Large vats of hot soup to pour on the peasants. A lot of these
files are localization related (en-us or whatever).
grep WindowsAppRuntime nfi-c-out.txt | wc -l
8534
C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.8_8000.921.1539.0_x64__8wekyb3d8bbwe\NpuDetect\NPUDetect.dll
C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.1.8_8000.921.1539.0_x64__8wekyb3d8bbwe\Microsoft.Windows.AI.ContentModerationInternal.winmd
C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.2_2.5.1.0_x64__8wekyb3d8bbwe\Microsoft.Windows.AI.MachineLearning.dll
C:\Program Files\WindowsApps\Microsoft.WindowsAppRuntime.2_2.5.1.0_x64__8wekyb3d8bbwe\Microsoft.Windows.AI.Video.dll
C:\Program Files\WindowsApps\Microsoft.ScreenSketch_11.2608.41.0_x64__8wekyb3d8bbwe\SnippingTool\onnxruntime.dll
C:\Windows\SystemApps\Microsoft.WindowsAppRuntime.CBS.2_8wekyb3d8bbwe\Microsoft.UI.Xaml.Phone.dll
You would think WinSxS would be a large enough vat, for all occasions.
Whereas these vats are updated on a relatively high frequency basis
via Reliability Monitor citation. Maybe we could think of the WinSxS
as the "low frequency" "Patch Tuesday" vat, and whatever this purpose
serves, is the "high frequency" "stealth" vat. My reliability info
has scrolled off, since I did a Repair Install, so I cannot give
an example of a WindowsAppRuntime set of installs.
I think the NPUDetect routine is going to be somewhat disappointed on my machine :-)
My machine is more DialupNetworking and LongWalksOnTheBeach material.
You would think there would be Detect routines for those.
I guess I just have no interest in boatloads of INT8 multiplies.
"Riders On The Storm"
https://www.youtube.com/watch?v=7G2-FPlvY58
Paul
[toc] | [prev] | [next] | [standalone]
| From | Zaidy036 <Zaidy036@air.isp.spam> |
|---|---|
| Date | 2026-10-12 15:43 -0400 |
| Message-ID | <11ajd8v$3u7c9$1@dont-email.me> |
| In reply to | #3580 |
<snip> try the free for personal use Belarc Advisor
[toc] | [prev] | [standalone]
Back to top | Article view | alt.comp.microsoft.windows
csiph-web