CMD does not open

[Yosh]

I cannot open CMD. A box appears and it says, "The application failed to
initialize properly (0xc0000142). Click on OK to terminate the application."

 

[Pegasus \(MVP\)]

"Yosh" <Yosh@discussions.microsoft.com> wrote in message
news:CC6E260F-EE04-43BB-AE49-BB4F6263E750@microsoft.com...
>I cannot open CMD. A box appears and it says, "The application failed to
> initialize properly (0xc0000142). Click on OK to terminate the
> application."

There are several ways to open a Command Prompt. You
need to tell us which method you use. In the meantime do
this:
- Click Start, then Run
- Type this: c:\windows\system32\cmd.exe {Enter}
- Report the result.
- Try the same in Safe Mode.

 

[Yosh]

Pegasus,

Thanks for your suggestion.
Could you tell me how to got into the Safe Mode?



"Pegasus (MVP)" wrote:

>
> "Yosh" <Yosh@discussions.microsoft.com> wrote in message
> news:CC6E260F-EE04-43BB-AE49-BB4F6263E750@microsoft.com...
> >I cannot open CMD. A box appears and it says, "The application failed to
> > initialize properly (0xc0000142). Click on OK to terminate the
> > application."
>
> There are several ways to open a Command Prompt. You
> need to tell us which method you use. In the meantime do
> this:
> - Click Start, then Run
> - Type this: c:\windows\system32\cmd.exe {Enter}
> - Report the result.
> - Try the same in Safe Mode.
>
>
>

 

[Pegasus \(MVP\)]

You press F8 repeatedly during the early boot phase, then
select Safe Mode from the menu you see.


"Yosh" <Yosh@discussions.microsoft.com> wrote in message
news:EC9D4022-ECB0-4779-8B5A-42E5170E440F@microsoft.com...
> Pegasus,
>
> Thanks for your suggestion.
> Could you tell me how to got into the Safe Mode?
>
>
>
> "Pegasus (MVP)" wrote:
>
>>
>> "Yosh" <Yosh@discussions.microsoft.com> wrote in message
>> news:CC6E260F-EE04-43BB-AE49-BB4F6263E750@microsoft.com...
>> >I cannot open CMD. A box appears and it says, "The application failed to
>> > initialize properly (0xc0000142). Click on OK to terminate the
>> > application."
>>
>> There are several ways to open a Command Prompt. You
>> need to tell us which method you use. In the meantime do
>> this:
>> - Click Start, then Run
>> - Type this: c:\windows\system32\cmd.exe {Enter}
>> - Report the result.
>> - Try the same in Safe Mode.
>>
>>
>>

 

[Yosh]

Now I have tried both normal and safe modes and starting CMD by typing
c:\windows\system32\cmd.exe {Enter}

Both results are the same and What I got was the message:
"The application failed to initialize properly (0xc0000142). Click on OK to
terminate the application."



"Pegasus (MVP)" wrote:

> You press F8 repeatedly during the early boot phase, then
> select Safe Mode from the menu you see.
>
>
> "Yosh" <Yosh@discussions.microsoft.com> wrote in message
> news:EC9D4022-ECB0-4779-8B5A-42E5170E440F@microsoft.com...
> > Pegasus,
> >
> > Thanks for your suggestion.
> > Could you tell me how to got into the Safe Mode?
> >
> >
> >
> > "Pegasus (MVP)" wrote:
> >
> >>
> >> "Yosh" <Yosh@discussions.microsoft.com> wrote in message
> >> news:CC6E260F-EE04-43BB-AE49-BB4F6263E750@microsoft.com...
> >> >I cannot open CMD. A box appears and it says, "The application failed to
> >> > initialize properly (0xc0000142). Click on OK to terminate the
> >> > application."
> >>
> >> There are several ways to open a Command Prompt. You
> >> need to tell us which method you use. In the meantime do
> >> this:
> >> - Click Start, then Run
> >> - Type this: c:\windows\system32\cmd.exe {Enter}
> >> - Report the result.
> >> - Try the same in Safe Mode.
> >>
> >>
> >>
>
>
>

 

[Pegasus \(MVP\)]

It sounds as if your command processor is corrupted. Try a
System File Check by doing this:
- Click Start / Run
- Type sfc.exe /scannow {OK}

"Yosh" <Yosh@discussions.microsoft.com> wrote in message
newsEAAA3E8-258F-4A3E-A28D-6048D78582AF@microsoft.com...
> Now I have tried both normal and safe modes and starting CMD by typing
> c:\windows\system32\cmd.exe {Enter}
>
> Both results are the same and What I got was the message:
> "The application failed to initialize properly (0xc0000142). Click on OK
> to
> terminate the application."
>
>
>
> "Pegasus (MVP)" wrote:
>
>> You press F8 repeatedly during the early boot phase, then
>> select Safe Mode from the menu you see.
>>
>>
>> "Yosh" <Yosh@discussions.microsoft.com> wrote in message
>> news:EC9D4022-ECB0-4779-8B5A-42E5170E440F@microsoft.com...
>> > Pegasus,
>> >
>> > Thanks for your suggestion.
>> > Could you tell me how to got into the Safe Mode?
>> >
>> >
>> >
>> > "Pegasus (MVP)" wrote:
>> >
>> >>
>> >> "Yosh" <Yosh@discussions.microsoft.com> wrote in message
>> >> news:CC6E260F-EE04-43BB-AE49-BB4F6263E750@microsoft.com...
>> >> >I cannot open CMD. A box appears and it says, "The application failed
>> >> >to
>> >> > initialize properly (0xc0000142). Click on OK to terminate the
>> >> > application."
>> >>
>> >> There are several ways to open a Command Prompt. You
>> >> need to tell us which method you use. In the meantime do
>> >> this:
>> >> - Click Start, then Run
>> >> - Type this: c:\windows\system32\cmd.exe {Enter}
>> >> - Report the result.
>> >> - Try the same in Safe Mode.
>> >>
>> >>
>> >>
>>
>>
>>

 

[Yosh]

I tried bur since the CMD was not working the command line sfc.exe did not
work.


"Pegasus (MVP)" wrote:

> It sounds as if your command processor is corrupted. Try a
> System File Check by doing this:
> - Click Start / Run
> - Type sfc.exe /scannow {OK}
>
> "Yosh" <Yosh@discussions.microsoft.com> wrote in message
> newsEAAA3E8-258F-4A3E-A28D-6048D78582AF@microsoft.com...
> > Now I have tried both normal and safe modes and starting CMD by typing
> > c:\windows\system32\cmd.exe {Enter}
> >
> > Both results are the same and What I got was the message:
> > "The application failed to initialize properly (0xc0000142). Click on OK
> > to
> > terminate the application."
> >
> >
> >
> > "Pegasus (MVP)" wrote:
> >
> >> You press F8 repeatedly during the early boot phase, then
> >> select Safe Mode from the menu you see.
> >>
> >>
> >> "Yosh" <Yosh@discussions.microsoft.com> wrote in message
> >> news:EC9D4022-ECB0-4779-8B5A-42E5170E440F@microsoft.com...
> >> > Pegasus,
> >> >
> >> > Thanks for your suggestion.
> >> > Could you tell me how to got into the Safe Mode?
> >> >
> >> >
> >> >
> >> > "Pegasus (MVP)" wrote:
> >> >
> >> >>
> >> >> "Yosh" <Yosh@discussions.microsoft.com> wrote in message
> >> >> news:CC6E260F-EE04-43BB-AE49-BB4F6263E750@microsoft.com...
> >> >> >I cannot open CMD. A box appears and it says, "The application failed
> >> >> >to
> >> >> > initialize properly (0xc0000142). Click on OK to terminate the
> >> >> > application."
> >> >>
> >> >> There are several ways to open a Command Prompt. You
> >> >> need to tell us which method you use. In the meantime do
> >> >> this:
> >> >> - Click Start, then Run
> >> >> - Type this: c:\windows\system32\cmd.exe {Enter}
> >> >> - Report the result.
> >> >> - Try the same in Safe Mode.
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>

 

[Pegasus \(MVP\)]

This is getting serious. Since sfc.exe does not depend on
cmd.exe, the failure you report suggests that something is
wrong with the process that launches new processes.
I would now use System Restore to return the machine to
a point before the problem started. If you're unsure how
to do this, click Start / Help and look for help on System
Restore.


"Yosh" <Yosh@discussions.microsoft.com> wrote in message
news:AF0B7805-7EDF-4BDD-BF5A-1B39074E20DF@microsoft.com...
>I tried bur since the CMD was not working the command line sfc.exe did not
> work.
>
>
> "Pegasus (MVP)" wrote:
>
>> It sounds as if your command processor is corrupted. Try a
>> System File Check by doing this:
>> - Click Start / Run
>> - Type sfc.exe /scannow {OK}
>>
>> "Yosh" <Yosh@discussions.microsoft.com> wrote in message
>> newsEAAA3E8-258F-4A3E-A28D-6048D78582AF@microsoft.com...
>> > Now I have tried both normal and safe modes and starting CMD by typing
>> > c:\windows\system32\cmd.exe {Enter}
>> >
>> > Both results are the same and What I got was the message:
>> > "The application failed to initialize properly (0xc0000142). Click on
>> > OK
>> > to
>> > terminate the application."
>> >
>> >
>> >
>> > "Pegasus (MVP)" wrote:
>> >
>> >> You press F8 repeatedly during the early boot phase, then
>> >> select Safe Mode from the menu you see.
>> >>
>> >>
>> >> "Yosh" <Yosh@discussions.microsoft.com> wrote in message
>> >> news:EC9D4022-ECB0-4779-8B5A-42E5170E440F@microsoft.com...
>> >> > Pegasus,
>> >> >
>> >> > Thanks for your suggestion.
>> >> > Could you tell me how to got into the Safe Mode?
>> >> >
>> >> >
>> >> >
>> >> > "Pegasus (MVP)" wrote:
>> >> >
>> >> >>
>> >> >> "Yosh" <Yosh@discussions.microsoft.com> wrote in message
>> >> >> news:CC6E260F-EE04-43BB-AE49-BB4F6263E750@microsoft.com...
>> >> >> >I cannot open CMD. A box appears and it says, "The application
>> >> >> >failed
>> >> >> >to
>> >> >> > initialize properly (0xc0000142). Click on OK to terminate the
>> >> >> > application."
>> >> >>
>> >> >> There are several ways to open a Command Prompt. You
>> >> >> need to tell us which method you use. In the meantime do
>> >> >> this:
>> >> >> - Click Start, then Run
>> >> >> - Type this: c:\windows\system32\cmd.exe {Enter}
>> >> >> - Report the result.
>> >> >> - Try the same in Safe Mode.
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>

 

[Yosh]

I put my Xin XP CD and did managed to scan by sfc. It appears to be DLL
Chache was damaged.

It is now working.

Thanks.

"Pegasus (MVP)" wrote:

> This is getting serious. Since sfc.exe does not depend on
> cmd.exe, the failure you report suggests that something is
> wrong with the process that launches new processes.
> I would now use System Restore to return the machine to
> a point before the problem started. If you're unsure how
> to do this, click Start / Help and look for help on System
> Restore.
>
>
> "Yosh" <Yosh@discussions.microsoft.com> wrote in message
> news:AF0B7805-7EDF-4BDD-BF5A-1B39074E20DF@microsoft.com...
> >I tried bur since the CMD was not working the command line sfc.exe did not
> > work.
> >
> >
> > "Pegasus (MVP)" wrote:
> >
> >> It sounds as if your command processor is corrupted. Try a
> >> System File Check by doing this:
> >> - Click Start / Run
> >> - Type sfc.exe /scannow {OK}
> >>
> >> "Yosh" <Yosh@discussions.microsoft.com> wrote in message
> >> newsEAAA3E8-258F-4A3E-A28D-6048D78582AF@microsoft.com...
> >> > Now I have tried both normal and safe modes and starting CMD by typing
> >> > c:\windows\system32\cmd.exe {Enter}
> >> >
> >> > Both results are the same and What I got was the message:
> >> > "The application failed to initialize properly (0xc0000142). Click on
> >> > OK
> >> > to
> >> > terminate the application."
> >> >
> >> >
> >> >
> >> > "Pegasus (MVP)" wrote:
> >> >
> >> >> You press F8 repeatedly during the early boot phase, then
> >> >> select Safe Mode from the menu you see.
> >> >>
> >> >>
> >> >> "Yosh" <Yosh@discussions.microsoft.com> wrote in message
> >> >> news:EC9D4022-ECB0-4779-8B5A-42E5170E440F@microsoft.com...
> >> >> > Pegasus,
> >> >> >
> >> >> > Thanks for your suggestion.
> >> >> > Could you tell me how to got into the Safe Mode?
> >> >> >
> >> >> >
> >> >> >
> >> >> > "Pegasus (MVP)" wrote:
> >> >> >
> >> >> >>
> >> >> >> "Yosh" <Yosh@discussions.microsoft.com> wrote in message
> >> >> >> news:CC6E260F-EE04-43BB-AE49-BB4F6263E750@microsoft.com...
> >> >> >> >I cannot open CMD. A box appears and it says, "The application
> >> >> >> >failed
> >> >> >> >to
> >> >> >> > initialize properly (0xc0000142). Click on OK to terminate the
> >> >> >> > application."
> >> >> >>
> >> >> >> There are several ways to open a Command Prompt. You
> >> >> >> need to tell us which method you use. In the meantime do
> >> >> >> this:
> >> >> >> - Click Start, then Run
> >> >> >> - Type this: c:\windows\system32\cmd.exe {Enter}
> >> >> >> - Report the result.
> >> >> >> - Try the same in Safe Mode.
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>

 

[HeyBub]

Yosh wrote:
> I cannot open CMD. A box appears and it says, "The application failed
> to initialize properly (0xc0000142). Click on OK to terminate the
> application."

Try the alias: "COMMAND"

 

[Ken Blake, MVP]

On Sun, 12 Aug 2007 17:34:09 -0500, "HeyBub" <heybub@gmail.com> wrote:

> Yosh wrote:
> > I cannot open CMD. A box appears and it says, "The application failed
> > to initialize properly (0xc0000142). Click on OK to terminate the
> > application."
>
> Try the alias: "COMMAND"


"Command" is *not* an alias for "CMD." They are two different
programs.

--
Ken Blake, Microsoft MVP Windows - Shell/User
Please Reply to the Newsgroup

 

[davensocal]

Hi All-
I am having the same issue as described here..

Win XP Pro, SP2, IBM T60, English and Japanese Lang support

Cmd.exe, ping.exe, and unknown other console apps will not open in normal or
safe modes. WinXP reports Application failed to initialize, click to close
the application 0xc0000142 (or something close to that)

In addition, I discovered that I cannot edit the fonts for cmd.exe, if I
select the font tab in the right click>properties menu, it kills the
explorer, and Dr. Watson Post mortem.

We ruled out corruption of the two exe files by replacing them with known
good copies.

Registry rollback has no affect on this issue.

One thing that occured before this issue.. I needed to install something
that used batch files with sleep commands. WinXP does not support sleep
commands, and I didn't want to root out all of the batch files for editing,
so I installed Srvr2003 Resource Kit. After installation, I was able to use
cmd.exe and sleep commands. Approx 48 hrs later, this issue was found.

Any ideas? This is a preload system, so I do not have the original CD
available as Yosh did in this chain.

I will attempt scan disk.. any insight would be greatly appreciated.. I
REALLY don't want to start over on this box (and there are no other issues
that I am aware of)

Thanks!

Dave.

 

[trogers]

Just so that the MS people know, I also am having this problem. (Win XP
SP2.) It is not just Dave. My Dell D620 (Core Duo) was working fine on
Friday, and today (Monday), this showed up. No new software installed except
a new McAfee virus definition file. Note: I also have both English and
Japanese language support on this system, so maybe that's a clue (and then
again, maybe not).
-Thomas

"davensocal" wrote:

>
> Hi All-
> I am having the same issue as described here..
>
> Win XP Pro, SP2, IBM T60, English and Japanese Lang support
>
> Cmd.exe, ping.exe, and unknown other console apps will not open in normal or
> safe modes. WinXP reports Application failed to initialize, click to close
> the application 0xc0000142 (or something close to that)
>
> In addition, I discovered that I cannot edit the fonts for cmd.exe, if I
> select the font tab in the right click>properties menu, it kills the
> explorer, and Dr. Watson Post mortem.
>
> We ruled out corruption of the two exe files by replacing them with known
> good copies.
>
> Registry rollback has no affect on this issue.
>
> One thing that occured before this issue.. I needed to install something
> that used batch files with sleep commands. WinXP does not support sleep
> commands, and I didn't want to root out all of the batch files for editing,
> so I installed Srvr2003 Resource Kit. After installation, I was able to use
> cmd.exe and sleep commands. Approx 48 hrs later, this issue was found.
>
> Any ideas? This is a preload system, so I do not have the original CD
> available as Yosh did in this chain.
>
> I will attempt scan disk.. any insight would be greatly appreciated.. I
> REALLY don't want to start over on this box (and there are no other issues
> that I am aware of)
>
> Thanks!
>
> Dave.

 

[davensocal]

Thomas-
Well, Glad to know I am not the <i>only</i> one!
Does your system also crash Explorer if you try to edit the fonts of the CMD
window?
Programs>Accessories> Right click on "Command Prompt", select properties.
Go to font tab. Mine dies at that point.


I did find out that I get my console apps back after switching default
unicode language back to English..

Settings>control panel>Regional and Language Options
Select Advanced Tab.
Select English from drop down for ".. Non Unicode programs.."

I haven't tried returning mine to Japanese for this setting.. Normally when
I switch back and forth, it reloads some files, so maybe it will rewrite the
corrupt files?

 

[davensocal]

Also posted here... By me of course

http://www.microsoft.com/windowsxp/...f66774721da&cat=&lang=en&cr=US&sloc=en-us&p=1

 

[davensocal]

Solution found (dumb luck)

Hi All-
In my case, problem is solved..

XP SP2, configured for English and Japanese. Language option for
"non-unicode" programs set to Japanese.

I switched back to English for this setting, and the CMD prompt came back.
Switched back to Japanese, and it still works. I have to guess that one of
the fonts was corrupted..

Hope this helps others..

 

[priji]

There are several ways to open a Command Prompt. You
need to tell us which method you use. In the meantime do
this:
- Click Start, then Run
- Type this: c:\windows\system32\cmd.exe {Enter}
- Report the result.
- Try the same in Safe Mode.

 

[trogers]

Yes. Explorer crashes if I try to open either the Font or the Layout tabs.
I also switched my default unicode language back to English (which it was
already set at), and that seems to have solved the problem. I set it to UK
English, then back to US English to force the reload of US English. I also
forced it to reinstall from media, rather than use existing files. All is
much better now. Thanks for your help!
-Thomas

"davensocal" wrote:

>
> Thomas-
> Well, Glad to know I am not the <i>only</i> one!
> Does your system also crash Explorer if you try to edit the fonts of the CMD
> window?
> Programs>Accessories> Right click on "Command Prompt", select properties.
> Go to font tab. Mine dies at that point.
>
>
> I did find out that I get my console apps back after switching default
> unicode language back to English..
>
> Settings>control panel>Regional and Language Options
> Select Advanced Tab.
> Select English from drop down for ".. Non Unicode programs.."
>
> I haven't tried returning mine to Japanese for this setting.. Normally when
> I switch back and forth, it reloads some files, so maybe it will rewrite the
> corrupt files?
>
>

 

[davensocal]

Looks like my issue is solved by switching non-unicode default language from
Japanese to English.. I switched back to Japanese and they still work..

So I guess the font theory was a good one!

Hope this helps..

 

[SJ]

RE: Solution found (dumb luck) hoho

My case is just a little bit different.
'noon-unicode' is already set to 'English', but I once set it to Korean.

I changed back to Korean, and it worked.
I am concerning if I am able to change back to English.
The ugly Sage software forces me to do so.








"davensocal" wrote:

> Hi All-
> In my case, problem is solved..
>
> XP SP2, configured for English and Japanese. Language option for
> "non-unicode" programs set to Japanese.
>
> I switched back to English for this setting, and the CMD prompt came back.
> Switched back to Japanese, and it still works. I have to guess that one of
> the fonts was corrupted..
>
> Hope this helps others..