View Full Version : Can't get msconfig to work
Xenomaniac
06-13-2005, 12:31 PM
I'm in Chicago visiting and I'm using my friends computer. His computer starts up a lot of programs when he turns is on. I just want to see how many programs are actually starting up when he turns it on. The only way I know how to do this is typing msconfig in the Run program under Start. Everytime I type it in I get "windows can not find the file." cmd, iexploer, and regedit work just fine but msconfig doesn't. Any suggestions?
oh almost forgot he is using winXP. That might help.
The Donut
06-13-2005, 12:32 PM
Operating System? :)
djnes
06-13-2005, 12:35 PM
Sounds like the PC might be Windows 2000, but as a suggestion, if you want help, at least give us the info that's needed.
Download a freeware app called StartUpCPL 2.8. I like it better than MSconfig, and it runs on all versions of Windows.
mgars
06-13-2005, 12:45 PM
yeah if if's 2000 that would be the problem,
you can also just download the msconfig utility (google it) and use it under 2000 if you don't want to go the other route
Xenomaniac
06-13-2005, 12:46 PM
ok here is the weird thing. I got it to work but you have to go to the directory to make it work. So you either go to C:\WINDOWS\PCHEALTH\HELPCTR\Binaries and open it up manualy, or you type that whole thing in plus adding msconfig.exe. Only way I could get it to work.
Oh and again its WinXP, I corrected myself in the first post.
HTPC Rookie
06-13-2005, 12:51 PM
right click on msconfig in C:\WINDOWS\PCHEALTH\HELPCTR\Binaries, copy it, paste it into your windows directory.
C:\WINDOWS\PCHEALTH\HELPCTR\Binaries is not in the path by default. the windows directory is.
djnes
06-13-2005, 12:57 PM
right click on msconfig in C:\WINDOWS\PCHEALTH\HELPCTR\Binaries, copy it, paste it into your windows directory.
C:\WINDOWS\PCHEALTH\HELPCTR\Binaries is not in the path by default. the windows directory is.
Not to burst your bubble, but that IS the correct path for it. That's where mine is located...and only there.
texuspete00
06-13-2005, 01:03 PM
^^ Uh not to bust your bubble, but you too have a funny setup then. Maybe installed some apps that moved it. When things are in the windows thing... er system32 or whatever it is, then you don't have to type any paths. That's what's normal, and that's what the poster was expecting. Sure it can be anywhere. I dunno... just seemed weird to be "busting bubbles." The post is really just about why something isn't working as expected. This is why. Is it home that's like this? I dunno... I'd sort it to what is generally considered normal.
HTPC Rookie
06-13-2005, 01:04 PM
If he does not want to type in " C:\WINDOWS\PCHEALTH\HELPCTR\Binaries\msconfig.exe", just "msconfig" in the Run box, he needs to put a copy into a directory that is in the default path.
Bubble is fine. ;)
Grimmda
06-13-2005, 01:07 PM
So it sounds like a "Path" problem:
Right click My Computer/Properties/Advanced Tab/Environment Variables button
Under "System Variables" scroll to where it says Path and make sure it has some of the following:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbe m;
If atleast those are there you could always add them, as they should probably be there.
There will probably be other things listed there but that's ok (for now)
HTPC Rookie
06-13-2005, 01:09 PM
So it sounds like a "Path" problem:
Right click My Computer/Properties/Advanced Tab/Environment Variables button
Under "System Variables" scroll to where it says Path and make sure it has some of the following:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbe m;
If atleast those are there you could always add them, as they should probably be there.
There will probably be other things listed there but that's ok (for now)
bingo. but rather than have someone screw with their path statement, it's easier and safer to just put a copy into a directory that is already in the path.
djnes
06-13-2005, 01:26 PM
^^ Uh not to bust your bubble, but you too have a funny setup then. Maybe installed some apps that moved it. When things are in the windows thing... er system32 or whatever it is, then you don't have to type any paths. That's what's normal, and that's what the poster was expecting. Sure it can be anywhere. I dunno... just seemed weird to be "busting bubbles." The post is really just about why something isn't working as expected. This is why. Is it home that's like this? I dunno... I'd sort it to what is generally considered normal.
You could take a step down off your soapbox for a second, and read Grimmda's post about path statements being incorrect. My install is not "funny" as you suggested, it's a default install. I've checked for this file on 6 separate XP machines, and that is where msconfig.exe is located. I'm not sure what you hoped to accomplish with your post, but facts are facts. That's where the file is located.
djnes
06-13-2005, 01:27 PM
bingo. but rather than have someone screw with their path statement, it's easier and safer to just put a copy into a directory that is already in the path.
It's easier and safer to add a line to the path section than add extra copies of system files around your system.
HTPC Rookie
06-13-2005, 01:32 PM
It's easier and safer to add a line to the path section than add extra copies of system files around your system.
No, it's not. Having multible copies of something like msconfig in different folders is not going to hurt a thing. Screw up your path statement, and all of a sudden a lot of critical stuff will cease to function.
msconfig is not a system file. it is a utility. delete a system file, something critical doesn't work. delete msconfig.exe, and only msconfig.exe stops working.
do it any way you want though, all I can do is suggest.
djnes
06-13-2005, 01:47 PM
No, it's not. Having multible copies of something like msconfig in different folders is not going to hurt a thing. Screw up your path statement, and all of a sudden a lot of critical stuff will cease to function.
msconfig is not a system file. it is a utility. delete a system file, something critical doesn't work. delete msconfig.exe, and only msconfig.exe stops working.
do it any way you want though, all I can do is suggest.
You won't be screwing up your path statement by adding a line...nitpicking about these things isn't worth it.
Also, what happens if the utility is patched or updated in a future service pack or hot fix? This is a system used by a person who requires help....so the OP would have to make yet another trip out there. When your supporting PCs for others, you try to make everything work transparent to the user...and to make it easier for you to manage change down the road. Path statement is the way to do this.
seanmcd
06-13-2005, 01:50 PM
you are ALL wrong. A real pc tech would go straight into the registry and pull things out of startup that way...
/me runs off
HTPC Rookie
06-13-2005, 01:54 PM
you are ALL wrong. A real pc tech would go straight into the registry and pull things out of startup that way...
/me runs off
LOL hey dines, something we can agree on? LOL
djnes
06-13-2005, 02:00 PM
LOL hey dines, something we can agree on? LOL
Absolutely. In fact, he's a braver man than I to muck around in the registry. I have to admit, that's my PC weakness.
Phoenix86
06-13-2005, 02:02 PM
bingo. but rather than have someone screw with their path statement, it's easier and safer to just put a copy into a directory that is already in the path.
This is a BAD solution. When a file is patched, it's only patched in the default location.
Pfft, if you're a "real" tech you wouldn't even need regedit. It wouldn't be hosed in the first place. :p
/runs and hides.
Xenomaniac
06-13-2005, 02:33 PM
Ok I checked the path by going to properties under My Computer. The path is fine and is exact word for word. I double checked 3 times. I think the best bet will be to move it, where exactly should I move it to? Should I put it in C:/windows ?
HTPC Rookie
06-13-2005, 02:34 PM
This is a BAD solution. When a file is patched, it's only patched in the default location.
Pfft, if you're a "real" tech you wouldn't even need regedit. It wouldn't be hosed in the first place. :p
/runs and hides.
AAAARRRGGHHHHH!!!!!! What's the worst that could happen...he'd fire off an older version of msconfig, one that works anyways??????!!!!!!
We're talking about someone that is wondering why msconfig's default location isn't in the default path anymore! Do you REALLY want him to change his path, or worse yet, play in the registry????
I give up!!!!!!!!!!!!!!!!
/runs and finds the valium. LOL
Phoenix86
06-13-2005, 02:50 PM
AAAARRRGGHHHHH!!!!!! What's the worst that could happen...he'd fire off an older version of msconfig, one that works anyways??????!!!!!!
We're talking about someone that is wondering why msconfig's default location isn't in the default path anymore! Do you REALLY want him to change his path, or worse yet, play in the registry????
I give up!!!!!!!!!!!!!!!!
/runs and finds the valium. LOL
Yes, it should be done in the registry or with a normal copy (proper path, version, etc.) of the file. No the system isn't going to be at risk or anything because of that file's use. However, it's a sloppy solution in genenral... Apply the solution to other files (hey if it worked once...) and you see where it could be a problem.
Will it work your way? Sure. Is there another better way that you can apply to *any* file/software? Yep.
He's learning msconfig, might as well learn regedit. HKLM/Software/Microsoft/Windows/Current Version/Run
Phoenix86
06-13-2005, 02:52 PM
Ok I checked the path by going to properties under My Computer. The path is fine and is exact word for word. I double checked 3 times. I think the best bet will be to move it, where exactly should I move it to? Should I put it in C:/windows ?
The path is correct and it's still not running?!?
If the path is working and it's in the proper location, moving to another pathed directory isn't going to help. Go to a command prompt. Type "path" and hit enter. Is the file pathed here?
Can you double click the file from an explorer view and it works?
maynard
06-13-2005, 02:58 PM
Try typing msconfig.exe instead of just msconfig.
I have seen someone with a similar problem with regedit and adding the .exe got it to work
m
Xenomaniac
06-13-2005, 02:58 PM
I can open it up no problem. The program it self runs fine. Typing in the command in the Run menu is the only thing that isn't working.
Try typing msconfig.exe instead of just msconfig.
I have seen someone with a similar problem with regedit and adding the .exe got it to work
m
Tried that before I posted on here. Tried it agian just in case and same shit.
maynard
06-13-2005, 03:00 PM
cross posting.
pigster
06-13-2005, 03:18 PM
He's learning msconfig, might as well learn regedit. HKLM/Software/Microsoft/Windows/Current Version/Run
What about HKCU/Software/Microsoft/Windows/Current Version/Run ? :p
vBulletin® v3.8.2, Copyright ©2000-2009, Jelsoft Enterprises Ltd.