Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Hi. I just discovered my cmd.exe got problems
.I run using from start then run and type cmd
However i notice tat comands like ipconfig, chkdsk and etc are not reconizged at all ?
Whats wrong ? thanks for help

So you're opening a Command Window by cmd and then entering ipconfig? What error do you get after pressing the Enter key?
Life's more painless for the brainless.

I think he meant Command prompt not cmd.exe. Command prompt lets you run all that in a command prompt window.
i_XpUser

XPUser
"Command Prompt" is what it's called (because that's what it produces) and the program file itself is cmd.exe so differentiating between the two is unimportant to this post. Along similar lines is the "System Information Facility" using msconfig.exeshinigaimi
What we need to is know is whether nothing whatsoever happens or if there are error messages? Do you even get the little black DOS Screen? Maybe some commands have gone missing.DerekW

well set path command shows this C:\Documents and Settings\Skynet>set path
Path=%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\PROGRA~1\D
ISKEE~1\DISKEE~2\
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSHwell it is the cmd.exe i type cmd at the start, run there, for cmds such as ipconfig, chkdsk it would says
C:\Documents and Settings\Skynet>ipconfig
'ipconfig' is not recognized as an internal or external command,
operable program or batch file.However if i type those cmds at the start run, it will run normally.. Why ??

Okay, what about
set systemrootIf it responds with either of these two lines:
Environment variable systemroot not defined
systemroot=
Then respond with these 2 lines:
set systemroot=c:\windows
for /f "delims=" %a in ('@echo %path%') do set path=%a
If commands start to work, let me know.
Edit: Actually, seeing as I might not be around here for a while, I might as well just get on with my solution.IF (and only if) the above commands worked to restored cmd, type this in (while they're still working):
reg add "hklm\software\microsoft\windows nt\currentversion" /v SystemRoot /t REG_SZ /d c:\windowsThat should allow commands to work after you reboot.

set systemroot does work however the command
(set systemroot=c:\windows
for /f "delims=" %a in ('@echo %path%') do set path=%a) shows a message(C:\Documents and Settings\Skynet>set path=c:\windows\system32 c:\windows c:\wind
ows\System32\Wbem C:\PROGRA~1\DISKEE~1\DISKEE~2\)i tried the last command too but it is not recongized in the cmd.exe prompt but it works if i type the command at the run.It prompts me wether to overwrite anot.Well i chose yes but no changes too after reboot .....
Edit: Well i change set systemroot=c:\windows\system32\
since i guess the main cmd.exe and all main cmds are inside.. well and it finally works is wat i like to say
but when i restart it go backs to the same old problem..why ? :(
BTW the last command i overwrited in the cmd.exe what does it do actually ?

Maybe, but the command gives me what I need to give you a working PATH, even if it is screwed up.
In your System Properties dialog box, there's an Advanced tab. In that tab is a button called Environment Variables. In the Environment Variables dialog is a System Variables section. In that listbox, there should be Path. Replace whatever's there with this: c:\windows\system32;c:\windows;c:\wind
ows\System32\Wbem;C:\PROGRA~1\DISKEE~1\DISKEE~2If there's a PATH variable in the User variables section, get rid of it.
If that fixes everything, great. Otherwise, there's something going on behind the scenes, and actively sabotaging your computer's environment. Try a virus and malware scan, but no guarantees that the virus won't block the scans.

![]() |
Raid 1 Hard Drive Failure...
|
XP vs Vista
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |