Cmd.exe error message
Solved
Hello,
For the past few days, when I start my PC (running Windows 10), the following message appears:
cmd.exe Application Error
The application failed to start (0xc0000142)
I ran a virus scan with Avast yesterday and a scan with Malwarebytes this morning but I found nothing suspicious. I also cleaned the registry with Ccleaner but nothing helps.
Do you have any solutions?
Thank you in advance!
Configuration: Windows / Chrome 47.0.2526.106
For the past few days, when I start my PC (running Windows 10), the following message appears:
cmd.exe Application Error
The application failed to start (0xc0000142)
I ran a virus scan with Avast yesterday and a scan with Malwarebytes this morning but I found nothing suspicious. I also cleaned the registry with Ccleaner but nothing helps.
Do you have any solutions?
Thank you in advance!
Configuration: Windows / Chrome 47.0.2526.106
7 answers
-
Hello
Check if you have an ongoing update by clicking on Start, then Settings and Update
--
Computing is just a tool, like a brush or a pencil.
Avoid installing those so-called free software that supposedly boosts or repairs your PC; it has no major usefulness. The best tools -
Hello,
There was indeed an update in progress that had not been completed correctly. I clicked on Retry and then I restarted my PC, but unfortunately the error message still reappears! -
Yes, the update installed without any problems!
-
How to run this command as an administrator? Thank you!
-
Thank you! I started a scan, I'll keep you updated!
-
The scan is complete: no integrity violation detected...
-
Do you have any other suggestions?
-
-
@beber67470I installed Office 365. I actually had to perform a repair because my existing Excel files wouldn’t open. I also optimized the startup with CCleaner, maybe that could be the issue?
-
@DumazYour error message appeared before these installations!
-
@beber67470No, it appeared afterward. I reactivated all the services and processes that I had disabled at startup with CCleaner to check if that was the cause, but the message still shows up.
-
@DumazBy activating these services, did you restart to synchronize?
-