Process column shows <system> vs. process name - when running process escalated

[MarkGoldberg]

When I run my program from an administrator cmd prompt the process name shows < system >
(without the spaces)
When I run the same program from a non administrator cmd prompt, it shows the correct name
(also seen when debugging from VS.2015)

This issue also has an impact on filtering by process name

This issue confirmed to still be present in the latest and greatest (version 1.8.05)
I'm not certain, but I might've first noticed the issue in 1.7.0.88
tested on Win10 Creators Update

[janwilmans]

For debugview++ (or any program) to have acces to **system** process info, it needs to run as an administrator. could you try starting debugview by right clicking it and choose run as admin? note that in the shortcut properties you can also make this the default.

[janwilmans]

while I'm sure that would work
it still seems to me that there must be a way to get process name without being escalated
Notice how tasklist can show the names of escalated processes even when it is not escalated itself.

Hm, good point, I never gave that a second thought, will investigate it.

[janwilmans]

Turns out the taskbar.exe process does run as an Elavated process, the 'User name' that started it, is not a good indicator of whether the process is running Elavated or not...

[janwilmans]

it turns out the processname of elevated processes can be queried using PROCESS_QUERY_LIMITED_INFORMATION instead of PROCESS_QUERY_INFORMATION and that requires less privilegedes to use. I have send you a test version.

[janwilmans]

verified...closing