msconfig does not start from console

  • Thread starter Thread starter Andy
  • Start date Start date
A

Andy

It's been awhile, but I thought I could run msconfig from a console, but it does not start.

The binaries are here.

C:\WINDOWS\pchealth\helpctr\binaries

C:\WINDOWS\system32\dllcache
 
It's been awhile, but I thought I could run msconfig from a
console, but it does not start.

The binaries are here.

C:\WINDOWS\pchealth\helpctr\binaries

C:\WINDOWS\system32\dllcache
Click to expand...

Works for me. Just type "msconfig" at the prompt.
 
Nil said:
Works for me. Just type "msconfig" at the prompt.
Click to expand...

C: <--- probably already at C:
cd \WINDOWS\pchealth\helpctr\binaries <--- since executable not in %path%
msconfig <--- run from current working dir

Then it works for me. From Command Prompt (cmd.exe).

Even if I'm in some other current working directory, I managed
to get it to run using an absolute path.

C:\WINDOWS\pchealth\helpctr\binaries\msconfig

*******

And for some reason, Start : Run : msconfig
works without a fuss. No absolute path
or anything. So for some reason, on my system,
the %path% in Command Prompt, is different
than what Start : Run appears to be using.

Well, it's a computer. It's supposed to
do weird stuff :-)

Paul
 
C: <--- probably already
at C: cd \WINDOWS\pchealth\helpctr\binaries <--- since
executable not in %path% msconfig
<--- run from current working dir

Then it works for me. From Command Prompt (cmd.exe).

Even if I'm in some other current working directory, I managed
to get it to run using an absolute path.

C:\WINDOWS\pchealth\helpctr\binaries\msconfig
Click to expand...

Not sure what you're saying here, but my command prompt is at my
profile's Desktop when I issue the command "msconfig". No changing
directories needed. You're right, it doesn't seem to be in the path,
but it pops up anyway. I guess the executable is found via some
reference in the Registry to its location.
Well, it's a computer. It's supposed to
do weird stuff :-)
Click to expand...

It's only doing what somebody told it to do!
 
Paul said:
C: <--- probably already at C:
cd \WINDOWS\pchealth\helpctr\binaries <--- since executable not in %path%
msconfig <--- run from current working dir

Then it works for me. From Command Prompt (cmd.exe).

Even if I'm in some other current working directory, I managed
to get it to run using an absolute path.

C:\WINDOWS\pchealth\helpctr\binaries\msconfig

*******

And for some reason, Start : Run : msconfig
works without a fuss. No absolute path
or anything. So for some reason, on my system,
the %path% in Command Prompt, is different
than what Start : Run appears to be using.

Well, it's a computer. It's supposed to
do weird stuff :-)
Click to expand...

[HKLM\Software\Microsoft\Windows\CurrentVersion\App
Paths\msConfig.exe]

[for me] the WinNT Command Interpreter does not parse 'App
Paths', while WinExplorer does look there in addition to looking
under "Path" paths.

So, same behaviour for for example [msInfo32.exe] /et cetera/ .

If 'Nil', or others, can also start "Help and Support Center"
from the CLI prompt without using an absolute path it seems there
must be some way to enhance [Cmd.exe] to also parse 'App Paths'.
 
Back
Top