Re: Windows Process Executable Path is Null

I think you want the PathName property.

PathName

Fully qualified path to the executable file responsible for implementing the service.

When in doubt, mumble; when in trouble, delegate; when in charge, ponder. -- James H. Boren

Comment on Re: Windows Process Executable Path is Null

Replies are listed 'Best First'.
Re^2: Windows Process Executable Path is Null by dt667 (Acolyte) on Oct 28, 2013 at 17:58 UTC
Both ExecutablePath and PathName return null for the smss.exe process	[reply]
Re^3: Windows Process Executable Path is Null by Anonymous Monk on Oct 29, 2013 at 00:57 UTC
Both ExecutablePath and PathName return null for the smss.exe process Need to read more on MSDN -- getting info on some procs requires elevated privileges/permissions/runningasadmin ... you can see with http://live.sysinternals.com/procexp.exe	[reply]