Language:

Homepage » DLL Q & A

Cmd.Exe Application Failed To Initialize (0xc0000142)

Download Now


0xc0000142

LUCA CIMA asked on January 7, 2013. Status: Answered & Closed.

Cmd.Exe Application Failed To Initialize (0xc0000142)

» I have an issue with my Cmd.exe application. What happens is, whencever I try to use the Cmd.exe, it activates the program, however in a split second the program closes without me even doing anything to it. Then in another split second a pop up shows up and says this. "Windows is now shutting down" and it disappears. Soon my Laptop begins to close all the other applications and begins to power down.Can anyone please give me their thoughts and ideas for this issue?


Best Answer

» The exe file runs programs and can be used as a delivery system for viruses or other malicious programs. Viruses often reside to .exe files (Trojan:Win32/Medfos.A, for example); they can be running in the background, infecting or compromising the computer. The inflicted pc often has the symptoms of slowing down, high usage of CPU/memory, system crashes and so on. To deal with all of them, DLL Suite will be the best solution for you to troubleshoot and remove the exe virus infection automatically!

Download DLL Suite, install and run > Click Dashboard menu and > Click Scan DLL Errors button > Click Fix DLL Errors button after the scan. And all the problems directly associated with .exe files are fixed automatically.

HAYLEE WOLSEY replied on January 15, 2013


All Answers:

  1. TONY SUMIDA replied on January 7, 2013: » Are you running cmd.exe in elevated administrative mode? If not, lets try and see if you experience the problem while running cmd.exe in an elevated mode with administrator rights.

    How to open a elevated command prompt with administrator rights (Run as administrator) instead of the default command prompt without administrator rights. The cmd.exe file for the command prompt is located at C:\Windows\System32\cmd.exe: Open the Start Menu.> Click on All Programs and Accessories. > Right click on Command Prompt and click Run as administrator.> Click on Continue in the UAC prompt. If User account control is enabled.

    or you can: > Open the Start Menu.> In the white line (Start Search) area, type cmd> Right click on cmd (at top), and click on Run as administrator.NOTE: To open a regular non-elevated command prompt window, just click on cmd instead.

    > Click on Continue in the UAC prompt. Let us know if this helped or if you are still getting the same results.

  2. PATRICIA STREETER replied on January 8, 2013: » Did you try System Restore from the "repair mode", that will work on the not loaded operating system from within the Recovery Environment? Of course it might not fix the problem with cmd.exe but it may be worth a try.

    >Using System Restore from the Vista Windows Recovery Environmenthttp://www.bleepingcomputer.com/tutorials/tutorial142.html

    >About the only thing left to suggest if nothing above has helped is to backup and save your valuable data and then use the Recovery Options supplied by your OEM Manufacturer to return the machine to the Day One Factory Defaults.

  3. LUCA CIMA replied on January 9, 2013: » Restore the system did not work, but I found a folder "FOUND.000" in the root. Inside that folder find cmd.exe, conhost.exe, Comuid.dll and connect.dll. I went into repair mode and copying these files by hand and now it works perfectly. Now I'm using the sfc / scannow. :-)

    >Edit: Results

    >C: \ Users \ Shoke> sfc / scannow

    >Starting test on the system. This process will take some time.

    >Starting the verification phase of the review of the system.Testing was completed 100%.

    >Windows Resource Protection found corrupt files and failedrepair some of them. For more details, see CBS.log

    >windir \ Logs \ CBS \ CBS.log. For example, C: \ Windows \ Logs \ CBS \ CBS.log.

  4. PATRICIA STREETER replied on January 11, 2013: » I am glad you got CMD.exe working again, but I worry about copying those files from the "Found" folder as I believe they only ended up in there if ChkDsk found a problem with them or if they were on a bad sector of your hard drive? Maybe it is a warning to you that your hard drive is in danger of becoming unserviceable?

    >The hard drive manufacturer will have free, bootable, diagnostic software to thoroughly check the condition of your hard drive.

    >As for SFC, it is perhaps complaining about the files you recently restored, as well as other corrupt files that are unrepairable.

    >How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program generates in Windows Vistahttp://support.microsoft.com/kb/928228#appliesto

DLL Q & A you might like:

  1. Atibtmon.exe Microsoft Visual C++ Runtime Library Error »
  2. Corrupted Scanpst.exe File Needs to Be Downloaded »
  3. How To Fix BCHelper.exe Missing Sqlite3.dll »
  4. Hiber_nvraid.sys Blue Screen on Hibernate »
  5. Ifxupdate.exe Forces Cpu To Load 100% »
  6. Wuaudt.exe Is Really Bogging Down My Computer »
  7. 3 ways DLL Suite can fix your Windows missing DLL file error »