MSConfig Fails in SP3

[Patrick Moloney]

I am unable to run MSConfig or IPConfig. These seem to be disabled since
installing SP3 at 5/26/08. The files look like they are there:
\winnt\pchealth\helpctr\binaries\msconfig.exe
\winnt\servicepackfiles\i386\msconfig.exe

file is version 5512.

Sometimes the command window blinks briefly. I have tried executing from
the file without success. Other programs like regedit do work.

I don't think this is a virus. Any ideas on cause or how to proceed?

 

[Pegasus \(MVP\)]

I am unable to run MSConfig or IPConfig. These seem to be disabled since
installing SP3 at 5/26/08. The files look like they are there:
\winnt\pchealth\helpctr\binaries\msconfig.exe
\winnt\servicepackfiles\i386\msconfig.exe

file is version 5512.

Sometimes the command window blinks briefly. I have tried executing from
the file without success. Other programs like regedit do work.

I don't think this is a virus. Any ideas on cause or how to proceed?

When you run ipconfig.exe from the Run box then you deprive yourself of the
opportunity to see the error messages. You should do this instead:
- Click Start / Run / cmd {OK}
- Type these commands:
ipconfig{Enter}
%SystemRoot%\pchealth\helpctr\binaries\msconfig.exe{Enter}

 

[db ´¯`·.. >]

most of the time you can
gain control via safemode and
by holding the f8 key while
to system powers up.

--------------------

however, my first suggestion
would be to un install your anti
virals, at least temporarily during
your analysis.

sometimes they can be the
cause of the problem.


secondly, I would run a
check disk on the system
drive.

you can find the option on
the second tab when you
right click on the drive and
select properties.

then see if you have regain
control of your system.

if not then you should go directly
here and run a full scan:

http://onecare.live.com/site/en-US/article/registry_cleaner_why.htm

and if the above still doesn't
help, then perhaps you should
uninstall sp3 via add/remove
programs, at least temporarily.

--

db·´¯`·...¸><)))º>
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

 

[Pegasus \(MVP\)]

most of the time you can gain control via safemode and by holding the f8
key while to system powers up.

however, my first suggestion would be to un install your anti-
virals, at least temporarily during your analysis.
sometimes they can be the cause of the problem.


secondly, I would run a check disk on the system drive.

you can find the option on the second tab when you
right click on the drive and select properties.
then see if you have regain control of your system.
if not then you should go directly here and run a full scan:

http://onecare.live.com/site/en-US/article/registry_cleaner_why.htm

and if the above still doesn't help, then perhaps you should
uninstall sp3 via add/remove programs, at least temporarily.

db·´¯`·...¸><)))º>
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

If you are a retired IT professional then you should know from your working
life that the first step in such cases is to gather information.
Uninstalling anti-virus programs, running chkdsk or removing SP3, if at all,
will come much later when the facts are known. Taking these steps
prematurely can cause a lot of damage.

 

[db ´¯`·.. >]

there are always other
options to exercise and
ascertaining more information
would be helpful but not
always necessary.

the suggestions I provided
would be the ones I would
take myself.

it is the process of elimination
and peeling away third party
programs would be a step
towards achieving a stable
windows, like it was designed
to be.

thanks for your input

your suggestion was also a useful
one, thus I didn't post anything
bad about your helpful technique.

--

db·´¯`·...¸><)))º>
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

 

[Pegasus \(MVP\)]

there are always other options to exercise and
ascertaining more information would be helpful but not
always necessary.

This is precisely what the surgeon said after removing the patient's kidney,
although the patient was suffering from appendicitis.

your suggestion was also a useful one, thus I didn't post anything
bad about your helpful technique.

Do you sometimes post bad things about other people's contributions? Would
you care to give us an example of a "bad thing" that you post?

 

[db ´¯`·.. >]

well, if a doctor removed
a kidney then it was likely
poisoning the body.

however, you have already
diagnose the true cause of
the suffering as being
appendicitis.

if you know more than a
doctor does, then you ought
to be in another business
because you simply know
too much for your own
good.


I stand by my suggestions
so don't troll upon me with
your smart a** remarks,
ol' wing-ed mule.




--

db·´¯`·...¸><)))º>
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

 

[Pegasus \(MVP\)]

I stand by my suggestions
so don't troll upon me with
your smart a** remarks,
ol' wing-ed mule.

Showing your feathers?

 

[db ´¯`·.. >]

if msconfig fails to launch in
the usual manner, e.g.

start>run>msconfig

why would launching msconfig
from a cmd window fix the problem?

also why would typing %SystemRoot%
prove more successful than directly
clicking on the files the op mentioned
and located in \winnt?

your suggestion to utilize the command
window is a work-a-round and not
solution.

--

db·´¯`·...¸><)))º>
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

 

[Pegasus \(MVP\)]

if msconfig fails to launch in the usual manner, e.g.

start>run>msconfig

why would launching msconfig from a cmd window fix the problem?

The OP reported a "brief blink". Running the command from a Console screen
will make any error message permanently visible. This won't fix the problem
but seeing the error message is essential for the subsequent fixing effort.