cmd.exe error windows 7 the application was unable to start correctly (0xc0000142). Click ok to close the...
up vote
1
down vote
favorite
when i try to open the cmd.exe. a box pops up with the message of cmd.exe error windows 7 the application was unable to start correctly (0xc0000142). Click ok to close the application.
my pc was infected with surabaya virus and rootkit and removed it with Avast free anti virus and malwarebytes, spybot, but after this i am unable to open some files like windows defender and some system files.
windows-7 command-line virus cmd.exe
edited Dec 5 '15 at 22:29
Hennes
58.7k792141
asked Jan 6 '15 at 13:26
Shrikant
612
add a comment |
up vote
1
down vote
favorite
when i try to open the cmd.exe. a box pops up with the message of cmd.exe error windows 7 the application was unable to start correctly (0xc0000142). Click ok to close the application.
my pc was infected with surabaya virus and rootkit and removed it with Avast free anti virus and malwarebytes, spybot, but after this i am unable to open some files like windows defender and some system files.
windows-7 command-line virus cmd.exe
edited Dec 5 '15 at 22:29
Hennes
58.7k792141
asked Jan 6 '15 at 13:26
Shrikant
612
It sounds like the tools improperly removed the infection. Without access to a command prompt your problem cannot be solved. The only real solution is to install a fresh instance Windows.
– Ramhound
Jan 6 '15 at 13:33
if you have configured system backup and restore,try to do the restore with the latest version of the backup which would give the error-free installation
– vembutech
Jan 6 '15 at 13:38
Find if conhost.exe present in system32 or syswow64 folder.
– Biswapriyo
Aug 3 '17 at 8:13
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
when i try to open the cmd.exe. a box pops up with the message of cmd.exe error windows 7 the application was unable to start correctly (0xc0000142). Click ok to close the application.
my pc was infected with surabaya virus and rootkit and removed it with Avast free anti virus and malwarebytes, spybot, but after this i am unable to open some files like windows defender and some system files.
windows-7 command-line virus cmd.exe
edited Dec 5 '15 at 22:29
Hennes
58.7k792141
asked Jan 6 '15 at 13:26
Shrikant
612
when i try to open the cmd.exe. a box pops up with the message of cmd.exe error windows 7 the application was unable to start correctly (0xc0000142). Click ok to close the application.
my pc was infected with surabaya virus and rootkit and removed it with Avast free anti virus and malwarebytes, spybot, but after this i am unable to open some files like windows defender and some system files.
windows-7 command-line virus cmd.exe
windows-7 command-line virus cmd.exe
edited Dec 5 '15 at 22:29
Hennes
58.7k792141
asked Jan 6 '15 at 13:26
Shrikant
612
edited Dec 5 '15 at 22:29
Hennes
58.7k792141
asked Jan 6 '15 at 13:26
Shrikant
612
edited Dec 5 '15 at 22:29
Hennes
58.7k792141
edited Dec 5 '15 at 22:29
Hennes
58.7k792141
edited Dec 5 '15 at 22:29
Hennes
58.7k792141
58.7k792141
asked Jan 6 '15 at 13:26
Shrikant
612
asked Jan 6 '15 at 13:26
Shrikant
612
asked Jan 6 '15 at 13:26
Shrikant
612
612
It sounds like the tools improperly removed the infection. Without access to a command prompt your problem cannot be solved. The only real solution is to install a fresh instance Windows.
– Ramhound
Jan 6 '15 at 13:33
if you have configured system backup and restore,try to do the restore with the latest version of the backup which would give the error-free installation
– vembutech
Jan 6 '15 at 13:38
Find if conhost.exe present in system32 or syswow64 folder.
– Biswapriyo
Aug 3 '17 at 8:13
add a comment |
It sounds like the tools improperly removed the infection. Without access to a command prompt your problem cannot be solved. The only real solution is to install a fresh instance Windows.
– Ramhound
Jan 6 '15 at 13:33
if you have configured system backup and restore,try to do the restore with the latest version of the backup which would give the error-free installation
– vembutech
Jan 6 '15 at 13:38
Find if conhost.exe present in system32 or syswow64 folder.
– Biswapriyo
Aug 3 '17 at 8:13
It sounds like the tools improperly removed the infection. Without access to a command prompt your problem cannot be solved. The only real solution is to install a fresh instance Windows.
– Ramhound
Jan 6 '15 at 13:33
It sounds like the tools improperly removed the infection. Without access to a command prompt your problem cannot be solved. The only real solution is to install a fresh instance Windows.
– Ramhound
Jan 6 '15 at 13:33
if you have configured system backup and restore,try to do the restore with the latest version of the backup which would give the error-free installation
– vembutech
Jan 6 '15 at 13:38
if you have configured system backup and restore,try to do the restore with the latest version of the backup which would give the error-free installation
– vembutech
Jan 6 '15 at 13:38
Find if conhost.exe present in system32 or syswow64 folder.
– Biswapriyo
Aug 3 '17 at 8:13
Find if conhost.exe present in system32 or syswow64 folder.
– Biswapriyo
Aug 3 '17 at 8:13
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
I have read this began for some users after a Windows Update in Nov 2014. It seems to be a conflict with Geforce Experience (Nvidia graphics cards) and the Win Update.
Uninstalling Geforce experience has worked for many people. Perhaps Nividia are aware of the issue and have released a new driver by now - worth checking.
answered Jan 29 '15 at 8:59
john
1
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I have read this began for some users after a Windows Update in Nov 2014. It seems to be a conflict with Geforce Experience (Nvidia graphics cards) and the Win Update.
Uninstalling Geforce experience has worked for many people. Perhaps Nividia are aware of the issue and have released a new driver by now - worth checking.
answered Jan 29 '15 at 8:59
john
1
add a comment |
up vote
0
down vote
I have read this began for some users after a Windows Update in Nov 2014. It seems to be a conflict with Geforce Experience (Nvidia graphics cards) and the Win Update.
Uninstalling Geforce experience has worked for many people. Perhaps Nividia are aware of the issue and have released a new driver by now - worth checking.
answered Jan 29 '15 at 8:59
john
1
add a comment |
up vote
0
down vote
up vote
0
down vote
I have read this began for some users after a Windows Update in Nov 2014. It seems to be a conflict with Geforce Experience (Nvidia graphics cards) and the Win Update.
Uninstalling Geforce experience has worked for many people. Perhaps Nividia are aware of the issue and have released a new driver by now - worth checking.
answered Jan 29 '15 at 8:59
john
1
I have read this began for some users after a Windows Update in Nov 2014. It seems to be a conflict with Geforce Experience (Nvidia graphics cards) and the Win Update.
Uninstalling Geforce experience has worked for many people. Perhaps Nividia are aware of the issue and have released a new driver by now - worth checking.
answered Jan 29 '15 at 8:59
john
1
answered Jan 29 '15 at 8:59
john
1
answered Jan 29 '15 at 8:59
john
1
answered Jan 29 '15 at 8:59
john
1
1
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.
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%2f861300%2fcmd-exe-error-windows-7-the-application-was-unable-to-start-correctly-0xc000014%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
It sounds like the tools improperly removed the infection. Without access to a command prompt your problem cannot be solved. The only real solution is to install a fresh instance Windows.
– Ramhound
Jan 6 '15 at 13:33
if you have configured system backup and restore,try to do the restore with the latest version of the backup which would give the error-free installation
– vembutech
Jan 6 '15 at 13:38
Find if conhost.exe present in system32 or syswow64 folder.
– Biswapriyo
Aug 3 '17 at 8:13