Discussion Locked

CMD.exe error

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have windows 2000 and Service Pack 2 installed, IE 5.5 w/ SP. When executing DOS prompt I keep receiveing Program error CMD.EXE and the window closing not allowing me to be to a command prompt. Does anyone else have this problem. Would it have anything to due with LAN Desk? I really need help on this.
-Bob

7 replies

by jedzone

try typing c:\winnt\cmd.exe. This is a fix not what the problem is. I think there are path problems to the CMD file.

by dmiles

The command prompt menu item is on the Accessroies sub-menu in Win2K,type
cmd
In the Run box to open a command prompt window

by stockmaker1

This is where I am getting the error, I also get the same error by clicking on the DOS Prompt icon under start-programs-accessories. The DOS box appears then about 5 seconds later, I get the CMD.exe error and the windows close down on me.

by buffalodan

Yoiu give no indication what the error being returned says, the exact error message would be helpful. question for you, have you attempted to locate the file...cmd.exe?

Can you run cmd.exe from Start>Run dialog box?

And I highly doubt landesk had anything at all to do with this problem.

Possibly a policy was implemented, have you configured multiple accts on this wkst? Log in as administrator or equivalent and try executing this command.

Good Luck....

by stockmaker1

I can execute cmd from Start>Run it opens the DOS box and after about 5-7 second it shuts down giving me the following error.
"Program error" no code given, "cmd.exe has generated errors and will be closed by windows, you will need to restart the program."

There is no other accounts on this PC, and I have local admin rights on the machine....

by dgod40

Hey Bud, I just had the exact same problem. Its a real problem when you are trying to use the PING utility. The only solution I found was to find another computer with W2K and copy cmd.exe onto a floppy and then onto my hard drive. I think it has something to do with that filthy service pack.

This discussion is closed to new replies.