svchost issue

Did I read somewhere that MS will incorporate all the fixes to the svchost
issue in the next patch release (next week)? No need to download WSUS 3.0
separately.
I haven't run the May updates on my XP system yet.

My strategy has always to wait at least a week before installing updates (I
have "Notify Only" selected except for Defender) and monitor sites such as
this for issues. I got into that habit a few years back after some McAfee
fiascos. I also only use Windows Update not MS Update.

Grampy,

Are you administering a network ? If not, WSUS 3.0 has nothing to do
with the svchost 'fix'; it's the Windows Update Agent 3.0 client that is
being pushed out in stages :
http://mowgreen.castlecops.com/archi...ost_issue.html

MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============


Grampy wrote:

> Did I read somewhere that MS will incorporate all the fixes to the svchost
> issue in the next patch release (next week)? No need to download WSUS 3.0
> separately.
> I haven't run the May updates on my XP system yet.
>
> My strategy has always to wait at least a week before installing updates (I
> have "Notify Only" selected except for Defender) and monitor sites such as
> this for issues. I got into that habit a few years back after some McAfee
> fiascos. I also only use Windows Update not MS Update.

Sorry, I got it wrong.
I am administering my own desktop system.

Repeating my question correctly:

Did I read somewhere that MS will incorporate all the fixes to the svchost
issue in the next patch release (next week)? No need to download Window
Update Agent 3.0 separately.
I haven't run the May updates on my XP system yet.

My strategy has always to wait at least a week before installing updates (I
have "Notify Only" selected except for Defender) and monitor sites such as
this for issues. I got into that habit a few years back after some McAfee
fiascos. I also only use Windows Update not MS Update.

Thanks for the help.



"MowGreen [MVP]" wrote:

> Grampy,
>
> Are you administering a network ? If not, WSUS 3.0 has nothing to do
> with the svchost 'fix'; it's the Windows Update Agent 3.0 client that is
> being pushed out in stages :
> http://mowgreen.castlecops.com/archi...ost_issue.html
>
> MowGreen [MVP 2003-2007]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
> Grampy wrote:
>
> > Did I read somewhere that MS will incorporate all the fixes to the svchost
> > issue in the next patch release (next week)? No need to download WSUS 3.0
> > separately.
> > I haven't run the May updates on my XP system yet.
> >
> > My strategy has always to wait at least a week before installing updates (I
> > have "Notify Only" selected except for Defender) and monitor sites such as
> > this for issues. I got into that habit a few years back after some McAfee
> > fiascos. I also only use Windows Update not MS Update.
>

There are 2 "fixes" for WinXP machines: The first has been "pushed" by
Automatic Updates and has been available at Windows Update since 22 May-07;
the second will be "pushed" by Automatic Updates and offered at Windows
Update by the middle of Jun-07, not necessarily on Patch Tuesday (12
Jun-07).

>>> I haven't run the May updates on my XP system yet.

IMHO that is NOT a wise decision, Grampy.
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin; DTS-L.org


Grampy wrote:
> Sorry, I got it wrong.
> I am administering my own desktop system.
>
> Repeating my question correctly:
>
> Did I read somewhere that MS will incorporate all the fixes to the svchost
> issue in the next patch release (next week)? No need to download Window
> Update Agent 3.0 separately.
> I haven't run the May updates on my XP system yet.
>
> My strategy has always to wait at least a week before installing updates
> (I
> have "Notify Only" selected except for Defender) and monitor sites such as
> this for issues. I got into that habit a few years back after some McAfee
> fiascos. I also only use Windows Update not MS Update.
>
> Thanks for the help.
>
>
>
> "MowGreen [MVP]" wrote:
>
>> Grampy,
>>
>> Are you administering a network ? If not, WSUS 3.0 has nothing to do
>> with the svchost 'fix'; it's the Windows Update Agent 3.0 client that is
>> being pushed out in stages :
>> http://mowgreen.castlecops.com/archi...ost_issue.html
>>
>> MowGreen [MVP 2003-2007]
>> ===============
>> *-343-* FDNY
>> Never Forgotten
>> ===============
>>
>>
>> Grampy wrote:
>>
>>> Did I read somewhere that MS will incorporate all the fixes to the
>>> svchost
>>> issue in the next patch release (next week)? No need to download WSUS
>>> 3.0
>>> separately.
>>> I haven't run the May updates on my XP system yet.
>>>
>>> My strategy has always to wait at least a week before installing updates
>>> (I have "Notify Only" selected except for Defender) and monitor sites
>>> such as this for issues. I got into that habit a few years back after
>>> some McAfee fiascos. I also only use Windows Update not MS Update.

PA Bear
Thanks for the information.

I understand what you mean about not being perhaps the wisest decision to
hold off on updates. It's a tradeoff of risks.

Grampy

"PA Bear" wrote:

> There are 2 "fixes" for WinXP machines: The first has been "pushed" by
> Automatic Updates and has been available at Windows Update since 22 May-07;
> the second will be "pushed" by Automatic Updates and offered at Windows
> Update by the middle of Jun-07, not necessarily on Patch Tuesday (12
> Jun-07).
>
> >>> I haven't run the May updates on my XP system yet.
>
> IMHO that is NOT a wise decision, Grampy.
> --
> ~Robear Dyer (PA Bear)
> MS MVP-Windows (IE, OE, Security, Shell/User)
> AumHa VSOP & Admin; DTS-L.org
>
>
> Grampy wrote:
> > Sorry, I got it wrong.
> > I am administering my own desktop system.
> >
> > Repeating my question correctly:
> >
> > Did I read somewhere that MS will incorporate all the fixes to the svchost
> > issue in the next patch release (next week)? No need to download Window
> > Update Agent 3.0 separately.
> > I haven't run the May updates on my XP system yet.
> >
> > My strategy has always to wait at least a week before installing updates
> > (I
> > have "Notify Only" selected except for Defender) and monitor sites such as
> > this for issues. I got into that habit a few years back after some McAfee
> > fiascos. I also only use Windows Update not MS Update.
> >
> > Thanks for the help.
> >
> >
> >
> > "MowGreen [MVP]" wrote:
> >
> >> Grampy,
> >>
> >> Are you administering a network ? If not, WSUS 3.0 has nothing to do
> >> with the svchost 'fix'; it's the Windows Update Agent 3.0 client that is
> >> being pushed out in stages :
> >> http://mowgreen.castlecops.com/archi...ost_issue.html
> >>
> >> MowGreen [MVP 2003-2007]
> >> ===============
> >> *-343-* FDNY
> >> Never Forgotten
> >> ===============
> >>
> >>
> >> Grampy wrote:
> >>
> >>> Did I read somewhere that MS will incorporate all the fixes to the
> >>> svchost
> >>> issue in the next patch release (next week)? No need to download WSUS
> >>> 3.0
> >>> separately.
> >>> I haven't run the May updates on my XP system yet.
> >>>
> >>> My strategy has always to wait at least a week before installing updates
> >>> (I have "Notify Only" selected except for Defender) and monitor sites
> >>> such as this for issues. I got into that habit a few years back after
> >>> some McAfee fiascos. I also only use Windows Update not MS Update.
>
>