RE: KB942615 is Defective and Microsoft Advisies Removing and Disa

I have reviewed the many postings regarding this issue as I experienced the
same on 1 out of 3 computers at home. It took me a a few hours to realize
that the solution was as you described. That is, uninstall the update.
While I appreciate the advise from many of the volunteers, I am choosing not
to perform any workarounds and will wait for a formal update from MS.

I would be interested to hear from the technical volunteers out there why
some computers are affected and others are not. My two computers that
experienced no issue are desktops with Windows XP Home, SP2, and IE 6.0 SP2.
The MFG and hardware content is completely different. While some software is
the same, there are differences. My laptop, which experienced the issue,
runs Windows XP Professional, SP2, and IE 6.0, SP2. So why does the update
affect some and not all? Differences in the version of URLMON.DLL,
hardware/software configurations, other? Thanks in advance.

While I realize this has turned into a very heated discussion and has opened
up the opportunities to bash MS, I do appreciate the efforts of the
volunteers. However, I do have to agree with those that have voiced their
concerns about the lack of quality control and thoroughness of the testing
exhibited.

"gayboylaca" wrote:

> Sorry for the spelling and grammatical errors in my posting.
>
> "Philippines" not Phillipines and "advises" not advisies are the correct
> spelling for those words.
>
> "gayboylaca" wrote:
>
> > 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.)
> >
> > Best wishes and Happy Holidays everyone!
> >
> >

Thanks for your reply. I submitted a case number with MS simply to record
the issue (URLMON.DLL runtime errors after installation of KB). While I do
not doubt what the MS support center told you, I am confused why he would say
this update is only for non-XP opetating systems such as Windows ME as
KB942615 is still posted on the MS website and states no mention of Windows
Me as follows:

APPLIES TO
• Microsoft Internet Explorer 6.0 Service Pack 1, when used with:
Microsoft Windows NT 4.0 Service Pack 6a
Microsoft Windows XP Professional
Microsoft Windows XP Tablet PC Edition

• Microsoft Internet Explorer 6.0, when used with:
Microsoft Windows Server 2003, Web Edition
Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Microsoft Windows Server 2003, Enterprise Edition
Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based
Systems
Microsoft Windows Server 2003, Enterprise Edition for Itanium-based
Systems
Microsoft Windows Small Business Server 2003 Standard Edition

• Windows Internet Explorer 7 for Windows Server 2003 IA64
• Windows Internet Explorer 7 for Windows XP
• Windows Internet Explorer 7 for Windows Server 2003
• Windows Internet Explorer 7 in Windows Vista


I chose not to upgrade to IE7 since colleages exprienced browser issues and
slower response when it was first released. Since I am happy with IE 6.0 and
not used to the multiple tab environment, I have chosen not to upgrade at
this time.

"gayboylaca" wrote:

> Hi Kaz,
>
> I am not a technical volunteer, just a personal computer user, but I can
> share with you what the technical support at the Microsoft Telephone Support
> Center in the Philippines told me.
>
> He said that the update KB942615 was intended for personal computers running
> a different Windows operating system such as Windows ME and not the Windows
> XP operating system. The problem is that the update KB942615 incorrectly
> tries to install on computers running the Windows XP operating system. Since
> it was not intended for Windows XP users, it causes the errors.
>
> Maybe that is why you may be experiencing different problems with different
> personal computers.
>
> ASIDE FROM THAT:
>
> By the way, can you tell me why you are using Internet Explorer 6 instead of
> Internet Explorer 7?
>
> I am using Windows XP Home Edition with Internet Explorer 6 because I was
> having difficulties with Internet Explorer 7 on my personal computer.
>
> Please reply.
>
> Thanks,
>
> gayboylaca
>
>
>
> __________________________________________________ _________________
>
> "Kaz" wrote:
>
> > I have reviewed the many postings regarding this issue as I experienced the
> > same on 1 out of 3 computers at home. It took me a a few hours to realize
> > that the solution was as you described. That is, uninstall the update.
> > While I appreciate the advise from many of the volunteers, I am choosing not
> > to perform any workarounds and will wait for a formal update from MS.
> >
> > I would be interested to hear from the technical volunteers out there why
> > some computers are affected and others are not. My two computers that
> > experienced no issue are desktops with Windows XP Home, SP2, and IE 6.0 SP2.
> > The MFG and hardware content is completely different. While some software is
> > the same, there are differences. My laptop, which experienced the issue,
> > runs Windows XP Professional, SP2, and IE 6.0, SP2. So why does the update
> > affect some and not all? Differences in the version of URLMON.DLL,
> > hardware/software configurations, other? Thanks in advance.
> >
> > While I realize this has turned into a very heated discussion and has opened
> > up the opportunities to bash MS, I do appreciate the efforts of the
> > volunteers. However, I do have to agree with those that have voiced their
> > concerns about the lack of quality control and thoroughness of the testing
> > exhibited.
> >
> > "gayboylaca" wrote:
> >
> > > Sorry for the spelling and grammatical errors in my posting.
> > >
> > > "Philippines" not Phillipines and "advises" not advisies are the correct
> > > spelling for those words.
> > >
> > > "gayboylaca" wrote:
> > >
> > > > 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.)
> > > >
> > > > Best wishes and Happy Holidays everyone!
> > > >
> > > >

"gayboylaca" <> schrieb:

> I am not a technical volunteer, just a personal computer user, but I can
> share with you what the technical support at the Microsoft Telephone Support
> Center in the Philippines told me.
>
> He said that the update KB942615 was intended for personal computers running
> a different Windows operating system such as Windows ME and not the Windows
> XP operating system. The problem is that the update KB942615 incorrectly
> tries to install on computers running the Windows XP operating system. Since
> it was not intended for Windows XP users, it causes the errors.

Sorry, I don't want to be rude nor offend *you*, but that's plain nonsense.
There's no support for Windows 98/Me since July 2006 by MS anyway and yes,
KB942615 for IE6 running on Windows XP SP2 *is* an update that fixes several
more or less serious security holes - but has a bug in it's "compilation".
To workaround the issue, you may want to followup the following thread:
http://groups.google.com/groups?thre...TNGP02.phx.gbl

Once again: Please note, that the issue dealed with in the thread linked to
above deals with IE6 running on Windows XP SP2 and having KB942615 for that
very configuaration applied! It does *NOT* deal with IE6 running on Windows
2000 nor IE7 running on any other Windows platform.

Bye,
Freudi

Freudi,

Thanks for the clarification. I have read your informative feedback to the
many questions being posted on this subject since the KB was released. Many
volunteers have been working overtime to support those in need. Have you
received any private feedback or can you comment on the following:

1. With the same operating system (XP, SP2) and the same IE version (6.0,
SP2), why are some computers affected and others not? I checked my three
computers and all have the same version of URLMON.DLL (6.0.2900.3199). Only
one computer was negatively impacted by the upgrade (URLMON.DLL runtime
error).

2. For those of us not wishing to perform the workaround, have you received
any feedback from MS as to the release of a revised upgrade?

3. Did you receive any feedback on your suggestions so elloquently stated
below?

Newsgroups: microsoft.public.windowsupdate,
microsoft.public.windowsxp.general
From: "Ottmar Freudenberger" <fre...@gmx.net>
Date: Sat, 15 Dec 2007 08:59:52 +0100
Local: Sat, Dec 15 2007 1:59 am
Subject: Re: WARNING: KB942615 may require an extra reboot to apply correctly

Now, since the "registry hack" seems to solve the problems with urlmon.dll
running IE6 under Windows XP SP2, wouldn't it be a good idea to revise the
Security Bulletin MS07-069 and the "Known Issues" section there which still
states, that there are no known problems?

Further more, what will the next steps be from MS to really fix the issue
for the average user? The release of a KB942615v2 for IE6 on Windows XP SP2
*inculding* the registry fix or even better, releasing the update package
with a fixed urlmon.dll? Me thinks it's somewhat unacceptable to force
users hacking in the heart and brain of Windows aka the registry themself
and leaving those users in the dark, which will most likely never find the
way into the newsgroups to get aware of the -well- "fix".



"Ottmar Freudenberger" wrote:

> "gayboylaca" <> schrieb:
>
> > I am not a technical volunteer, just a personal computer user, but I can
> > share with you what the technical support at the Microsoft Telephone Support
> > Center in the Philippines told me.
> >
> > He said that the update KB942615 was intended for personal computers running
> > a different Windows operating system such as Windows ME and not the Windows
> > XP operating system. The problem is that the update KB942615 incorrectly
> > tries to install on computers running the Windows XP operating system. Since
> > it was not intended for Windows XP users, it causes the errors.
>
> Sorry, I don't want to be rude nor offend *you*, but that's plain nonsense.
> There's no support for Windows 98/Me since July 2006 by MS anyway and yes,
> KB942615 for IE6 running on Windows XP SP2 *is* an update that fixes several
> more or less serious security holes - but has a bug in it's "compilation".
> To workaround the issue, you may want to followup the following thread:
> http://groups.google.com/groups?thre...TNGP02.phx.gbl
>
> Once again: Please note, that the issue dealed with in the thread linked to
> above deals with IE6 running on Windows XP SP2 and having KB942615 for that
> very configuaration applied! It does *NOT* deal with IE6 running on Windows
> 2000 nor IE7 running on any other Windows platform.
>
> Bye,
> Freudi
>

"Kaz" <> schrieb:

> Have you
> received any private feedback or can you comment on the following:
>
> 1. With the same operating system (XP, SP2) and the same IE version (6.0,
> SP2), why are some computers affected and others not?

All machines running IE6 on Windows XP SP2 are indeed affected, but the
crashes in urlmon.dll are occuring more or less randomly. There seems to
be a relation on the cache (Temporary Internet Files) and its content and
some site specfics. I've had the crash on a test machine even on the
Windows Update site...

> 2. For those of us not wishing to perform the workaround, have you received
> any feedback from MS as to the release of a revised upgrade?

Nope.

> 3. Did you receive any feedback on your suggestions so elloquently stated
> below?

Nope.

MS seems to playing "dead man" on the issue and on publishing even the issue.
I really "love" when "they" behave that way NOT :-/

Bye,
Freudi

Ottmar Freudenberger wrote:
<snipped>
> MS seems to playing "dead man" on the issue and on publishing even
> the issue. I really "love" when "they" behave that way NOT :-/

Agreed... In all its sarcastic glory. ;-)

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

"Shenan Stanley" <> schrieb:
> Ottmar Freudenberger wrote:
> <snipped>
>> MS seems to playing "dead man" on the issue and on publishing even
>> the issue. I really "love" when "they" behave that way NOT :-/
>
> Agreed... In all its sarcastic glory. ;-)

Hm, thanks. Have you pinged someone in the campus already?
Seems to me I'll have to contact MSRC by mail tomorrow...

Bye,
Freudi

Thanks for the prompt reply. Based on your feedback, I will take it as a
blessing that my two desktops running XP Home SP2, with IE 6.0, SP2, have had
zero issues since the KB upgrade. My laptop, XP Pro, SP2, with IE 6.0, SP2,
was the only victim exhibiting the urlmon.dll crashes. All computers reside
under the same household, workgroup, router, etc. I routinely empty the
'temp internet file' cache on all machines and purposely did so on my laptop
as one of the diagnostics before uninstalling the KB.

"Ottmar Freudenberger" wrote:

> "Kaz" <> schrieb:
>
> > Have you
> > received any private feedback or can you comment on the following:
> >
> > 1. With the same operating system (XP, SP2) and the same IE version (6.0,
> > SP2), why are some computers affected and others not?
>
> All machines running IE6 on Windows XP SP2 are indeed affected, but the
> crashes in urlmon.dll are occuring more or less randomly. There seems to
> be a relation on the cache (Temporary Internet Files) and its content and
> some site specfics. I've had the crash on a test machine even on the
> Windows Update site...
>
> > 2. For those of us not wishing to perform the workaround, have you received
> > any feedback from MS as to the release of a revised upgrade?
>
> Nope.
>
> > 3. Did you receive any feedback on your suggestions so elloquently stated
> > below?
>
> Nope.
>
> MS seems to playing "dead man" on the issue and on publishing even the issue.
> I really "love" when "they" behave that way NOT :-/
>
> Bye,
> Freudi
>

Shenan Stanley wrote:
> Ottmar Freudenberger wrote:
> <snipped>
>> MS seems to playing "dead man" on the issue and on publishing even
>> the issue. I really "love" when "they" behave that way NOT :-/
>
> Agreed... In all its sarcastic glory. ;-)

This issue /is/ being discussed in certain MS circles, believe me.

Shenan Stanley wrote:
> Agreed... In all its sarcastic glory. ;-)

Ottmar Freudenberger wrote:
> Hm, thanks. Have you pinged someone in the campus already?
> Seems to me I'll have to contact MSRC by mail tomorrow...

I have not - but I can say with some certainty that the issue is known and
being discussed by some in MS.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html