CMD doesn't recognize commands from run dialoge box - error

Whenever I open up the cmd using start>run>cmd, it never allows me to run a command (it will say for e.g. that 'taskmgr' is not recognized as an external or internal command).

However, when I navigate to "C:\Windows\System32\cmd.exe" it will allow me to run any command including taskmgr. So in short, my cmd doesn't work right if I use the shortcut start>run>cmd.

I believe it may have to due with opening up in 'C:\Users\Chris' but I am not sure.

Here are two images for your reference:

Attachment 196416

Attachment 196417

richc46 said:

Welcome
Be happy that your computer is working as it should
The system CMD is called an elevated prompt and has full authority
The Chris prompt is limited
Many commands from Chris are not suppose to work as a protective measure, only the elevated prompt will work in those situations.
An administrators password is needed for the elevated prompt
Elevated Command Prompt

How come when I used 'start>run>cmd' before my commands used to work. Now they don't. I know this for sure. It's not that I don't have rights because, then, wouldn't the error code say, "System 5 Error Access Denied". In this case, the cmd is not reading the commands properly. I am guessing that by putting in just 'cmd', it starts off in the wrong directory, hence is not able to read commands by their executable names. (e.g. taskmgr, calc, notepad, etc.)

I just would like to know a fix for this since having to go to my desktop is now the fastest way to open the cmd.

I want to be able to run commands in my cmd by using "start>run>type in 'cmd' and hit enter" for anyone who is clueless reading this post.

Do any commands work in the command prompt?

I helped someone else with a similar problem earlier this week who could not even type exit to exit the command prompt. ipconfig and ping commands should also be recognized in either elevated or normal mode.

Golden said:

Hi,

Rich is 100% correct - the reason is the differnt states of elevation of the CMD prompt.

Your best bet is to pin the CMD command to your taskbar, and then hold SHIFT+CONTROL+ALT and click the pinned CMD icon : this will open the CMD window in the elevated state.

Regards,
Golden

It is running as an elevated command prompt. See the Administrator: at the top of the windows. Thanks for the info, It'll come of use later but right now I am not looking for a 'hotfix'.

richc46 said:

If you are giving correct information, the computer was not working the way that it should have, before. It would not show an error, it just would not take the command. It has happened to me. I recognize the cause, go to an elevated prompt and it works.
This may help make your like easier:
Elevated Command Prompt Shortcut

Everything worked before, and notice, it is running as an elevated command prompt. See the 'Administrator:' at the top of cmd window in picture.

writhziden said:

Do any commands work in the command prompt?

I helped someone else with a similar problem earlier this week who could not even type exit to exit the command prompt. ipconfig and ping commands should also be recognized in either elevated or normal mode.

Well, the only commmands that work are commands like exit, cd, start. however, when I navigate to the system32 by using cd\windows\system32 in the problem ridden cmd, all the commands work.

Another user from hackforums has suggested that the problem has to do with my environmental variables. Here is his post, all credit goes to Polymath 1.0 on hackforums.net. I am simply using this as a reference to see if your approve/disprove his answer.

Polymath 1.0' pid='19631089' dateline='1328281905 said:

It is because the environment path variables that the command line cmd interpreter parses to resolve the location of an external process hasn't been set. Rather than navigating to the folder you could get around it by specifying the path to the process explicitly to the CLI command interpreter. In your example you could use %windir%\System32\Taskmgr as %windir% is just such an environment variable that resolves to C:\Windows and the subfolder System32 is where taskmgr.exe resides. Another system variable %COMSPEC% + enter if typed into the Search or Run dialogue box will open a cmd prompt in Windows\System32. So when the command window was open you could then simply type the name of any process in System32 and it would work without errors as there is no unresolved path.

A nice feature of Vista and Windows 7 is that in any Windows Explorer folder view if you press Shift + Right Click you open a secondary context menu with an open Command prompt here which saves you navigating via the command line. Additionally if you press Shift + Crtl + Right Click on that Command prompt here item it opens as an elevated Administrative command process.

Take care

It is likely due to your environment variables. Here is what I suggest:

1. Click Start Menu
2. Type sysdm.cpl into the Search programs and files (do not hit enter)
3. Right click sysdm.cpl and select Run as administrator
4. Go to Advanced
5. Click Environment Variables...
6. Double click Path from the System Variables list (after scrolling down)
7. Select everything in the box Variable Value:
8. Hit CTRL + X to cut the values, leaving it blank (you may have to put a space in), and hit OK.
9. Hit OK again to close Environment Variables to reset the Path to nothing.
10. Now, click Environment Variables... again.
11. Double click Path in System Variables (after scrolling down again)
12. Paste the values back into the path Variable Value by hitting CTRL + V.

Does command prompt work after the above process?

If not, do steps 1-8, but use CTRL + C instead of CTRL + X (do not leave the path blank this time in other words), and paste the path in your next post. You may be missing important variables.

writhziden said:

It is likely due to your environment variables. Here is what I suggest:

1. Click Start Menu
2. Type sysdm.cpl into the Search programs and files (do not hit enter)
3. Right click sysdm.cpl and select Run as administrator
4. Go to Advanced
5. Click Environment Variables...
6. Double click Path from the System Variables list (after scrolling down)
7. Select everything in the box Variable Value:
8. Hit CTRL + X to cut the values, leaving it blank (you may have to put a space in), and hit OK.
9. Hit OK again to close Environment Variables to reset the Path to nothing.
10. Now, click Environment Variables... again.
11. Double click Path in System Variables (after scrolling down again)
12. Paste the values back into the path Variable Value by hitting CTRL + V.

Does command prompt work after the above process?

If not, do steps 1-8, but use CTRL + C instead of CTRL + X (do not leave the path blank this time in other words), and paste the path in your next post. You may be missing important variables.

Didn't work, and all I have in Path is

Code:

;C:\Program Files\Java\jdk1.7.0\bin

Lol Froob said:

writhziden said:

It is likely due to your environment variables. Here is what I suggest:

1. Click Start Menu
2. Type sysdm.cpl into the Search programs and files (do not hit enter)
3. Right click sysdm.cpl and select Run as administrator
4. Go to Advanced
5. Click Environment Variables...
6. Double click Path from the System Variables list (after scrolling down)
7. Select everything in the box Variable Value:
8. Hit CTRL + X to cut the values, leaving it blank (you may have to put a space in), and hit OK.
9. Hit OK again to close Environment Variables to reset the Path to nothing.
10. Now, click Environment Variables... again.
11. Double click Path in System Variables (after scrolling down again)
12. Paste the values back into the path Variable Value by hitting CTRL + V.

Does command prompt work after the above process?

If not, do steps 1-8, but use CTRL + C instead of CTRL + X (do not leave the path blank this time in other words), and paste the path in your next post. You may be missing important variables.

Didn't work, and all I have in Path is

Code:

;C:\Program Files\Java\jdk1.7.0\bin

Replace your path with:

Code:

%SYSTEMROOT%\System32;%SYSTEMROOT%;%SYSTEMROOT%\System32\wbem;C:\Program Files\Java\jdk1.7.0\bin

Does the command prompt now accept the normal commands?