Manually installing Win XP SP3. So I used MSConfig to do a clean boot.
Install SP3 [no errors]. Reboot. Let the system finish off it's stuff. Open
MSConfig and re-enable everything. Reboot.

Some services do not start up. They don't even show up in MSConfig but are
listed in the Services applet. In MSConfig, if you go back to the "normal"
settings and reboot, the services are still disabled and MSConfig is still in
selective mode. In the Services applet, you can't start them.

Of note that most services do start up but a few didn't. In this one the
anti-virus [Avast managed] did not. Can't even uninstall. Gives me an error.

Did a system restore to get back to where I was. Not even sure uninstalling
SP3 would of helped.

I've seen this happen once before with SP3 and MSConfig. In that case, it
wasn't the anti-virus that didn't load.

"Gis Bun" <(E-Mail Removed)> wrote in message
news:B967A554-E9BD-4F01-B8DA-(E-Mail Removed)...
> Manually installing Win XP SP3. So I used MSConfig to do a clean boot.
> Install SP3 [no errors]. Reboot. Let the system finish off it's [its?]
> stuff. Open
> MSConfig and re-enable everything. Reboot.
>
> Some services do not start up. They don't even show up in MSConfig but are
> listed in the Services applet. In MSConfig, if you go back to the "normal"
> settings and reboot, the services are still disabled and MSConfig is still
> in
> selective mode. In the Services applet, you can't start them.
>
> Of note that most services do start up but a few didn't. In this one the
> anti-virus [Avast managed] did not. Can't even uninstall. Gives me an
> error.
>
> Did a system restore to get back to where I was. Not even sure
> uninstalling
> SP3 would of [have?] helped.
>
> I've seen this happen once before with SP3 and MSConfig. In that case, it
> wasn't the anti-virus that didn't load.

You need to be a little more specific. You write, for example:
- "Some services do not start up". Which ones?
- "Some services do not start up" and "you can't start them" but you
never tell us what happens when you do attempt to start them.
- "It wasn't the anti-virus that didn't load." If it wasn't, what was it?

Gis

You're probably misusing Mscofig, which is intended for use as a
troubleshooting tool.

You would normally configure a Sevice by selecting Start, Control
Panel, Administrative Tools, Services and right clicking on the Service
to changethe StartUp type.

You can also use Autoruns to manage what loads when the computer is
booted.

A safer way than msconfig to disable / remove unwanted start up items is
to use Autoruns.
http://www.microsoft.com/technet/sys.../Autoruns.mspx

With Autoruns you can uncheck an item, which disables it from starting,
or you can can right click an item and then delete it. If you uncheck
you can recheck to re-enable the item. It is a much safer approach than
editing the Registry. Another useful feature of the programme is that
you can right click an item and select Search Online to get information
about the item selected.

Why are you tinkering with StartUp items? You can mess things up if you
fail to take dependencies into account. Using Msconfig leaves you
unaware of dependencies.


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Gis Bun wrote:
> Manually installing Win XP SP3. So I used MSConfig to do a clean boot.
> Install SP3 [no errors]. Reboot. Let the system finish off it's
> stuff. Open MSConfig and re-enable everything. Reboot.
>
> Some services do not start up. They don't even show up in MSConfig
> but are listed in the Services applet. In MSConfig, if you go back to
> the "normal" settings and reboot, the services are still disabled and
> MSConfig is still in selective mode. In the Services applet, you
> can't start them.
>
> Of note that most services do start up but a few didn't. In this one
> the anti-virus [Avast managed] did not. Can't even uninstall. Gives
> me an error.
>
> Did a system restore to get back to where I was. Not even sure
> uninstalling SP3 would of helped.
>
> I've seen this happen once before with SP3 and MSConfig. In that
> case, it wasn't the anti-virus that didn't load.

To enable or disable services go to: Start/Run: services.msc

--

All the Best and Happy Holidays,
Kelly (MS-MVP/DTS&XP)

Taskbar Repair Tool Plus!
http://www.kellys-korner-xp.com/taskbarplus!.htm


"Gis Bun" <(E-Mail Removed)> wrote in message
news:B967A554-E9BD-4F01-B8DA-(E-Mail Removed)...
> Manually installing Win XP SP3. So I used MSConfig to do a clean boot.
> Install SP3 [no errors]. Reboot. Let the system finish off it's stuff.
> Open
> MSConfig and re-enable everything. Reboot.
>
> Some services do not start up. They don't even show up in MSConfig but are
> listed in the Services applet. In MSConfig, if you go back to the "normal"
> settings and reboot, the services are still disabled and MSConfig is still
> in
> selective mode. In the Services applet, you can't start them.
>
> Of note that most services do start up but a few didn't. In this one the
> anti-virus [Avast managed] did not. Can't even uninstall. Gives me an
> error.
>
> Did a system restore to get back to where I was. Not even sure
> uninstalling
> SP3 would of helped.
>
> I've seen this happen once before with SP3 and MSConfig. In that case, it
> wasn't the anti-virus that didn't load.
>
>

For all, see http://support.microsoft.com/kb/310353 [parts 2.2, 2.3 and 2.4
are required]

Using MsConfig *NOT* to permanently stop services but to disable not needed
services during the SP3 install. This normally reduces any chance of
conflicts.

I have installed SP3 on probably over 50 systems with not 1 issue except this.

By disabling all non-MS services, there should be no conflicts.

Others have recommended this method as well.


"Gis Bun" wrote:

> Manually installing Win XP SP3. So I used MSConfig to do a clean boot.
> Install SP3 [no errors]. Reboot. Let the system finish off it's stuff. Open
> MSConfig and re-enable everything. Reboot.
>
> Some services do not start up. They don't even show up in MSConfig but are
> listed in the Services applet. In MSConfig, if you go back to the "normal"
> settings and reboot, the services are still disabled and MSConfig is still in
> selective mode. In the Services applet, you can't start them.
>
> Of note that most services do start up but a few didn't. In this one the
> anti-virus [Avast managed] did not. Can't even uninstall. Gives me an error.
>
> Did a system restore to get back to where I was. Not even sure uninstalling
> SP3 would of helped.
>
> I've seen this happen once before with SP3 and MSConfig. In that case, it
> wasn't the anti-virus that didn't load.
>
>

Which don't start up? All the Avast anti-virus services.

The Start button in services.msc is grayed out for those that can't start.

Safe mode doesn't help.

MSConfig tells me I can't start the services because I'm not an
administrator of the PC but I am. But even logged in as a domain
administrator doesn't help.

"Pegasus (MVP)" wrote:

>
> "Gis Bun" <(E-Mail Removed)> wrote in message
> news:B967A554-E9BD-4F01-B8DA-(E-Mail Removed)...
> > Manually installing Win XP SP3. So I used MSConfig to do a clean boot.
> > Install SP3 [no errors]. Reboot. Let the system finish off it's [its?]
> > stuff. Open
> > MSConfig and re-enable everything. Reboot.
> >
> > Some services do not start up. They don't even show up in MSConfig but are
> > listed in the Services applet. In MSConfig, if you go back to the "normal"
> > settings and reboot, the services are still disabled and MSConfig is still
> > in
> > selective mode. In the Services applet, you can't start them.
> >
> > Of note that most services do start up but a few didn't. In this one the
> > anti-virus [Avast managed] did not. Can't even uninstall. Gives me an
> > error.
> >
> > Did a system restore to get back to where I was. Not even sure
> > uninstalling
> > SP3 would of [have?] helped.
> >
> > I've seen this happen once before with SP3 and MSConfig. In that case, it
> > wasn't the anti-virus that didn't load.
>
> You need to be a little more specific. You write, for example:
> - "Some services do not start up". Which ones?
> - "Some services do not start up" and "you can't start them" but you
> never tell us what happens when you do attempt to start them.
> - "It wasn't the anti-virus that didn't load." If it wasn't, what was it?
>
>
>

Gis Bun

If your computer is not starting normally, or if you receive errors when
you start your computer that you cannot identify, you could consider
performing a "clean boot." This operation starts the computer by using a
minimal set of drivers and startup programs. This can help you
troubleshoot the problem.
Quote from: http://support.microsoft.com/kb/310353

The process is to determine which start up item is causing the error.

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Gis Bun wrote:
> For all, see http://support.microsoft.com/kb/310353 [parts 2.2, 2.3
> and 2.4 are required]
>
> Using MsConfig *NOT* to permanently stop services but to disable not
> needed services during the SP3 install. This normally reduces any
> chance of conflicts.
>
> I have installed SP3 on probably over 50 systems with not 1 issue
> except this.
>
> By disabling all non-MS services, there should be no conflicts.
>
> Others have recommended this method as well.
>
>
> "Gis Bun" wrote:
>
>> Manually installing Win XP SP3. So I used MSConfig to do a clean
>> boot. Install SP3 [no errors]. Reboot. Let the system finish off
>> it's stuff. Open MSConfig and re-enable everything. Reboot.
>>
>> Some services do not start up. They don't even show up in MSConfig
>> but are listed in the Services applet. In MSConfig, if you go back
>> to the "normal" settings and reboot, the services are still disabled
>> and MSConfig is still in selective mode. In the Services applet, you
>> can't start them.
>>
>> Of note that most services do start up but a few didn't. In this one
>> the anti-virus [Avast managed] did not. Can't even uninstall. Gives
>> me an error.
>>
>> Did a system restore to get back to where I was. Not even sure
>> uninstalling SP3 would of helped.
>>
>> I've seen this happen once before with SP3 and MSConfig. In that
>> case, it wasn't the anti-virus that didn't load.