Missing Windows Command Prompt issue

Asked By 70 points N/A Posted on -
qa-featured

Hi,

I am not sure what happened to my computer. I don't know if this is a sort of a virus. When I typed cmd on run, nothing appears.

I opened the C:WINDOWSsystem32 and add cmd.exe to manually open it, I waited for few minutes for it to appear but it doesn't.

All I can see on the location of cmd is a space between two .dll registry files.

 

My system is running normally and has no signs of any virus, spyware or malware attack, but to make it sure, I run my Norton 360 and scanned the whole system, but found 0 infections.

I go back to the location of cmd from C, and notice the space between the 2 .dll files, thinking if I accidentally deleted the cmd on its location.

Anyway, I want to know how I can fix this, because cmd is one of the major features of windows. My operating system is Windows XP Home Edition with Intel Core 2 Duo.

I don't have any recovery or installation disk with me so, I really can't figure out what to do with it.

How can I recover my missing command prompt? Or how can I create a new cmd?

I am seeking for assistance.

I hope someone here can help.

Thanks.

SHARE
Best Answer by Gill Bros
Best Answer
Best Answer
Answered By 200 points N/A #125653

Missing Windows Command Prompt issue

qa-featured

An alternative way to enter the Command Line Interface (CLI)

There are two available options in our Microsoft Windows Operating system to enter the Command Line Interface (CLI). The major application for this is the CMD.EXE and the original command line since Microsoft Operating system is in Text Based Interface is the COMMAND.COM.

There are some Viruses and worms that prevent CMD.EXE from running in windows environment. The major reason is to prevent the user from manual deletion of the virus code and infections. CMD.EXE is the most powerful tool in our Microsoft Windows systems. By the use of this application, you can manually remove the attributes of the files and folders. Deleting protected files by the virus. Inside the CMD.EXE you can show hidden files without editing the settings on Windows Explorer. You can also repair your windows using the CMD.EXE by scheduling CHKDSK to run during start-up. You can also modify your registry settings or keys without using the registry editor.

If it is true that your computer is virus-free and no virus found during the virus scan, your CMD.EXE might be corrupted or you are prevented by your administrator to run the CMD.EXE. You may contact your administrator to turn-on or to unrestrict you from running CMD.EXE.

If it is corrupted, you can run your Windows Recovery Disk or your installation disk and run the recovery option so that it will replace those corrupted files and folders.

In the case that you don’t have the installation disk, you may download the CMD.EXE on the internet and replace the CMD.EXE you have. CMD.EXE is located in your windows system32 folder (C:WINDOWSSYSTEM32). Or, you may have a copy from your friend’s computer. Get a USB drive and ask permission from your friend to copy the CMD.EXE from his computer to your USB drive. Then on your computer or operating system windows system32 folder, delete the CMD.EXE before copying from your USB Drive. Deletion is important do not overwrite.

An alternative to enter the Command Prompt or the Command Line Interface (CLI) is by running the COMMAND.COM. Running COMMAND.COM is just the same with running the CMD.EXE.

  1. Click start then Run. Run dialog appears
  2. On the run input box, type COMMAND.COM
  3. Click OK.

Sometimes running CHKDSK will fix the issue in corrupted files. Just run the CHKDSK under the COMMAND.COM and add the parameter /F to fix error on the disk and with the parameter /R which locates bad sectors and recover the readable information from your disk drive.

COMMAND.COM and CMD.EXE are both the same in nature but they are different in accessibility. CMD.EXE is in Windows NT platform while the COMMAND.COM is in old DOS (Disk Operating System) platform. COMMAND.COM is more likely in DOS operating system, COMMAND.COM looks for CONFIG.SYS as the configuration start-up and AUTOEXEC.BAT to run programs or application when started. CMD.EXE uses CONFIG.NT for configuration files and variables during start-up and AUTOEXEC.NT for the automatic running of programs or application when start-up.

Any of the two can be use for command prompt or the so called Command Line Interface (CLI).

Answered By 70 points N/A #125654

Missing Windows Command Prompt issue

qa-featured

This comment has a lot of important message to remember. Thanks Gill Bros for sharing those information. You are the best and so with techyv.

Login/Register to Answer

Related Questions