Command line tools to view process list in Windows 10. pslist slow












0















Default Task Manager and Sysinternals ProcessExplorer are well-known GUI applications to show processes details in Windows 10. I use both.



Windows 10 comes also with command-line tasklist.exe.

It shows the processes list and but I can not make it show them in tree mode.

From here I tried with /SVC with no luck.



Just downloaded Sysinternals PsTools which come with pslist.exe & pslist64.exe.

This one seems to be that tool I want, since it can show all processes in tree mode.

It is like a command-line ProcessExplorer.



The only problems is that pslist takes a lot of time to show the results.

As a comparison, tasklist.exe takes less than 3 seconds to show all the processes.

Whereas pslist (both exes) take about 26 seconds, either showing or not as tree.



Why is pslist so slow?
Are there other alternatives?










share|improve this question























  • probably because it is gathering much more information. Maybe use the S switch?....Figure 5 on this page....docs.microsoft.com/en-us/previous-versions/technet-magazine/…

    – Moab
    Jan 24 at 14:05











  • I have never seen such delays: on my Win10 Pro system, pslist -t shows 220 processes - it runs in 770ms. I suggest you use other SysInternals utilities, such as ProcExp or ProcMon to find out what ps list is doing for such a long time.

    – AFH
    Jan 24 at 14:37











  • @Moab Switch -s seems like work as Unix top command, and does not really help here.

    – nephewtom
    Jan 24 at 15:09











  • @AFH I have run ProcMon, with a filter for pslist64.exe, but I do not know where to start... I can see a Process Start at 16:07:37.2231183, and IRP_MJ_CLOSE at 16:08:08.9720484. There are 10,876 events... I can see tons of RegOpenKey/QueryValue/CloseKey, but also many IRP_MJ_CREATE/CLEANUP/QUERY_SECURITY/CLOSE and FASTIO_ACQUIRE/RELEASE_FOR_SECTION_SYNCHRONIZATION/NETWORK_QUERY_OPEN/QUERY_INFORMATION... The information is overwhelming... BTW, mine shows 317 processes.

    – nephewtom
    Jan 24 at 15:16













  • I exported ProcMon info to a CSV file, and got a total of 10876 events with the following returned codes: TOTAL:10876, SUCCESS:7410, NAME NOT FOUND:2022, BUFFER, OVERFLOW:421, FILE LOCKED WITH ONLY READERS:396, FAST IO DISALLOWED:336, ACCESS DENIED:182 , NO MORE ENTRIES:46, REPARSE:38, PATH NOT FOUND:14, INVALID PARAMETER:5, IS DIRECTORY:4, BUFFER TOO SMALL:1, NAME INVALID:1

    – nephewtom
    Jan 24 at 15:45
















0















Default Task Manager and Sysinternals ProcessExplorer are well-known GUI applications to show processes details in Windows 10. I use both.



Windows 10 comes also with command-line tasklist.exe.

It shows the processes list and but I can not make it show them in tree mode.

From here I tried with /SVC with no luck.



Just downloaded Sysinternals PsTools which come with pslist.exe & pslist64.exe.

This one seems to be that tool I want, since it can show all processes in tree mode.

It is like a command-line ProcessExplorer.



The only problems is that pslist takes a lot of time to show the results.

As a comparison, tasklist.exe takes less than 3 seconds to show all the processes.

Whereas pslist (both exes) take about 26 seconds, either showing or not as tree.



Why is pslist so slow?
Are there other alternatives?










share|improve this question























  • probably because it is gathering much more information. Maybe use the S switch?....Figure 5 on this page....docs.microsoft.com/en-us/previous-versions/technet-magazine/…

    – Moab
    Jan 24 at 14:05











  • I have never seen such delays: on my Win10 Pro system, pslist -t shows 220 processes - it runs in 770ms. I suggest you use other SysInternals utilities, such as ProcExp or ProcMon to find out what ps list is doing for such a long time.

    – AFH
    Jan 24 at 14:37











  • @Moab Switch -s seems like work as Unix top command, and does not really help here.

    – nephewtom
    Jan 24 at 15:09











  • @AFH I have run ProcMon, with a filter for pslist64.exe, but I do not know where to start... I can see a Process Start at 16:07:37.2231183, and IRP_MJ_CLOSE at 16:08:08.9720484. There are 10,876 events... I can see tons of RegOpenKey/QueryValue/CloseKey, but also many IRP_MJ_CREATE/CLEANUP/QUERY_SECURITY/CLOSE and FASTIO_ACQUIRE/RELEASE_FOR_SECTION_SYNCHRONIZATION/NETWORK_QUERY_OPEN/QUERY_INFORMATION... The information is overwhelming... BTW, mine shows 317 processes.

    – nephewtom
    Jan 24 at 15:16













  • I exported ProcMon info to a CSV file, and got a total of 10876 events with the following returned codes: TOTAL:10876, SUCCESS:7410, NAME NOT FOUND:2022, BUFFER, OVERFLOW:421, FILE LOCKED WITH ONLY READERS:396, FAST IO DISALLOWED:336, ACCESS DENIED:182 , NO MORE ENTRIES:46, REPARSE:38, PATH NOT FOUND:14, INVALID PARAMETER:5, IS DIRECTORY:4, BUFFER TOO SMALL:1, NAME INVALID:1

    – nephewtom
    Jan 24 at 15:45














0












0








0








Default Task Manager and Sysinternals ProcessExplorer are well-known GUI applications to show processes details in Windows 10. I use both.



Windows 10 comes also with command-line tasklist.exe.

It shows the processes list and but I can not make it show them in tree mode.

From here I tried with /SVC with no luck.



Just downloaded Sysinternals PsTools which come with pslist.exe & pslist64.exe.

This one seems to be that tool I want, since it can show all processes in tree mode.

It is like a command-line ProcessExplorer.



The only problems is that pslist takes a lot of time to show the results.

As a comparison, tasklist.exe takes less than 3 seconds to show all the processes.

Whereas pslist (both exes) take about 26 seconds, either showing or not as tree.



Why is pslist so slow?
Are there other alternatives?










share|improve this question














Default Task Manager and Sysinternals ProcessExplorer are well-known GUI applications to show processes details in Windows 10. I use both.



Windows 10 comes also with command-line tasklist.exe.

It shows the processes list and but I can not make it show them in tree mode.

From here I tried with /SVC with no luck.



Just downloaded Sysinternals PsTools which come with pslist.exe & pslist64.exe.

This one seems to be that tool I want, since it can show all processes in tree mode.

It is like a command-line ProcessExplorer.



The only problems is that pslist takes a lot of time to show the results.

As a comparison, tasklist.exe takes less than 3 seconds to show all the processes.

Whereas pslist (both exes) take about 26 seconds, either showing or not as tree.



Why is pslist so slow?
Are there other alternatives?







windows-10 command-line process process-explorer






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 24 at 13:01









nephewtomnephewtom

1,1851811




1,1851811













  • probably because it is gathering much more information. Maybe use the S switch?....Figure 5 on this page....docs.microsoft.com/en-us/previous-versions/technet-magazine/…

    – Moab
    Jan 24 at 14:05











  • I have never seen such delays: on my Win10 Pro system, pslist -t shows 220 processes - it runs in 770ms. I suggest you use other SysInternals utilities, such as ProcExp or ProcMon to find out what ps list is doing for such a long time.

    – AFH
    Jan 24 at 14:37











  • @Moab Switch -s seems like work as Unix top command, and does not really help here.

    – nephewtom
    Jan 24 at 15:09











  • @AFH I have run ProcMon, with a filter for pslist64.exe, but I do not know where to start... I can see a Process Start at 16:07:37.2231183, and IRP_MJ_CLOSE at 16:08:08.9720484. There are 10,876 events... I can see tons of RegOpenKey/QueryValue/CloseKey, but also many IRP_MJ_CREATE/CLEANUP/QUERY_SECURITY/CLOSE and FASTIO_ACQUIRE/RELEASE_FOR_SECTION_SYNCHRONIZATION/NETWORK_QUERY_OPEN/QUERY_INFORMATION... The information is overwhelming... BTW, mine shows 317 processes.

    – nephewtom
    Jan 24 at 15:16













  • I exported ProcMon info to a CSV file, and got a total of 10876 events with the following returned codes: TOTAL:10876, SUCCESS:7410, NAME NOT FOUND:2022, BUFFER, OVERFLOW:421, FILE LOCKED WITH ONLY READERS:396, FAST IO DISALLOWED:336, ACCESS DENIED:182 , NO MORE ENTRIES:46, REPARSE:38, PATH NOT FOUND:14, INVALID PARAMETER:5, IS DIRECTORY:4, BUFFER TOO SMALL:1, NAME INVALID:1

    – nephewtom
    Jan 24 at 15:45



















  • probably because it is gathering much more information. Maybe use the S switch?....Figure 5 on this page....docs.microsoft.com/en-us/previous-versions/technet-magazine/…

    – Moab
    Jan 24 at 14:05











  • I have never seen such delays: on my Win10 Pro system, pslist -t shows 220 processes - it runs in 770ms. I suggest you use other SysInternals utilities, such as ProcExp or ProcMon to find out what ps list is doing for such a long time.

    – AFH
    Jan 24 at 14:37











  • @Moab Switch -s seems like work as Unix top command, and does not really help here.

    – nephewtom
    Jan 24 at 15:09











  • @AFH I have run ProcMon, with a filter for pslist64.exe, but I do not know where to start... I can see a Process Start at 16:07:37.2231183, and IRP_MJ_CLOSE at 16:08:08.9720484. There are 10,876 events... I can see tons of RegOpenKey/QueryValue/CloseKey, but also many IRP_MJ_CREATE/CLEANUP/QUERY_SECURITY/CLOSE and FASTIO_ACQUIRE/RELEASE_FOR_SECTION_SYNCHRONIZATION/NETWORK_QUERY_OPEN/QUERY_INFORMATION... The information is overwhelming... BTW, mine shows 317 processes.

    – nephewtom
    Jan 24 at 15:16













  • I exported ProcMon info to a CSV file, and got a total of 10876 events with the following returned codes: TOTAL:10876, SUCCESS:7410, NAME NOT FOUND:2022, BUFFER, OVERFLOW:421, FILE LOCKED WITH ONLY READERS:396, FAST IO DISALLOWED:336, ACCESS DENIED:182 , NO MORE ENTRIES:46, REPARSE:38, PATH NOT FOUND:14, INVALID PARAMETER:5, IS DIRECTORY:4, BUFFER TOO SMALL:1, NAME INVALID:1

    – nephewtom
    Jan 24 at 15:45

















probably because it is gathering much more information. Maybe use the S switch?....Figure 5 on this page....docs.microsoft.com/en-us/previous-versions/technet-magazine/…

– Moab
Jan 24 at 14:05





probably because it is gathering much more information. Maybe use the S switch?....Figure 5 on this page....docs.microsoft.com/en-us/previous-versions/technet-magazine/…

– Moab
Jan 24 at 14:05













I have never seen such delays: on my Win10 Pro system, pslist -t shows 220 processes - it runs in 770ms. I suggest you use other SysInternals utilities, such as ProcExp or ProcMon to find out what ps list is doing for such a long time.

– AFH
Jan 24 at 14:37





I have never seen such delays: on my Win10 Pro system, pslist -t shows 220 processes - it runs in 770ms. I suggest you use other SysInternals utilities, such as ProcExp or ProcMon to find out what ps list is doing for such a long time.

– AFH
Jan 24 at 14:37













@Moab Switch -s seems like work as Unix top command, and does not really help here.

– nephewtom
Jan 24 at 15:09





@Moab Switch -s seems like work as Unix top command, and does not really help here.

– nephewtom
Jan 24 at 15:09













@AFH I have run ProcMon, with a filter for pslist64.exe, but I do not know where to start... I can see a Process Start at 16:07:37.2231183, and IRP_MJ_CLOSE at 16:08:08.9720484. There are 10,876 events... I can see tons of RegOpenKey/QueryValue/CloseKey, but also many IRP_MJ_CREATE/CLEANUP/QUERY_SECURITY/CLOSE and FASTIO_ACQUIRE/RELEASE_FOR_SECTION_SYNCHRONIZATION/NETWORK_QUERY_OPEN/QUERY_INFORMATION... The information is overwhelming... BTW, mine shows 317 processes.

– nephewtom
Jan 24 at 15:16







@AFH I have run ProcMon, with a filter for pslist64.exe, but I do not know where to start... I can see a Process Start at 16:07:37.2231183, and IRP_MJ_CLOSE at 16:08:08.9720484. There are 10,876 events... I can see tons of RegOpenKey/QueryValue/CloseKey, but also many IRP_MJ_CREATE/CLEANUP/QUERY_SECURITY/CLOSE and FASTIO_ACQUIRE/RELEASE_FOR_SECTION_SYNCHRONIZATION/NETWORK_QUERY_OPEN/QUERY_INFORMATION... The information is overwhelming... BTW, mine shows 317 processes.

– nephewtom
Jan 24 at 15:16















I exported ProcMon info to a CSV file, and got a total of 10876 events with the following returned codes: TOTAL:10876, SUCCESS:7410, NAME NOT FOUND:2022, BUFFER, OVERFLOW:421, FILE LOCKED WITH ONLY READERS:396, FAST IO DISALLOWED:336, ACCESS DENIED:182 , NO MORE ENTRIES:46, REPARSE:38, PATH NOT FOUND:14, INVALID PARAMETER:5, IS DIRECTORY:4, BUFFER TOO SMALL:1, NAME INVALID:1

– nephewtom
Jan 24 at 15:45





I exported ProcMon info to a CSV file, and got a total of 10876 events with the following returned codes: TOTAL:10876, SUCCESS:7410, NAME NOT FOUND:2022, BUFFER, OVERFLOW:421, FILE LOCKED WITH ONLY READERS:396, FAST IO DISALLOWED:336, ACCESS DENIED:182 , NO MORE ENTRIES:46, REPARSE:38, PATH NOT FOUND:14, INVALID PARAMETER:5, IS DIRECTORY:4, BUFFER TOO SMALL:1, NAME INVALID:1

– nephewtom
Jan 24 at 15:45










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1397910%2fcommand-line-tools-to-view-process-list-in-windows-10-pslist-slow%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1397910%2fcommand-line-tools-to-view-process-list-in-windows-10-pslist-slow%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Список кардиналов, возведённых папой римским Каликстом III

Deduzione

Mysql.sock missing - “Can't connect to local MySQL server through socket”