Re: "NET NOT RECOGNIZED AS A COMMAND" et al
- From: "Pegasus \(MVP\)" <I.can@xxxxxxx>
- Date: Mon, 1 Oct 2007 19:03:48 +0200
<bill@xxxxxxxxxx> wrote in message
news:ls82g3psdo6acg2j8tg1pil3vqrf9bg0md@xxxxxxxxxx
I got this issue and error when trying to execute a NET STOP command
to fix the update not working issue.
"NET NOT RECOGNIZED AS A COMMAND"
OK so I know what the problem is - the PATH isn't working.
I have verified that, BUT the PATH variable appears correct and I
re-entered it.
I was able to type the long path command and it works
C:\WINDOWS\SYSTEM32\NET STOP ....
If I type %systemroot% I get back C:\WINDOWS not recognized as a
command.
So the system knows what %systemroot% is
the first item in PATH=%systemroot%\system32;.........
NET.EXE is in system32
BUT typing NET STOP at the command prompt gets me the error.
Even if I open the cmd prompt in the system32 folder I get the same
error.
everything works the same if I rename notepad.exe to test.exe and type
TEST.
WHY & How to fix pplleeaasseeeee.
Some of the items you report appear contradictory. However, the
usual cause for this problem is an invalid value type for the %path%
variable. I assume that your path shows up as
%systemroot%\system32;......... at the Command Prompt, which
is wrong. It should show up as
c:\windows\system32;........
Have a look at the value
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\Path
I suspect it is a Reg_SZ value. It should be a Reg_Expand_SZ value.
.
- Follow-Ups:
- Re: "NET NOT RECOGNIZED AS A COMMAND" et al
- From: bill
- Re: "NET NOT RECOGNIZED AS A COMMAND" et al
- References:
- "NET NOT RECOGNIZED AS A COMMAND" et al
- From: bill
- "NET NOT RECOGNIZED AS A COMMAND" et al
- Prev by Date: Re: Can't Run Any Microsoft Office 2007 Application
- Next by Date: How to configure a 2nd SCSI SATA drive?
- Previous by thread: "NET NOT RECOGNIZED AS A COMMAND" et al
- Next by thread: Re: "NET NOT RECOGNIZED AS A COMMAND" et al
- Index(es):
Relevant Pages
|
