KB942367 Problems

I found this on the microsoft.public.windowsupdate News Group today:


"The head of technical support at the Microsoft Telephone Support Center in
the Phillipines told me that the update KB942615 is Defective and Microsoft
Advisies Removing the update with your ADD/REMOVE PROGRAMS (don't forget to
click on show updates) and Disabling Automatic Updating on your computer so
that it does not try to reinstall this update automatically.

He does not know when the problem will be fixed. I hope that Microsoft
issues new updates and an apology letter very soon.

I hope that Microsoft fires their Quality Assurance Manager (if they even
have one.)"


Rich

"Rich" <Rich_NoSpam@ptd_nospam.net> wrote in message
news:...
>I found this on the microsoft.public.windowsupdate News Group today:
>
>
> "The head of technical support at the Microsoft Telephone Support Center
> in
> the Phillipines told me that the update KB942615 is Defective and
> Microsoft
> Advisies Removing the update with your ADD/REMOVE PROGRAMS (don't forget
> to
> click on show updates) and Disabling Automatic Updating on your computer
> so
> that it does not try to reinstall this update automatically.
>
> He does not know when the problem will be fixed. I hope that Microsoft
> issues new updates and an apology letter very soon.
>
> I hope that Microsoft fires their Quality Assurance Manager (if they even
> have one.)"
>
>
> Rich
>
>


Not surprising that it's broken.

It is surprising that they'd admit it and then also admit to not having a
fix/patch immediately ready after said admission.

Swell.

"Rich" <Rich_NoSpam@ptd_nospam.net> wrote in message
news:...
> I found this on the microsoft.public.windowsupdate News Group today:
>
>
> "The head of technical support at the Microsoft Telephone Support Center
> in
> the Phillipines told me that the update KB942615 is Defective and
> Microsoft

Your Subject line says KB942367 but the body of your message says KB942615.

Which is it?

Tom Lake

Sorry!

KB942367 is Microsoft's fix for the problems that KB942615 created.

If you read some of the posts in microsoft.public.windowsupdate KB942367
fixes the problem for a while and then some users report that the problem
re-occurs.

Others in have stated that you don't need the KB942367 Hotfix, all you need
is the registry patch in KB942367.

The post I quoted says to not do the KB942615 until they get it figured out.
I read one post where someone said that a real fix for KB942615 might not be
implemented until XP SP3.

Rich



"Tom Lake" <> wrote in message
news:476745b4$0$4976$...
>
>
> "Rich" <Rich_NoSpam@ptd_nospam.net> wrote in message
> news:...
>> I found this on the microsoft.public.windowsupdate News Group today:
>>
>>
>> "The head of technical support at the Microsoft Telephone Support Center
>> in
>> the Phillipines told me that the update KB942615 is Defective and
>> Microsoft
>
> Your Subject line says KB942367 but the body of your message says
> KB942615.
>
> Which is it?
>
> Tom Lake

Not sure exactly how serious the problems are, because I use IE only to update
Windows and Firefox for all else. But if this is serious enough, pressure from
various corporate and enterprise users will push Microsoft to fix this one up
prior it XP SP3, whenever that is. If all the Microsoft worker bees are
successful, there will be a fix available on the next patch Tuesday... Ben Myers

On Tue, 18 Dec 2007 10:19:22 -0500, "Rich" <Rich_NoSpam@ptd_nospam.net> wrote:

>Sorry!
>
>KB942367 is Microsoft's fix for the problems that KB942615 created.
>
>If you read some of the posts in microsoft.public.windowsupdate KB942367
>fixes the problem for a while and then some users report that the problem
>re-occurs.
>
>Others in have stated that you don't need the KB942367 Hotfix, all you need
>is the registry patch in KB942367.
>
>The post I quoted says to not do the KB942615 until they get it figured out.
>I read one post where someone said that a real fix for KB942615 might not be
>implemented until XP SP3.
>
>Rich
>
>
>
>"Tom Lake" <> wrote in message
>news:476745b4$0$4976$...
>>
>>
>> "Rich" <Rich_NoSpam@ptd_nospam.net> wrote in message
>> news:...
>>> I found this on the microsoft.public.windowsupdate News Group today:
>>>
>>>
>>> "The head of technical support at the Microsoft Telephone Support Center
>>> in
>>> the Phillipines told me that the update KB942615 is Defective and
>>> Microsoft
>>
>> Your Subject line says KB942367 but the body of your message says
>> KB942615.
>>
>> Which is it?
>>
>> Tom Lake
>

I don't know if they can do it that quick. KB942615 fixes all the things
mentioned in Microsoft Securuty Bulletin MS07-069.

Rich




"Ben Myers" <> wrote in message
news:...
> Not sure exactly how serious the problems are, because I use IE only to
> update
> Windows and Firefox for all else. But if this is serious enough,
> pressure from
> various corporate and enterprise users will push Microsoft to fix this one
> up
> prior it XP SP3, whenever that is. If all the Microsoft worker bees are
> successful, there will be a fix available on the next patch Tuesday... Ben
> Myers
>
> On Tue, 18 Dec 2007 10:19:22 -0500, "Rich" <Rich_NoSpam@ptd_nospam.net>
> wrote:
>
>>Sorry!
>>
>>KB942367 is Microsoft's fix for the problems that KB942615 created.
>>
>>If you read some of the posts in microsoft.public.windowsupdate KB942367
>>fixes the problem for a while and then some users report that the problem
>>re-occurs.
>>
>>Others in have stated that you don't need the KB942367 Hotfix, all you
>>need
>>is the registry patch in KB942367.
>>
>>The post I quoted says to not do the KB942615 until they get it figured
>>out.
>>I read one post where someone said that a real fix for KB942615 might not
>>be
>>implemented until XP SP3.
>>
>>Rich
>>
>>
>>
>>"Tom Lake" <> wrote in message
>>news:476745b4$0$4976$.. .
>>>
>>>
>>> "Rich" <Rich_NoSpam@ptd_nospam.net> wrote in message
>>> news:...
>>>> I found this on the microsoft.public.windowsupdate News Group
>>>> today:
>>>>
>>>>
>>>> "The head of technical support at the Microsoft Telephone Support
>>>> Center
>>>> in
>>>> the Phillipines told me that the update KB942615 is Defective and
>>>> Microsoft
>>>
>>> Your Subject line says KB942367 but the body of your message says
>>> KB942615.
>>>
>>> Which is it?
>>>
>>> Tom Lake
>>

"Rich" <Rich_NoSpam@ptd_nospam.net> wrote in message
news:...
> Sorry!
>
> KB942367 is Microsoft's fix for the problems that KB942615 created.
>
> If you read some of the posts in microsoft.public.windowsupdate KB942367
> fixes the problem for a while and then some users report that the problem
> re-occurs.
>
> Others in have stated that you don't need the KB942367 Hotfix, all you
> need is the registry patch in KB942367.
>
> The post I quoted says to not do the KB942615 until they get it figured
> out.
> I read one post where someone said that a real fix for KB942615 might not
> be implemented until XP SP3.
>
> Rich
>


Rich -

(Not a flame, btw......)

What the hell is the symptom of breakage from KB942615?

I see that I have it installed, but so far as I can tell I have no issues to
report.

Wait, ah. urlmon.dll errors in IE.......nope:

http://www.eggheadcafe.com/software/...d-ie6-sp1.aspx


Thanks,

Stew

"S.Lewis" wrote:
>
> What the hell is the symptom of breakage from KB942615?
>
> I see that I have it installed, but so far as I can tell I have no issues to
> report.


For me, it was IE v. 6 crashing everytime I went to
www.mail.yahoo.com . It also crashed on random other
websites, but I saw no pattern since I usually use Opera.
Simply uninstalling KB942615 corrected the problem.

*TimDaniels*

I can attest that there are problems.

Since my last update, IE crashes at times. There are 2-3 sites where it
does this consistently (it says it has to close--I let it close and then
reclick to that site and it works).

I tried the regedit part and it did fix it for about 12 hours and then
problem re-occurs. So, I undid the regedit. They do recommend you do the
hotfix followed by the regedit. I've decided to wait until they fix it. I
suspect it will be resolved before SP3. (Does anyone know when SP3 is coming
out? I thought they were done with these service packs)


Mel


"Ben Myers" <> wrote in message
news:...
> Not sure exactly how serious the problems are, because I use IE only to
> update
> Windows and Firefox for all else. But if this is serious enough,
> pressure from
> various corporate and enterprise users will push Microsoft to fix this one
> up
> prior it XP SP3, whenever that is. If all the Microsoft worker bees are
> successful, there will be a fix available on the next patch Tuesday... Ben
> Myers
>
> On Tue, 18 Dec 2007 10:19:22 -0500, "Rich" <Rich_NoSpam@ptd_nospam.net>
> wrote:
>
>>Sorry!
>>
>>KB942367 is Microsoft's fix for the problems that KB942615 created.
>>
>>If you read some of the posts in microsoft.public.windowsupdate KB942367
>>fixes the problem for a while and then some users report that the problem
>>re-occurs.
>>
>>Others in have stated that you don't need the KB942367 Hotfix, all you
>>need
>>is the registry patch in KB942367.
>>
>>The post I quoted says to not do the KB942615 until they get it figured
>>out.
>>I read one post where someone said that a real fix for KB942615 might not
>>be
>>implemented until XP SP3.
>>
>>Rich
>>
>>
>>
>>"Tom Lake" <> wrote in message
>>news:476745b4$0$4976$.. .
>>>
>>>
>>> "Rich" <Rich_NoSpam@ptd_nospam.net> wrote in message
>>> news:...
>>>> I found this on the microsoft.public.windowsupdate News Group
>>>> today:
>>>>
>>>>
>>>> "The head of technical support at the Microsoft Telephone Support
>>>> Center
>>>> in
>>>> the Phillipines told me that the update KB942615 is Defective and
>>>> Microsoft
>>>
>>> Your Subject line says KB942367 but the body of your message says
>>> KB942615.
>>>
>>> Which is it?
>>>
>>> Tom Lake
>>

"Timothy Daniels" <> wrote in message
news:47681e82$0$9615$...
> "S.Lewis" wrote:
>>
>> What the hell is the symptom of breakage from KB942615?
>>
>> I see that I have it installed, but so far as I can tell I have no issues
>> to report.
>
>
> For me, it was IE v. 6 crashing everytime I went to
> www.mail.yahoo.com . It also crashed on random other
> websites, but I saw no pattern since I usually use Opera.
> Simply uninstalling KB942615 corrected the problem.
>
> *TimDaniels*
>


Thanks. Somehow my configuration has dodged the bullet - at least for the
moment.