Windows Bluetooth (v2) patch toasts XP Pro

Having auto-updates on was the death of our server (in a peer to peer config
really).
Fri AM came in and XP was in a BSOD loop. Fine. Finally got it working by
doing a
system restore for a few days back from the update. Should have left it
there. At the end of the day I decided (since it seemed like an important
update) to re-try the install. Big mistake. Well, now no amount of system
restore points will bring it out of the BSOD state. My dumb mistake for
thinking that something would work twice
(safe mode is still useable . Tomorrow (Mon) I'll go access the damage. I
see nothing short of a long annoying re-install here but figured I'd ask to
see if anyone has any ideas. BTW: None of the other 6 computers choked on
this upgrade. One possible issue is that the .net ver 1.1 installer had been
damaged (?) prior to this upgrade. Couldn't re-install nor un-install 1.1
prior to this (Yes an issue I was planning on tackling at "sometime") though
the one program (that I know of) that relied on it worked just fine.
PS Sorry about the cross post (it's also in XP help and support) but
couldn't find a way to edit orig post...

Are you running WinXP SP2 or WinXP SP3?

What other updates had been installed recently (i.e., just before the BSODs
started; e.g., WinXP SP3)?

Did you install the re-released version of MS08-030/KB951376 via Windows
Update or Automatic Updates?

===================================
For home users, no-charge support is available by calling 1-866-PCSAFETY in
the United States and in Canada or by contacting your local Microsoft
subsidiary. There is no-charge for support calls that are associated with
security updates. When you call, clearly state that your problem is related
to a Security Update and cite the update's KB number (e.g., KB951376).

For more information about how to contact your local Microsoft subsidiary
for security update support issues, visit the International Support Web
site: http://support.microsoft.com/common/international.aspx

For enterprise customers, support for security updates is available through
your usual support contacts.

Start a free Windows Update support incident request:
https://support.microsoft.com/oas/de...spx?gprid=6527

Support for Windows Update:
http://support.microsoft.com/gp/wusupport
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin; DTS-L.net


jeffkrol wrote:
> Having auto-updates on was the death of our server (in a peer to peer
> config
> really).
> Fri AM came in and XP was in a BSOD loop. Fine. Finally got it working by
> doing a
> system restore for a few days back from the update. Should have left it
> there. At the end of the day I decided (since it seemed like an important
> update) to re-try the install. Big mistake. Well, now no amount of system
> restore points will bring it out of the BSOD state. My dumb mistake for
> thinking that something would work twice
> (safe mode is still useable . Tomorrow (Mon) I'll go access the damage.
> I
> see nothing short of a long annoying re-install here but figured I'd ask
> to
> see if anyone has any ideas. BTW: None of the other 6 computers choked on
> this upgrade. One possible issue is that the .net ver 1.1 installer had
> been
> damaged (?) prior to this upgrade. Couldn't re-install nor un-install 1.1
> prior to this (Yes an issue I was planning on tackling at "sometime")
> though
> the one program (that I know of) that relied on it worked just fine.
> PS Sorry about the cross post (it's also in XP help and support) but
> couldn't find a way to edit orig post...

"PA Bear [MS MVP]" wrote:

> Are you running WinXP SP2 or WinXP SP3?
SP# loaded approx 1 month ago
>
> What other updates had been installed recently (i.e., just before the BSODs
> started; e.g., WinXP SP3)?
Did update an HP printer program. An update to the printer software updater
>
> Did you install the re-released version of MS08-030/KB951376 via Windows
Both versions were present. The June 10th one caused no problems. v2 did.
> Update or Automatic Updates?
First instance of loading v2 was an unattended automated update Fri night.
Second attempt was from Windows update. Same crash but now it's
unrecoverable using "system restore". Tomorrow I'll pull the HP program and
see if this helps. Never was crazy about HP programming..
>
> ===================================
> For home users, no-charge support is available by calling 1-866-PCSAFETY in
> the United States and in Canada or by contacting your local Microsoft
> subsidiary. There is no-charge for support calls that are associated with
> security updates. When you call, clearly state that your problem is related
> to a Security Update and cite the update's KB number (e.g., KB951376).
>
> For more information about how to contact your local Microsoft subsidiary
> for security update support issues, visit the International Support Web
> site: http://support.microsoft.com/common/international.aspx
>
> For enterprise customers, support for security updates is available through
> your usual support contacts.
>
> Start a free Windows Update support incident request:
> https://support.microsoft.com/oas/de...spx?gprid=6527
>
> Support for Windows Update:
> http://support.microsoft.com/gp/wusupport
> --
> ~Robear Dyer (PA Bear)
> MS MVP-Windows (IE, OE, Security, Shell/User)
> AumHa VSOP & Admin; DTS-L.net
>
>
> jeffkrol wrote:
> > Having auto-updates on was the death of our server (in a peer to peer
> > config
> > really).
> > Fri AM came in and XP was in a BSOD loop. Fine. Finally got it working by
> > doing a
> > system restore for a few days back from the update. Should have left it
> > there. At the end of the day I decided (since it seemed like an important
> > update) to re-try the install. Big mistake. Well, now no amount of system
> > restore points will bring it out of the BSOD state. My dumb mistake for
> > thinking that something would work twice
> > (safe mode is still useable . Tomorrow (Mon) I'll go access the damage.
> > I
> > see nothing short of a long annoying re-install here but figured I'd ask
> > to
> > see if anyone has any ideas. BTW: None of the other 6 computers choked on
> > this upgrade. One possible issue is that the .net ver 1.1 installer had
> > been
> > damaged (?) prior to this upgrade. Couldn't re-install nor un-install 1.1
> > prior to this (Yes an issue I was planning on tackling at "sometime")
> > though
> > the one program (that I know of) that relied on it worked just fine.
> > PS Sorry about the cross post (it's also in XP help and support) but
> > couldn't find a way to edit orig post...
>
>

Oopps SP3 as you may have figured out..

"jeffkrol" wrote:

>
>
> "PA Bear [MS MVP]" wrote:
>
> > Are you running WinXP SP2 or WinXP SP3?
> SP# loaded approx 1 month ago
> >
> > What other updates had been installed recently (i.e., just before the BSODs
> > started; e.g., WinXP SP3)?
> Did update an HP printer program. An update to the printer software updater
> >
> > Did you install the re-released version of MS08-030/KB951376 via Windows
> Both versions were present. The June 10th one caused no problems. v2 did.
> > Update or Automatic Updates?
> First instance of loading v2 was an unattended automated update Fri night.
> Second attempt was from Windows update. Same crash but now it's
> unrecoverable using "system restore". Tomorrow I'll pull the HP program and
> see if this helps. Never was crazy about HP programming..
> >
> > ===================================
> > For home users, no-charge support is available by calling 1-866-PCSAFETY in
> > the United States and in Canada or by contacting your local Microsoft
> > subsidiary. There is no-charge for support calls that are associated with
> > security updates. When you call, clearly state that your problem is related
> > to a Security Update and cite the update's KB number (e.g., KB951376).
> >
> > For more information about how to contact your local Microsoft subsidiary
> > for security update support issues, visit the International Support Web
> > site: http://support.microsoft.com/common/international.aspx
> >
> > For enterprise customers, support for security updates is available through
> > your usual support contacts.
> >
> > Start a free Windows Update support incident request:
> > https://support.microsoft.com/oas/de...spx?gprid=6527
> >
> > Support for Windows Update:
> > http://support.microsoft.com/gp/wusupport
> > --
> > ~Robear Dyer (PA Bear)
> > MS MVP-Windows (IE, OE, Security, Shell/User)
> > AumHa VSOP & Admin; DTS-L.net
> >
> >
> > jeffkrol wrote:
> > > Having auto-updates on was the death of our server (in a peer to peer
> > > config
> > > really).
> > > Fri AM came in and XP was in a BSOD loop. Fine. Finally got it working by
> > > doing a
> > > system restore for a few days back from the update. Should have left it
> > > there. At the end of the day I decided (since it seemed like an important
> > > update) to re-try the install. Big mistake. Well, now no amount of system
> > > restore points will bring it out of the BSOD state. My dumb mistake for
> > > thinking that something would work twice
> > > (safe mode is still useable . Tomorrow (Mon) I'll go access the damage.
> > > I
> > > see nothing short of a long annoying re-install here but figured I'd ask
> > > to
> > > see if anyone has any ideas. BTW: None of the other 6 computers choked on
> > > this upgrade. One possible issue is that the .net ver 1.1 installer had
> > > been
> > > damaged (?) prior to this upgrade. Couldn't re-install nor un-install 1.1
> > > prior to this (Yes an issue I was planning on tackling at "sometime")
> > > though
> > > the one program (that I know of) that relied on it worked just fine.
> > > PS Sorry about the cross post (it's also in XP help and support) but
> > > couldn't find a way to edit orig post...
> >
> >

Assuming you've been able to install other updates successfully after having
installed SP3 approx 1 month ago, your best best would be to open a free
support incident about this, Jeff. Let us know how things work out, please.
--
~PA Bear

jeffkrol wrote:
> Oopps SP3 as you may have figured out..
>
>>> Are you running WinXP SP2 or WinXP SP3?
>> SP# loaded approx 1 month ago
>>>
>>> What other updates had been installed recently (i.e., just before the
>>> BSODs started; e.g., WinXP SP3)?
>> Did update an HP printer program. An update to the printer software
>> updater
>>>
>>> Did you install the re-released version of MS08-030/KB951376 via Windows
>> Both versions were present. The June 10th one caused no problems. v2 did.
>>> Update or Automatic Updates?
>> First instance of loading v2 was an unattended automated update Fri
>> night.
>> Second attempt was from Windows update. Same crash but now it's
>> unrecoverable using "system restore". Tomorrow I'll pull the HP program
>> and
>> see if this helps. Never was crazy about HP programming..
>>>
>>> ===================================
>>> For home users, no-charge support is available by calling 1-866-PCSAFETY
>>> in the United States and in Canada or by contacting your local Microsoft
>>> subsidiary. There is no-charge for support calls that are associated
>>> with
>>> security updates. When you call, clearly state that your problem is
>>> related to a Security Update and cite the update's KB number (e.g.,
>>> KB951376).
>>>
>>> For more information about how to contact your local Microsoft
>>> subsidiary
>>> for security update support issues, visit the International Support Web
>>> site: http://support.microsoft.com/common/international.aspx
>>>
>>> For enterprise customers, support for security updates is available
>>> through your usual support contacts.
>>>
>>> Start a free Windows Update support incident request:
>>> https://support.microsoft.com/oas/de...spx?gprid=6527
>>>
>>> Support for Windows Update:
>>> http://support.microsoft.com/gp/wusupport
>>> --
>>> ~Robear Dyer (PA Bear)
>>> MS MVP-Windows (IE, OE, Security, Shell/User)
>>> AumHa VSOP & Admin; DTS-L.net
>>>
>>>
>>> jeffkrol wrote:
>>>> Having auto-updates on was the death of our server (in a peer to peer
>>>> config
>>>> really).
>>>> Fri AM came in and XP was in a BSOD loop. Fine. Finally got it working
>>>> by
>>>> doing a
>>>> system restore for a few days back from the update. Should have left it
>>>> there. At the end of the day I decided (since it seemed like an
>>>> important
>>>> update) to re-try the install. Big mistake. Well, now no amount of
>>>> system
>>>> restore points will bring it out of the BSOD state. My dumb mistake for
>>>> thinking that something would work twice
>>>> (safe mode is still useable . Tomorrow (Mon) I'll go access the
>>>> damage.
>>>> I
>>>> see nothing short of a long annoying re-install here but figured I'd
>>>> ask
>>>> to
>>>> see if anyone has any ideas. BTW: None of the other 6 computers choked
>>>> on
>>>> this upgrade. One possible issue is that the .net ver 1.1 installer had
>>>> been
>>>> damaged (?) prior to this upgrade. Couldn't re-install nor un-install
>>>> 1.1
>>>> prior to this (Yes an issue I was planning on tackling at "sometime")
>>>> though
>>>> the one program (that I know of) that relied on it worked just fine.
>>>> PS Sorry about the cross post (it's also in XP help and support) but
>>>> couldn't find a way to edit orig post...

Will try that. hopefully it will work out better than the last one I
reported. Did you see my ntldr question by any chance?
I could have probably reformatted (which is what the last advice was) till
the cows came home Anyways in that incident, restoring the orig ntldr from
my xp cd worked, even tough it was pre sp2, sp3 ect.

"PA Bear [MS MVP]" wrote:

> Assuming you've been able to install other updates successfully after having
> installed SP3 approx 1 month ago, your best best would be to open a free
> support incident about this, Jeff. Let us know how things work out, please.
> --
> ~PA Bear
>
> jeffkrol wrote:
> > Oopps SP3 as you may have figured out..
> >
> >>> Are you running WinXP SP2 or WinXP SP3?
> >> SP# loaded approx 1 month ago
> >>>
> >>> What other updates had been installed recently (i.e., just before the
> >>> BSODs started; e.g., WinXP SP3)?
> >> Did update an HP printer program. An update to the printer software
> >> updater
> >>>
> >>> Did you install the re-released version of MS08-030/KB951376 via Windows
> >> Both versions were present. The June 10th one caused no problems. v2 did.
> >>> Update or Automatic Updates?
> >> First instance of loading v2 was an unattended automated update Fri
> >> night.
> >> Second attempt was from Windows update. Same crash but now it's
> >> unrecoverable using "system restore". Tomorrow I'll pull the HP program
> >> and
> >> see if this helps. Never was crazy about HP programming..
> >>>
> >>> ===================================
> >>> For home users, no-charge support is available by calling 1-866-PCSAFETY
> >>> in the United States and in Canada or by contacting your local Microsoft
> >>> subsidiary. There is no-charge for support calls that are associated
> >>> with
> >>> security updates. When you call, clearly state that your problem is
> >>> related to a Security Update and cite the update's KB number (e.g.,
> >>> KB951376).
> >>>
> >>> For more information about how to contact your local Microsoft
> >>> subsidiary
> >>> for security update support issues, visit the International Support Web
> >>> site: http://support.microsoft.com/common/international.aspx
> >>>
> >>> For enterprise customers, support for security updates is available
> >>> through your usual support contacts.
> >>>
> >>> Start a free Windows Update support incident request:
> >>> https://support.microsoft.com/oas/de...spx?gprid=6527
> >>>
> >>> Support for Windows Update:
> >>> http://support.microsoft.com/gp/wusupport
> >>> --
> >>> ~Robear Dyer (PA Bear)
> >>> MS MVP-Windows (IE, OE, Security, Shell/User)
> >>> AumHa VSOP & Admin; DTS-L.net
> >>>
> >>>
> >>> jeffkrol wrote:
> >>>> Having auto-updates on was the death of our server (in a peer to peer
> >>>> config
> >>>> really).
> >>>> Fri AM came in and XP was in a BSOD loop. Fine. Finally got it working
> >>>> by
> >>>> doing a
> >>>> system restore for a few days back from the update. Should have left it
> >>>> there. At the end of the day I decided (since it seemed like an
> >>>> important
> >>>> update) to re-try the install. Big mistake. Well, now no amount of
> >>>> system
> >>>> restore points will bring it out of the BSOD state. My dumb mistake for
> >>>> thinking that something would work twice
> >>>> (safe mode is still useable . Tomorrow (Mon) I'll go access the
> >>>> damage.
> >>>> I
> >>>> see nothing short of a long annoying re-install here but figured I'd
> >>>> ask
> >>>> to
> >>>> see if anyone has any ideas. BTW: None of the other 6 computers choked
> >>>> on
> >>>> this upgrade. One possible issue is that the .net ver 1.1 installer had
> >>>> been
> >>>> damaged (?) prior to this upgrade. Couldn't re-install nor un-install
> >>>> 1.1
> >>>> prior to this (Yes an issue I was planning on tackling at "sometime")
> >>>> though
> >>>> the one program (that I know of) that relied on it worked just fine.
> >>>> PS Sorry about the cross post (it's also in XP help and support) but
> >>>> couldn't find a way to edit orig post...
>
>

"PA Bear [MS MVP]" wrote:

> Assuming you've been able to install other updates successfully after having
> installed SP3 approx 1 month ago, your best best would be to open a free
> support incident about this, Jeff. Let us know how things work out, please.
> --
> ~PA Bear
>

MAJOR UPDATE:
After fighting w/ a re-install today (nothing was working)I finally had to
surrender. Decided to break down the RAID array and put one of the drives in
an external box.
LOW AND BEHOLD.. what did I see on the MB?
BAD, BAD blowing out CAPACITORS... I though this "problem" was rectified
years ago (board is Only 4 yrs old ). I swaer I lost about 4 MB's due to
this issue. With that in mind it is no wonder XP became toast (though I'm
not sure that was the entire issue) Anyways it was a disaster waiting to
happen...... Now I need to get that SATA box and see IF the HD's file system
is in tact.
Only lost a wee bit of data so far due to some good planning and a pile of
luck.
Now back to my ntldr issue