How to search a process by name?
SearchIndexer.exe is preventing my device, which actually is my external hard drive, to be stopped.
I tried to close this application by looking up onto Task Manager, but couldn't find it on Processes tab.
Can I look up this process by name, get process id, and kill it?
windows windows-8.1 powershell
asked Jul 20 '17 at 8:54
Santosh KumarSantosh Kumar
5671934
add a comment |
SearchIndexer.exe is preventing my device, which actually is my external hard drive, to be stopped.
I tried to close this application by looking up onto Task Manager, but couldn't find it on Processes tab.
Can I look up this process by name, get process id, and kill it?
windows windows-8.1 powershell
asked Jul 20 '17 at 8:54
Santosh KumarSantosh Kumar
5671934
Did you try with Process Explorer?
– simlev
Jul 20 '17 at 13:54
No, I don't find SearchIndexer.exe in the Disk tab, under the Processes with Disk Activity.
– Santosh Kumar
Jul 20 '17 at 14:11
Well, I'm suggesting you try with a different tool called Process Explorer.
– simlev
Jul 20 '17 at 14:30
run control panel and exclude your external HDD from search index
– magicandre1981
Jul 20 '17 at 14:46
add a comment |
SearchIndexer.exe is preventing my device, which actually is my external hard drive, to be stopped.
I tried to close this application by looking up onto Task Manager, but couldn't find it on Processes tab.
Can I look up this process by name, get process id, and kill it?
windows windows-8.1 powershell
asked Jul 20 '17 at 8:54
Santosh KumarSantosh Kumar
5671934
SearchIndexer.exe is preventing my device, which actually is my external hard drive, to be stopped.
I tried to close this application by looking up onto Task Manager, but couldn't find it on Processes tab.
Can I look up this process by name, get process id, and kill it?
windows windows-8.1 powershell
windows windows-8.1 powershell
asked Jul 20 '17 at 8:54
Santosh KumarSantosh Kumar
5671934
asked Jul 20 '17 at 8:54
Santosh KumarSantosh Kumar
5671934
asked Jul 20 '17 at 8:54
Santosh KumarSantosh Kumar
5671934
asked Jul 20 '17 at 8:54
Santosh KumarSantosh Kumar
5671934
asked Jul 20 '17 at 8:54
Santosh KumarSantosh Kumar
5671934
5671934
Did you try with Process Explorer?
– simlev
Jul 20 '17 at 13:54
No, I don't find SearchIndexer.exe in the Disk tab, under the Processes with Disk Activity.
– Santosh Kumar
Jul 20 '17 at 14:11
Well, I'm suggesting you try with a different tool called Process Explorer.
– simlev
Jul 20 '17 at 14:30
run control panel and exclude your external HDD from search index
– magicandre1981
Jul 20 '17 at 14:46
add a comment |
Did you try with Process Explorer?
– simlev
Jul 20 '17 at 13:54
No, I don't find SearchIndexer.exe in the Disk tab, under the Processes with Disk Activity.
– Santosh Kumar
Jul 20 '17 at 14:11
Well, I'm suggesting you try with a different tool called Process Explorer.
– simlev
Jul 20 '17 at 14:30
run control panel and exclude your external HDD from search index
– magicandre1981
Jul 20 '17 at 14:46
Did you try with Process Explorer?
– simlev
Jul 20 '17 at 13:54
Did you try with Process Explorer?
– simlev
Jul 20 '17 at 13:54
No, I don't find SearchIndexer.exe in the Disk tab, under the Processes with Disk Activity.
– Santosh Kumar
Jul 20 '17 at 14:11
No, I don't find SearchIndexer.exe in the Disk tab, under the Processes with Disk Activity.
– Santosh Kumar
Jul 20 '17 at 14:11
Well, I'm suggesting you try with a different tool called Process Explorer.
– simlev
Jul 20 '17 at 14:30
Well, I'm suggesting you try with a different tool called Process Explorer.
– simlev
Jul 20 '17 at 14:30
run control panel and exclude your external HDD from search index
– magicandre1981
Jul 20 '17 at 14:46
run control panel and exclude your external HDD from search index
– magicandre1981
Jul 20 '17 at 14:46
add a comment |
1 Answer
1
active
oldest
votes
If you're looking for processes such as SearchIndexer - this should be pretty simple to do with PowerShell
Get-Process will show you a list of running processes. In this case, I have piped it to Select -first 1 because you're interested in the column headers, not a list of the 100+ processes on my PC:
Next up - now you know how to get processes, you need to narrow this down to a specific process. Below, I've shown 4 methods to do this:
Get-Process Search* will return all processes starting with search
Get-Process SearchIndexer will return just that one process if it exists
Get-Process | Where {$_.Name -eq "SearchIndexer"} will find all processes and then only select the one called SearchIndexer
Get-Process | Where {$_.ProcessName -Like "SearchIn*"} will get all processes and narrow down to ones that start with "SearchIn".
As a side note - you can use wild cards at either end, so `rchInde" will also return the process you want.
Now - to kill the process - pipe it to Stop-Process:
..But it didnt work!
To Stop it - as with some processes - you need to run PowerShell as an Administrator:
..but you still get a prompt!
...ignore the error at the bottom, we've just proven that the process doesn't exist any more
Add the -Force switch and the prompt goes away!
But we dont like errors when we try to do it over and over:
...so we need to handle it slightly differently. Instead of explicitly stopping that one process, grab all of them, filter it down to the ones we want (if any) and then kill them (if they exist):
last up - add it as a scheduled task action (if you need to) as windows likes to restart certain services/processes and you're all set.
answered Jul 20 '17 at 14:59
Fazer87Fazer87
10.5k12742
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1231640%2fhow-to-search-a-process-by-name%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you're looking for processes such as SearchIndexer - this should be pretty simple to do with PowerShell
Get-Process will show you a list of running processes. In this case, I have piped it to Select -first 1 because you're interested in the column headers, not a list of the 100+ processes on my PC:
Next up - now you know how to get processes, you need to narrow this down to a specific process. Below, I've shown 4 methods to do this:
Get-Process Search* will return all processes starting with search
Get-Process SearchIndexer will return just that one process if it exists
Get-Process | Where {$_.Name -eq "SearchIndexer"} will find all processes and then only select the one called SearchIndexer
Get-Process | Where {$_.ProcessName -Like "SearchIn*"} will get all processes and narrow down to ones that start with "SearchIn".
As a side note - you can use wild cards at either end, so `rchInde" will also return the process you want.
Now - to kill the process - pipe it to Stop-Process:
..But it didnt work!
To Stop it - as with some processes - you need to run PowerShell as an Administrator:
..but you still get a prompt!
...ignore the error at the bottom, we've just proven that the process doesn't exist any more
Add the -Force switch and the prompt goes away!
But we dont like errors when we try to do it over and over:
...so we need to handle it slightly differently. Instead of explicitly stopping that one process, grab all of them, filter it down to the ones we want (if any) and then kill them (if they exist):
last up - add it as a scheduled task action (if you need to) as windows likes to restart certain services/processes and you're all set.
answered Jul 20 '17 at 14:59
Fazer87Fazer87
10.5k12742
add a comment |
If you're looking for processes such as SearchIndexer - this should be pretty simple to do with PowerShell
Get-Process will show you a list of running processes. In this case, I have piped it to Select -first 1 because you're interested in the column headers, not a list of the 100+ processes on my PC:
Next up - now you know how to get processes, you need to narrow this down to a specific process. Below, I've shown 4 methods to do this:
Get-Process Search* will return all processes starting with search
Get-Process SearchIndexer will return just that one process if it exists
Get-Process | Where {$_.Name -eq "SearchIndexer"} will find all processes and then only select the one called SearchIndexer
Get-Process | Where {$_.ProcessName -Like "SearchIn*"} will get all processes and narrow down to ones that start with "SearchIn".
As a side note - you can use wild cards at either end, so `rchInde" will also return the process you want.
Now - to kill the process - pipe it to Stop-Process:
..But it didnt work!
To Stop it - as with some processes - you need to run PowerShell as an Administrator:
..but you still get a prompt!
...ignore the error at the bottom, we've just proven that the process doesn't exist any more
Add the -Force switch and the prompt goes away!
But we dont like errors when we try to do it over and over:
...so we need to handle it slightly differently. Instead of explicitly stopping that one process, grab all of them, filter it down to the ones we want (if any) and then kill them (if they exist):
last up - add it as a scheduled task action (if you need to) as windows likes to restart certain services/processes and you're all set.
answered Jul 20 '17 at 14:59
Fazer87Fazer87
10.5k12742
add a comment |
If you're looking for processes such as SearchIndexer - this should be pretty simple to do with PowerShell
Get-Process will show you a list of running processes. In this case, I have piped it to Select -first 1 because you're interested in the column headers, not a list of the 100+ processes on my PC:
Next up - now you know how to get processes, you need to narrow this down to a specific process. Below, I've shown 4 methods to do this:
Get-Process Search* will return all processes starting with search
Get-Process SearchIndexer will return just that one process if it exists
Get-Process | Where {$_.Name -eq "SearchIndexer"} will find all processes and then only select the one called SearchIndexer
Get-Process | Where {$_.ProcessName -Like "SearchIn*"} will get all processes and narrow down to ones that start with "SearchIn".
As a side note - you can use wild cards at either end, so `rchInde" will also return the process you want.
Now - to kill the process - pipe it to Stop-Process:
..But it didnt work!
To Stop it - as with some processes - you need to run PowerShell as an Administrator:
..but you still get a prompt!
...ignore the error at the bottom, we've just proven that the process doesn't exist any more
Add the -Force switch and the prompt goes away!
But we dont like errors when we try to do it over and over:
...so we need to handle it slightly differently. Instead of explicitly stopping that one process, grab all of them, filter it down to the ones we want (if any) and then kill them (if they exist):
last up - add it as a scheduled task action (if you need to) as windows likes to restart certain services/processes and you're all set.
answered Jul 20 '17 at 14:59
Fazer87Fazer87
10.5k12742
If you're looking for processes such as SearchIndexer - this should be pretty simple to do with PowerShell
Get-Process will show you a list of running processes. In this case, I have piped it to Select -first 1 because you're interested in the column headers, not a list of the 100+ processes on my PC:
Next up - now you know how to get processes, you need to narrow this down to a specific process. Below, I've shown 4 methods to do this:
Get-Process Search* will return all processes starting with search
Get-Process SearchIndexer will return just that one process if it exists
Get-Process | Where {$_.Name -eq "SearchIndexer"} will find all processes and then only select the one called SearchIndexer
Get-Process | Where {$_.ProcessName -Like "SearchIn*"} will get all processes and narrow down to ones that start with "SearchIn".
As a side note - you can use wild cards at either end, so `rchInde" will also return the process you want.
Now - to kill the process - pipe it to Stop-Process:
..But it didnt work!
To Stop it - as with some processes - you need to run PowerShell as an Administrator:
..but you still get a prompt!
...ignore the error at the bottom, we've just proven that the process doesn't exist any more
Add the -Force switch and the prompt goes away!
But we dont like errors when we try to do it over and over:
...so we need to handle it slightly differently. Instead of explicitly stopping that one process, grab all of them, filter it down to the ones we want (if any) and then kill them (if they exist):
last up - add it as a scheduled task action (if you need to) as windows likes to restart certain services/processes and you're all set.
answered Jul 20 '17 at 14:59
Fazer87Fazer87
10.5k12742
edited Feb 6 at 15:50
answered Jul 20 '17 at 14:59
Fazer87Fazer87
10.5k12742
answered Jul 20 '17 at 14:59
Fazer87Fazer87
10.5k12742
answered Jul 20 '17 at 14:59
Fazer87Fazer87
10.5k12742
10.5k12742
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1231640%2fhow-to-search-a-process-by-name%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
Did you try with Process Explorer?
– simlev
Jul 20 '17 at 13:54
No, I don't find SearchIndexer.exe in the Disk tab, under the Processes with Disk Activity.
– Santosh Kumar
Jul 20 '17 at 14:11
Well, I'm suggesting you try with a different tool called Process Explorer.
– simlev
Jul 20 '17 at 14:30
run control panel and exclude your external HDD from search index
– magicandre1981
Jul 20 '17 at 14:46