Question Locked

CMD won't work!

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

I have Windows XP and I am not able to open cmd.
Whenever I try to, it gives me the message "Another program is currently using this file".
I've used cmd before and I do not know why this is happening.

12 replies

by gary56789

Would strongly suggest you run spyware/virus checkers which are currently updated.

Another possibility, is that the c:\windows\system32\cmd.exe file is corrupted for some other reason, in which case it will need to be reinstalled.

by waldemar axdorph

How do you open cmd?

Do you use WINDOWS + R > cmd
or
WINDOWS + R > command
?

I would search for spyware and adware and perhaps virus.

Many wishes!

Waldemar Axdorph

by sidharthgowtham84

The possible reason for this problem is the file cmd.exe would have been corrupted.
try using the repair option from your windows XP cd to reinstall the cmd.exe file.

by robaaaaaa2

Can you run Regedit or msconfig?

Malware often renames, deletes, or locks these three to defend itself.

by jjarvis

Check your path and make sure C:\windows\system32 is in it. Go to your system properties (Windows key + Pause/Break) go to the advanced tab, Click Environment variables, Find PATH in the System variables section and see if it contains C:\windows\system32. Also not sure if this is related but there is a ComSpec variable that is pointing to %SystemRoot%\system32\cmd.exe

by sp-admin

I am also have problem in cmd. start run and type cmd system automatically restarted . Anti virus updated .

Replay to saravananias@hotmail.com

by desktop veteran

This issue can exist when the path statement has been modified (usually) by the installation of some software that has to modify the path statement. If the change puts anything in front of the %SystemRoot% and %SystemRoot%\System32 entries in the path statement, trying to launch the CMD.EXE file will result in an attempt to try and find the file in location mentioned at the begining of the path statement. This is particularly true with IBM. They are responsible for my first hand knowledge of this situation. Thanks IBM (I think).

by merlin the wiz

DO an Advanced search (Make sure to check the hidden files and folders option.)for Cmd.exe It should show four files CMD.exe-xxxxxx.pf in the windows prefetch folder @17KB, cmd.exe in the %systempath%(usually Windows)\system32 folder @380KB, cmd.exe in the %systempath%\system32
\dllcache folder @380KB and evntcmd.exe in the dams folder @ 24KB. This is WinXP Home Edition.
If you do not get the same results from your search, either you the file had been corrupted or you have a virus.

WwinXP Pro usually has the same file structure for the older system commands.

by martha dibblee

start, run, type command.com & press return

this will open a DOS shell window.

in the window, at the prompt, type cd\ which will get you the c:> prompt.

by timothy j. bruce

While the appearance of these programs are the same (a command-line tool) their functionality is significantly different. COMMAND.COM is a 16-bit application which shares the 16-bit address space. Since it's in the 16-bit space (and is shared with all other applications in the 16-bit space), in "bad" program can crash it (the environment).

Using CMD.EXE results in a program that runs in a separate memory space completely. You can run multiple copies of CMD.EXE and there is nothing shared by them, so any application problems are isolated to that running application.

Tim

This discussion is closed to new replies.