-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PT Run] [WindowWalker] Process ID is zero for win32 apps #15326
Comments
@davidegiacometti |
Not sure. Does it happen with programs that aren't running elevated? |
every one. I don't understand why it's gone and only for win32. It seems that we instantiate the windows on every query but keep the window cache as static class variable. Maybe we should look when the windows gets instanced and maybe we should rework the entire class. I don't like the fix I have added. It feels a bit ugly. |
@davidegiacometti |
@davidegiacometti |
@crutkas |
@htcfreek done |
The was fixed in in 0.55. Head over to https://aka.ms/installpowertoys to try it out |
Microsoft PowerToys version
0.53.1
Running as admin
Area(s) with issue?
PowerToys Run
Steps to reproduce
While working on the code for #6084 I detected that the process ID of the detected windows is incorrect/zero. It only happens on non-packaged apps.
Note: I use the
NativeMethods.cs
from PR #15186.✔️ Expected Behavior
Correct PID.
❌ Actual Behavior
It is incorrect for non-packaged apps:
![image](https://user-images.githubusercontent.com/61519853/148567717-c4cbbaa4-408e-4f37-b1b0-1453ede30656.png)
It is correct for packaged apps and the process that is shown for it:
![image](https://user-images.githubusercontent.com/61519853/148567648-5f603bc8-3439-4779-b735-bb9aac2bc8d6.png)
Other Software
No response
The text was updated successfully, but these errors were encountered: