CODEWITHSUNDEEP
uwp
trungnt2910
trungnt2910

Reputation: 352

How to get the UWP package associated with an UWP process?

Process Explorer seems to have a magical way of determining which package a UWP process belongs to:enter image description here

enter image description here

Somehow, both process have identical names (RuntimeBroker.exe), starts from an identical path (C:\Windows\System32), and are passed identical, meaningless command arguments (-Embedding).

The other processes are passed some ServerName argument as a hint, but the RuntimeBrokers are not.

So my question is: How can we know which package started the RuntimeBrokers, like what Process Explorer did?

Upvotes: 0

Views: 573

Answers (2)

trungnt2910
trungnt2910

Reputation: 352

The magic is right here, at home: Magic

Simply use tasklist /apps and every UWP-related thing will be shown.

P.S. Confirmed only on Windows 10 20H2. I don't know for how long has this feature been available.

Upvotes: 0

Nico Zhu
Nico Zhu

Reputation: 32785

How can we know which package started the RuntimeBrokers, like what Process Explorer did?

I'm afraid you can't detect if the packaged app contains RuntimeBrokers, and currently, UWP Diagnostics API only could get limit process info such as CpuUsage, and here is code sample that you could test with.

The Runtime Broker application is a Microsoft program included with Windows 8 (and newer versions) that handles permissions for all local Universal Windows Platform (UWP) applications.

The purpose of Runtime Broker is to monitor and manage all permissions granted to running UWP applications. If you’ve ever opened the Windows Store, or launched any UWP application from a built-in start menu “tile” or open FileOpenPicker chances are this application has used the Runtime Broker to verify its proper permissions and Capabilities.

And it is system leave, if you do want to check it when app running, we suggest you make desktop extension for uwp app, and load info with Win32 API.

Upvotes: 1

Related Questions