How To Fix Startup Files That Do Not Startup?

The files that are expected to run in the startup section of msconfig do not
always start up all the files. I have run registry cleaners, etc. yet the
problem persists. I must start up these orphaned files manually after a
system restart.

Does anyone have any suggestions on how this might be remedied? Thanks.

MH

On Wed, 23 May 2007 11:40:01 -0700, mbhinz
<mbhinz@discussions.microsoft.com> wrote:

>The files that are expected to run in the startup section of msconfig do not
>always start up all the files. I have run registry cleaners, etc. yet the
>problem persists. I must start up these orphaned files manually after a
>system restart.
>
>Does anyone have any suggestions on how this might be remedied? Thanks.



I can't help with your problem, but I urge you to avoid running
registry cleaners. They may possibly have exacerbated your problem.

I strongly recommend *against* the routine use of registry cleaners.
Routine cleaning of the registry isn't needed and is dangerous. Leave
the registry alone and don't use any registry cleaner. Despite what
many people think, and what vendors of registry cleaning software try
to convince you of, having unused registry entries doesn't really hurt
you.

The risk of a serious problem caused by a registry cleaner erroneously
removing an entry you need is far greater than any potential benefit
it may have.


--
Ken Blake, Microsoft MVP Windows - Shell/User
Please Reply to the Newsgroup

Try Autoruns from the MS Windows SysInternals site:
http://www.microsoft.com/technet/sys.../Autoruns.mspx
This will show all apps/etc. that load/run when you first boot/logon and
selectively allow you to stop any that you don't want.
If the program or programs are not listed by AutoRuns then chances are you
have some registry entries missing.

JS

"mbhinz" <mbhinz@discussions.microsoft.com> wrote in message
news26025EA-E09D-4872-8F58-F2AF0DCFDDBD@microsoft.com...
> The files that are expected to run in the startup section of msconfig do
> not
> always start up all the files. I have run registry cleaners, etc. yet the
> problem persists. I must start up these orphaned files manually after a
> system restart.
>
> Does anyone have any suggestions on how this might be remedied? Thanks.
>
> MH

Try Autoruns from the MS Windows SysInternals site:
http://www.microsoft.com/technet/sys.../Autoruns.mspx
This will show all apps/etc. that load/run when you first boot/logon and
selectively allow you to stop any that you don't want.
If the program or programs are not listed by AutoRuns then chances are you
have some registry entries missing.

JS

"mbhinz" <mbhinz@discussions.microsoft.com> wrote in message
news26025EA-E09D-4872-8F58-F2AF0DCFDDBD@microsoft.com...
> The files that are expected to run in the startup section of msconfig do
> not
> always start up all the files. I have run registry cleaners, etc. yet the
> problem persists. I must start up these orphaned files manually after a
> system restart.
>
> Does anyone have any suggestions on how this might be remedied? Thanks.
>
> MH

mbhinz wrote:
> The files that are expected to run in the startup section of msconfig
> do not always start up all the files. I have run registry cleaners,
> etc. yet the problem persists. I must start up these orphaned files
> manually after a system restart.
>
> Does anyone have any suggestions on how this might be remedied?
> Thanks.
>
> MH

GADS!!

--
--
How to Post a newsgroup
question effectively:
http://support.microsoft.com/kb/q555375

"mbhinz" wrote
> The files that are expected to run in the startup section of msconfig do
> not
> always start up all the files. I have run registry cleaners, etc. yet the
> problem persists. I must start up these orphaned files manually after a
> system restart.
>
> Does anyone have any suggestions on how this might be remedied? Thanks.

What, exactly, isn't starting consistently?

Without knowing more, one possible solution is to enter the services snap
in, from Start | Run | Services.msc | Ok. Then disable one or both of these
below listed two services. Disable one, test. If that doesn't do it,
enable that one and disable the other, test again. If no go, disable both
of them:

SSDP Discovery Service
UPnP Service

Most users don't need these services so there is normally no downside to
disabling them. For info on these services see this link:
http://www.blackviper.com/WinXP/service411.htm

On a final note, I concur with what Ken said. Do not use a registry
cleaner. There is a greater chance it will create a problem than fix one.
Unused (orphaned) entries in the registry, do not as a rule cause problems,
but removing the wrong item can.

--
Rock [MS-MVP User/Shell]