How to kill suspended processes in Windows 10
I've found a tons of arma3.exe processes in Task Manager. They all have status "Suspended". When i'm trying to kill them, I get the message "Access Denied".
I've tried to kill them with cmd
. Using /f /t but still "Access Denied". After that I've tried psexec -s
to gain System privileges, but still nothing.
I have Windows 10.
Do you have any idea how to kill those processes? And sorry for my English.
windows-10 process kill
|
show 2 more comments
I've found a tons of arma3.exe processes in Task Manager. They all have status "Suspended". When i'm trying to kill them, I get the message "Access Denied".
I've tried to kill them with cmd
. Using /f /t but still "Access Denied". After that I've tried psexec -s
to gain System privileges, but still nothing.
I have Windows 10.
Do you have any idea how to kill those processes? And sorry for my English.
windows-10 process kill
Did you try running command prompt as admin and then trying to kill the tasks using those commands?
– Tim G.
Jul 30 '16 at 13:59
It's possible that the process hung in a kernel operation. You have to reboot the OS in order to correctly kill that process.
– GiantTree
Jul 30 '16 at 14:16
2
So what happens when you resume them? You can do that with Process Explorer.
– Daniel B
Jul 30 '16 at 14:17
From an elevated command prompt RUN AS ADMINISTRATOR try 1.wmic process where name="arma3.exe" call terminate
. Additionally, if you've not launched the command prompt as administrator with taskkill then try that as well as 2.TASKKILL /F /IM "arma3.exe"
and see what result you get. If you still have trouble, checked services.msc and see if it's perhaps running as a service and you're have to complete a 3.NET STOP
to kill the executable processes.
– Pimp Juice IT
Jul 30 '16 at 18:01
When i'm trying to resume them, it says "Unable to suspend (?!) the process"
– Кирилл Трофимов
Jul 31 '16 at 19:19
|
show 2 more comments
I've found a tons of arma3.exe processes in Task Manager. They all have status "Suspended". When i'm trying to kill them, I get the message "Access Denied".
I've tried to kill them with cmd
. Using /f /t but still "Access Denied". After that I've tried psexec -s
to gain System privileges, but still nothing.
I have Windows 10.
Do you have any idea how to kill those processes? And sorry for my English.
windows-10 process kill
I've found a tons of arma3.exe processes in Task Manager. They all have status "Suspended". When i'm trying to kill them, I get the message "Access Denied".
I've tried to kill them with cmd
. Using /f /t but still "Access Denied". After that I've tried psexec -s
to gain System privileges, but still nothing.
I have Windows 10.
Do you have any idea how to kill those processes? And sorry for my English.
windows-10 process kill
windows-10 process kill
edited Nov 22 at 14:57
Aulis Ronkainen
5991814
5991814
asked Jul 30 '16 at 13:15
Кирилл Трофимов
1112
1112
Did you try running command prompt as admin and then trying to kill the tasks using those commands?
– Tim G.
Jul 30 '16 at 13:59
It's possible that the process hung in a kernel operation. You have to reboot the OS in order to correctly kill that process.
– GiantTree
Jul 30 '16 at 14:16
2
So what happens when you resume them? You can do that with Process Explorer.
– Daniel B
Jul 30 '16 at 14:17
From an elevated command prompt RUN AS ADMINISTRATOR try 1.wmic process where name="arma3.exe" call terminate
. Additionally, if you've not launched the command prompt as administrator with taskkill then try that as well as 2.TASKKILL /F /IM "arma3.exe"
and see what result you get. If you still have trouble, checked services.msc and see if it's perhaps running as a service and you're have to complete a 3.NET STOP
to kill the executable processes.
– Pimp Juice IT
Jul 30 '16 at 18:01
When i'm trying to resume them, it says "Unable to suspend (?!) the process"
– Кирилл Трофимов
Jul 31 '16 at 19:19
|
show 2 more comments
Did you try running command prompt as admin and then trying to kill the tasks using those commands?
– Tim G.
Jul 30 '16 at 13:59
It's possible that the process hung in a kernel operation. You have to reboot the OS in order to correctly kill that process.
– GiantTree
Jul 30 '16 at 14:16
2
So what happens when you resume them? You can do that with Process Explorer.
– Daniel B
Jul 30 '16 at 14:17
From an elevated command prompt RUN AS ADMINISTRATOR try 1.wmic process where name="arma3.exe" call terminate
. Additionally, if you've not launched the command prompt as administrator with taskkill then try that as well as 2.TASKKILL /F /IM "arma3.exe"
and see what result you get. If you still have trouble, checked services.msc and see if it's perhaps running as a service and you're have to complete a 3.NET STOP
to kill the executable processes.
– Pimp Juice IT
Jul 30 '16 at 18:01
When i'm trying to resume them, it says "Unable to suspend (?!) the process"
– Кирилл Трофимов
Jul 31 '16 at 19:19
Did you try running command prompt as admin and then trying to kill the tasks using those commands?
– Tim G.
Jul 30 '16 at 13:59
Did you try running command prompt as admin and then trying to kill the tasks using those commands?
– Tim G.
Jul 30 '16 at 13:59
It's possible that the process hung in a kernel operation. You have to reboot the OS in order to correctly kill that process.
– GiantTree
Jul 30 '16 at 14:16
It's possible that the process hung in a kernel operation. You have to reboot the OS in order to correctly kill that process.
– GiantTree
Jul 30 '16 at 14:16
2
2
So what happens when you resume them? You can do that with Process Explorer.
– Daniel B
Jul 30 '16 at 14:17
So what happens when you resume them? You can do that with Process Explorer.
– Daniel B
Jul 30 '16 at 14:17
From an elevated command prompt RUN AS ADMINISTRATOR try 1.
wmic process where name="arma3.exe" call terminate
. Additionally, if you've not launched the command prompt as administrator with taskkill then try that as well as 2. TASKKILL /F /IM "arma3.exe"
and see what result you get. If you still have trouble, checked services.msc and see if it's perhaps running as a service and you're have to complete a 3. NET STOP
to kill the executable processes.– Pimp Juice IT
Jul 30 '16 at 18:01
From an elevated command prompt RUN AS ADMINISTRATOR try 1.
wmic process where name="arma3.exe" call terminate
. Additionally, if you've not launched the command prompt as administrator with taskkill then try that as well as 2. TASKKILL /F /IM "arma3.exe"
and see what result you get. If you still have trouble, checked services.msc and see if it's perhaps running as a service and you're have to complete a 3. NET STOP
to kill the executable processes.– Pimp Juice IT
Jul 30 '16 at 18:01
When i'm trying to resume them, it says "Unable to suspend (?!) the process"
– Кирилл Трофимов
Jul 31 '16 at 19:19
When i'm trying to resume them, it says "Unable to suspend (?!) the process"
– Кирилл Трофимов
Jul 31 '16 at 19:19
|
show 2 more comments
2 Answers
2
active
oldest
votes
First of all, do a restart. If those processes start at boot there is something fishy about them. If the process is still there, upload one of them to virustotal.com and check for any malware.
add a comment |
Logging off/restarting should get rid of them. Do they start with the OS, even without executing the relevant program?
No, i've tried that at first, no result
– Кирилл Трофимов
Jul 30 '16 at 17:23
Hello Leo, Welcome to super user! Its good to see your wanting to help people. Try to use comments under the question to ask for more information. (You can do this when you get 50 rep) When answering the question its best to answer to the best of your ability. In this case perhaps adding what could be done next if they do restart, as OP has stated they do. Good luck!
– Lister
Aug 3 '16 at 12:09
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%2f1106800%2fhow-to-kill-suspended-processes-in-windows-10%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
First of all, do a restart. If those processes start at boot there is something fishy about them. If the process is still there, upload one of them to virustotal.com and check for any malware.
add a comment |
First of all, do a restart. If those processes start at boot there is something fishy about them. If the process is still there, upload one of them to virustotal.com and check for any malware.
add a comment |
First of all, do a restart. If those processes start at boot there is something fishy about them. If the process is still there, upload one of them to virustotal.com and check for any malware.
First of all, do a restart. If those processes start at boot there is something fishy about them. If the process is still there, upload one of them to virustotal.com and check for any malware.
answered Jul 30 '16 at 14:16
Steven
629316
629316
add a comment |
add a comment |
Logging off/restarting should get rid of them. Do they start with the OS, even without executing the relevant program?
No, i've tried that at first, no result
– Кирилл Трофимов
Jul 30 '16 at 17:23
Hello Leo, Welcome to super user! Its good to see your wanting to help people. Try to use comments under the question to ask for more information. (You can do this when you get 50 rep) When answering the question its best to answer to the best of your ability. In this case perhaps adding what could be done next if they do restart, as OP has stated they do. Good luck!
– Lister
Aug 3 '16 at 12:09
add a comment |
Logging off/restarting should get rid of them. Do they start with the OS, even without executing the relevant program?
No, i've tried that at first, no result
– Кирилл Трофимов
Jul 30 '16 at 17:23
Hello Leo, Welcome to super user! Its good to see your wanting to help people. Try to use comments under the question to ask for more information. (You can do this when you get 50 rep) When answering the question its best to answer to the best of your ability. In this case perhaps adding what could be done next if they do restart, as OP has stated they do. Good luck!
– Lister
Aug 3 '16 at 12:09
add a comment |
Logging off/restarting should get rid of them. Do they start with the OS, even without executing the relevant program?
Logging off/restarting should get rid of them. Do they start with the OS, even without executing the relevant program?
answered Jul 30 '16 at 15:47
JpegXguy
314
314
No, i've tried that at first, no result
– Кирилл Трофимов
Jul 30 '16 at 17:23
Hello Leo, Welcome to super user! Its good to see your wanting to help people. Try to use comments under the question to ask for more information. (You can do this when you get 50 rep) When answering the question its best to answer to the best of your ability. In this case perhaps adding what could be done next if they do restart, as OP has stated they do. Good luck!
– Lister
Aug 3 '16 at 12:09
add a comment |
No, i've tried that at first, no result
– Кирилл Трофимов
Jul 30 '16 at 17:23
Hello Leo, Welcome to super user! Its good to see your wanting to help people. Try to use comments under the question to ask for more information. (You can do this when you get 50 rep) When answering the question its best to answer to the best of your ability. In this case perhaps adding what could be done next if they do restart, as OP has stated they do. Good luck!
– Lister
Aug 3 '16 at 12:09
No, i've tried that at first, no result
– Кирилл Трофимов
Jul 30 '16 at 17:23
No, i've tried that at first, no result
– Кирилл Трофимов
Jul 30 '16 at 17:23
Hello Leo, Welcome to super user! Its good to see your wanting to help people. Try to use comments under the question to ask for more information. (You can do this when you get 50 rep) When answering the question its best to answer to the best of your ability. In this case perhaps adding what could be done next if they do restart, as OP has stated they do. Good luck!
– Lister
Aug 3 '16 at 12:09
Hello Leo, Welcome to super user! Its good to see your wanting to help people. Try to use comments under the question to ask for more information. (You can do this when you get 50 rep) When answering the question its best to answer to the best of your ability. In this case perhaps adding what could be done next if they do restart, as OP has stated they do. Good luck!
– Lister
Aug 3 '16 at 12:09
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f1106800%2fhow-to-kill-suspended-processes-in-windows-10%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 running command prompt as admin and then trying to kill the tasks using those commands?
– Tim G.
Jul 30 '16 at 13:59
It's possible that the process hung in a kernel operation. You have to reboot the OS in order to correctly kill that process.
– GiantTree
Jul 30 '16 at 14:16
2
So what happens when you resume them? You can do that with Process Explorer.
– Daniel B
Jul 30 '16 at 14:17
From an elevated command prompt RUN AS ADMINISTRATOR try 1.
wmic process where name="arma3.exe" call terminate
. Additionally, if you've not launched the command prompt as administrator with taskkill then try that as well as 2.TASKKILL /F /IM "arma3.exe"
and see what result you get. If you still have trouble, checked services.msc and see if it's perhaps running as a service and you're have to complete a 3.NET STOP
to kill the executable processes.– Pimp Juice IT
Jul 30 '16 at 18:01
When i'm trying to resume them, it says "Unable to suspend (?!) the process"
– Кирилл Трофимов
Jul 31 '16 at 19:19