You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is somewhat similar to #1398. Using NtQuerySystemInformation instead of QueryFullProcessImageNameW may result in less AccessDenied exceptions for low pid processes.
The text was updated successfully, but these errors were encountered:
It turns out NtQuerySystemInformation retrieves the exe for all processes except PIDs 0 and 4. QueryFullProcessImageNameW on the other hand is much more limited (basically you get AccessDenied for any process not owned by your user).
Also, it's around 40 times faster!!
Right now in order to get the process exe() we use
QueryFullProcessImageNameW
(orGetProcessImageFileNameW
on Win XP), see #1394 (comment).It seems ProcessHacker uses
NtQuerySystemInformation
instead:https://github.com/processhacker/processhacker/blob/a39d0f312c863ccb1c4ed927bfcd8eedac1b5fd7/phlib/native.c#L4800
This is somewhat similar to #1398. Using
NtQuerySystemInformation
instead ofQueryFullProcessImageNameW
may result in less AccessDenied exceptions for low pid processes.The text was updated successfully, but these errors were encountered: