Home Page https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer
Allan Higdon wrote:
Home Page
https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer
Tnx!
Remember:
"Originally, the Sysinternals website (formerly known as ntinternals was created in 1996 and was operated by the company Winternals Software LP,
which was located in Austin, Texas. It was started by software
developers Bryce Cogswell and Mark Russinovich. Microsoft acquired
Winternals and its assets on July 18, 2006."
Although Sysinternals stuff is good to have on hand, I also use other
stuff that can report the same info. There must have been a reason for
MS to acquire NTInternals, and when the company went over to the dark
side this way, it's possible that it began hiding certain specific information from end users. I'm not saying that this happened for sure,
only that it's possible.
John C. wrote:
Remember:
"Originally, the Sysinternals website (formerly known as ntinternals was
created in 1996 and was operated by the company Winternals Software LP,
which was located in Austin, Texas. It was started by software
developers Bryce Cogswell and Mark Russinovich. Microsoft acquired
Winternals and its assets on July 18, 2006."
I remember.
Although Sysinternals stuff is good to have on hand, I also use other
stuff that can report the same info. There must have been a reason for
MS to acquire NTInternals, and when the company went over to the dark
side this way, it's possible that it began hiding certain specific
information from end users. I'm not saying that this happened for sure,
only that it's possible.
It's a portable application and I don't have it running all the time.
System Explorer still runs on W11, so I have that.
"Microsoft Process Explorer quickly displays information about which handles and DLL processes have opened or loaded.
Its display consists primarily of two sub-windows; the top window will show a list of the currently active processes, including all names of their owning accounts. The bottom window's data depends on Process Explorer's mode. If in handle mode, you'll be able to view all handles that the process selected in the top window has opened; if Process Explorer is in DLL mode, then you can see the DLLs and memory-mapped files that the process has loaded.
Microsoft Process Explorer includes a powerful search capability for quickly displaying which processes have particular handles opened or DLLs loaded. All these capabilities ensure that it is perfect for tracking down DLL-version problems, handling leaks, and providing valuable insight into how Windows and applications perform."
https://www.majorgeeks.com/files/details/microsoft_process_explorer.html
Home Page https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer
Release Notes https://techcommunity.microsoft.com/blog/sysinternals-blog/zoomit-v9-20-process-explorer-v17-07-and-rdcman-v3-11/4469055
| Sysop: | KJ5EKH |
|---|---|
| Location: | Siloam Springs, Ar. |
| Users: | 10 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 75:53:08 |
| Calls: | 32 |
| Files: | 76,049 |
| Messages: | 59,603 |