asked on

0xc0000142 error as cmd.exe is started in XP

Have been struggling with this error. Can't load cmd.exe. An error message, "The aaplication failed to initialize properly (0xc0000142)", pops up.
There are some posts as to Oxc0000142 error, not specifically related to cmd.exe. Posted answers are two types. Some say it's from Virus. Others say it's due to corrupted files to run cmd.exe. Also, one post from Microsoft, pointing out Roxio product's incompatibility. But no Roxio product is installed on my machine.

Suspecting a virus, tried various virus scans including McAfee, and regiestry cleaner such as RegistryFix.
But, didn't do any good.

Now, I would like to replace cmd.exe and dependent files with clean files from XP CD or other computer.
What files needs to be copied?

Thanks in advance

ASKER CERTIFIED SOLUTION

rossfingal

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

nobus

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

terrygreensill

I had a similar problem and i found two files which should not be there in c:\windows\system32\

cmd.com and regedit.com

I deleted them and this fixed the problem

The giveaway is when you run cmd from the run menu it runs cmd.com instead of cmd.exe. The same happened for my regedit.exe.

This might not be your problem but thought I should mention it

garrettf

I've had a similar problem on two systems that had been using for localization testing and had the Asian languages installed and then removed.

Using Sysinternal's Process Explorer, I found (on a working system ) that cmd.exe reads the NLS (Native Language Support) registry key. (HKLM\System\Current Control Set\Control\Nls)

I exported the key from the working system to the other system and the command console now opens up correctly.

pjedmond

This error occurs when a program tries to use CreateProcess, but is denied by application interaction control. Typically this is due to antivirus software/security software.

For Zone Alarm, this issue can eb resolved by:

Go to the program control tab, click the main tab, click the custom button under program control and see if "integrated application control" is enabled. If so, view the alerts & logs to see which program tried to use CreateProcess but was denied. To allow application interaction for that program, go to program control > programs tab, right click the program, select options and check "allow application interaction"

HTH:)

solutia

Thanks, garrettf, the language setting was the culprit in my case! I followed your instructions and fixed problem.