KB942615 is Defective and Microsoft Advisies Removing and Disablin
gayboylaca
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
"Philippines" not Phillipines and "advises" not advisies are the correct
spelling for those words.
Tresa
checker. Happy Holidays to you.
Shenan Stanley
> I will. Thanks for the info. I know what you mean, this site needs
> spell checker. Happy Holidays to you.
Tresa,
Although there is a web interface for this newsgroup - it is recommended
that you not use the web interface to post/reply/keep track of your
messages. This is a newsgroup - not a web forum and the web interface
written to interface with it is - well - horrible. It has not changed that
i know of in a LONG time, it has issues that have repeated themselves many
times over in the years I have been here and just about everyone here will
tell you to find a different way to access the newsgroups.
Microsoft Newsgroups: Frequently Asked Questions
http://www.microsoft.com/communities/guide/newsgroupfaq.mspx
How to Configure Outlook Express for Internet News
http://support.microsoft.com/kb/171164
How to Subscribe to Newsgroups in Outlook Express
http://support.microsoft.com/kb/171190
A little more detail...
http://www.michaelstevenstech.com/outlookexpressnewreader.htm
If you want to search for older posts than you may choose to keep on your
computer...
http://groups.google.com/
If you have Windows Vista - which I believe you might going by past
postings:
Accessing Newsgroups With Windows Mail
http://vistasupport.mvps.org/accessing_newsgrousp_with-windows_mail.htm
That should make things a little easier.
Enjoy!
--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html
Kaz
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
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
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
I asked the technical support representative in the Philippines the same
question:
"Why is KB942615 posted for used by Windows XP users on the Microsoft
website?"
His answer was that Microsoft made a mistake.
I don't remember which operating system exactly that he said the update was
supposed to be for, but he specifically stated it was not supposed to be for
Windows XP as stated on the Microsoft website.
_____________________
Regarding Internet Explorer 7 I agree with you 100%. For me part of the
problems were that Internet Explorer 7 was much slower and gave a slower
response, and I did not like the multiple tab environment either. Among
other problems I was experiencing, you said it in a nutshell. That's why I
switched back to Internet Explorer 6.
Have a happy holiday season Kaz, and thanks for writing back.
Sincerely,
gayboylaca
Ottmar Freudenberger
> 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?threadm=uMMymIgPIHA.292%40TK2MSFTNGP02.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
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
> 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
<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. ;-)
Ottmar Freudenberger
> 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
Kaz
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.
PA Bear
> 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
> 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
<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 :-/
Shenan 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...
PA Bear wrote:
> This issue /is/ being discussed in certain MS circles, believe me.
Of this I have no doubt - but it does not preclude me from agreeing. *grin*
Ottmar Freudenberger
> 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.
Sure, but there *needs* to be a revised Security Bulletin *at least*
stating that there *are* known issues (and maybe how to workaround
these by applying the registry changes mentioned in MSKB article
KB942367). Right now it looks for customers as if MS resonsibles are
holding their hands before their eyes and are stating that they aren't
seeing any issue so far. *That's* the most furstrating aspect of the
glitch - not only for me, but for the average user anyway.
Why is it that MS seems to be a champ when it comes to marketing bla
but seems to lack to communicate issues of all kind to their *users*/
customers?
Something is Rotten in (the state of) Denmark,
Freu"and it's 'beginning' to stink against heaven"di
Kipp
"gayboylaca" <gaybo...@discussions.microsoft.com> wrote in message
news:F5272F45-53FE-4F91...@microsoft.com...
Shenan Stanley
> 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 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.
Kipp wrote:
> Is this an english grammar and spelling newsgroup?
No...
Does it bother you when someone corrects their own posts the way
"gayboylaca" has above?
Perhaps they just wished not to offend anyone - or perhaps they are just a
stickler for details. ;-)
Kipp
"Shenan Stanley" <newsh...@gmail.com> wrote in message
news:%23ru$dWUQIH...@TK2MSFTNGP06.phx.gbl...
> Kipp wrote:
>> Is this an english grammar and spelling newsgroup?
>
> No...
>
> Does it bother you when someone corrects their own posts the way
> "gayboylaca" has above?
>
No but I could care less how someone spells a word in this discussion as
long as it's not that far off and I can understand it. Missing an "l", got
an extra "i"... what's the big deal? We're discussing computer problem
(windows update, specifically) here, not english.
> Perhaps they just wished not to offend anyone - or perhaps they are just a
> stickler for details. ;-)
A perfectionist.
Tom [Pepper] Willett
"Kipp" <ki...@kipp.com> wrote in message
news:Oh6v4nU...@TK2MSFTNGP06.phx.gbl...
:
::
: No but I could care less how someone spells a word in this discussion as
:
![Kurt Falde [MSFT]'s profile photo](http://lh3.googleusercontent.com/a-/ALV-UjWbVI8x-pGGGsTXCKML0DcR5VnKLQFHFStb8B7nG9_xrSto6AjHdg=s40-c)
Kurt Falde [MSFT]
been tracking issues in CSS Security as well. The issue as far as I know is
a result of certain web sites as well as some type of timing issue that can
happen which is why it does not occur on all systems. The KB942367 is the
issue being seen and was what is termed a QFE fix and not a GDR fix which
means it has not been fully regression tested and was not included as
enabled in the current cumulative patch. I don't have any timeframes but I
believe that there will be something added to the current bulletin about
known issues regarding this. As far as what our person is the Phillipines
said I'm not sure where they got that... this current patch has nothing to
do with older OS's as several people have already pointed out we do not
realease updates for older out of support OS's. These patches definitely
apply to XP SP2 w/ IE6 along with all the other's pointed out in the KB.
--
Kurt Falde [MSFT]
"PA Bear" <PABe...@gmail.com> wrote in message
news:OUdlsvQQ...@TK2MSFTNGP02.phx.gbl...
antioch
"Kurt Falde [MSFT]" <n...@spam.com> wrote in message
news:OB5i3XaQ...@TK2MSFTNGP04.phx.gbl...
> Yep definitely being discussed :). MSRC knows/sees these posts and we have
> been tracking issues in CSS Security as well.
Clipped
> Kurt Falde [MSFT]
Hello Kurt Falde from MSFT.
Thank you for letting us know that MSRC knows and sees these posts and have
been tracking certain issues.
What a shame they did not see fit to let everybody know earlier - instead
time has been wasted by those trying to help, and posters are left running
around like 'farts in colanders not knowing which hole to get out'.
So in the meantime what are the computer ignorant, like myself, supposed to
do if they have the problem after install of KB942615.
I will not attempt to do anything with the Registry - though I have noticed
when it was first mentioned, that the below link to this registry fix does
not mention KB942615.
http://support.microsoft.com/kb/942367
Perhaps I have missed something along the way.
Anyhow, thanks for the info - I think I will wait for the next update to fix
the update that updated the fix - if you follow :-)
Rgds
Antioch
Ottmar Freudenberger
> Hello Kurt Falde from MSFT.
>
> Thank you for letting us know that MSRC knows and sees these posts and have
> been tracking certain issues.
http://support.microsoft.com/kb/946627/en-us will reflect the issue with
IE6 on Windows XP SP2 after having KB942615 installed - it's not live yet.
"The workaround is similar to KB942367" Kieron from MSRC stated by mail.
See also
http://blogs.technet.com/msrc/archive/2007/12/18/ms07-069-cumulative-security-update-for-internet-explorer-post-install-issue.aspx
whereas I'm not "lucky" with the formulation of "Because this occurs in
a customized installation, this isn't a widespread issue". I'm contact
with Kieron from MSRC not only to make clear that the issue is *not*
based on "a customized installation".
Bye,
Freudi
Ottmar Freudenberger
> See also
> http://blogs.technet.com/msrc/archive/2007/12/18/ms07-069-cumulative-security-update-for-internet-explorer-post-install-issue.aspx
> whereas I'm not "lucky" with the formulation of "Because this occurs in
> a customized installation, this isn't a widespread issue". I'm contact
> with Kieron from MSRC not only to make clear that the issue is *not*
> based on "a customized installation".
Well, we all have to be brave and wait for an explaination of the meaning
of the mysterious "customized installation" till Wednesday, when there
will/may be an posting on the IE blog according to Kieron:
http://blogs.msdn.com/ie/
<sarcasm>
Has anyone thought there's a lack of communication by MS which unsatisfies
MS's customers? No!!!1! I just have to be a brave guy and wait til MS is
willing to communicate, you naughty guy! MS knows what their customers
need, even better than their customers ever will. That reminds me on the
claim for Windows 98: "Where we want you to go tomorrow" (or similar <eg>).
</sarcasm>
Thanks MS for slapping right into my face once more,
Freudi
Ottmar Freudenberger
> http://support.microsoft.com/kb/946627/en-us will reflect the issue with
> IE6 on Windows XP SP2 after having KB942615 installed - it's not live yet.
It's live now.
> "The workaround is similar to KB942367" Kieron from MSRC stated by mail.
To be precise: It's the exact same workaround concerning the registry entry.
Surprise, surprise, it's Christmas time,
Freudi
Kaz
Update of KB942615 and all is well. As much as I was against editing the
registry, my requirement for a secure browser was a priority. I feel sorry
for those not savvy or comfortable enough with this editing process. I find
it unacceptable to push the solution off on the user for final repair even
though MS Tech Support may be willing to walk one through the process. It
certainly could have been rolled out as an automated process.
Had a good laugh at reading "Because this occurs in a customized
installation, this isn’t a widespread issue." as posted in
http://blogs.technet.com/msrc/archive/2007/12/18/ms07-069-cumulative-security-update-for-internet-explorer-post-install-issue.aspx.
I do not have a customized installation and experienced the urlmon.dll crash
issues. What a clever way to word it so as to minimize the issue. I suppose
we'll never know how many were really impacted.
Best of success to those still working on a repair. This issue provided me
the opportunity to install and run Mozilla for the first time. Love the
clean look and will now be using it as my main browser and switch to IE only
for MS and other sites requiring it. It's nice to have options.
Thanks to all the volunteers for your time and assistance.
Ottmar Freudenberger
> Completed registry patch via directions in KB946627 followed by Windows
> Update of KB942615 and all is well. As much as I was against editing the
> registry, my requirement for a secure browser was a priority. I feel sorry
> for those not savvy or comfortable enough with this editing process. I find
> it unacceptable to push the solution off on the user for final repair even
> though MS Tech Support may be willing to walk one through the process. It
> certainly could have been rolled out as an automated process.
Full ACK.
> Had a good laugh at reading "Because this occurs in a customized
> installation, this isn't a widespread issue." as posted in
>
http://blogs.technet.com/msrc/archive/2007/12/18/ms07-069-cumulative-security-update-for-internet-explorer-post-install-issue.aspx.
>
> I do not have a customized installation and experienced the urlmon.dll crash
> issues.
Well, they were simply unable to call "customized installation" an
"installation of QFE tree files contained in KB942615". See e.g.
http://groups.google.com/groups?selm=5ss0d2F...@mid.individual.net
and the additions I made to PABear's posting for some kind of a
(technical) explaination. Most are not aware that they/the system
installs the QFE tree files of an IE6 update. I wasn't either on a
system which has never seen any Hotfix installation for IE nor the
relevant registry key beeing set. I wounder why the QFE tree has
been used though (and it has been for *all* IE6 updates since last
year - when I've received the machine). It may be, that the vendor
of the machine has had a Hotfix for IE installed, that I'm not aware
of.
Anyway, it's a bug in the QFE tree set of files contained in KB942615
which still needs to be fixed by MS (and *NOT* their customers). And
no, there doesn't seem to be an easy way to revert back to GDR tree.
Bye,
Freudi
antioch
"Ottmar Freudenberger" <fre...@gmx.net> wrote in message
news:5st67oF...@mid.individual.net...
Clipped
> Anyway, it's a bug in the QFE tree set of files contained in KB942615
> which still needs to be fixed by MS (and *NOT* their customers). And
> no, there doesn't seem to be an easy way to revert back to GDR tree.
>
> Bye,
> Freudi
>
My heartfelt sympathy to you, Freudi, and the others working on our behalf
on this 'little inconvenience' - as it would appear as described by MS
articles.
I have a customized computer and at first thought that was what MS were
talking about - glad to see you were also a bit mystified by that phrase.
However I have bravely installed other updates for this month - so far all
seems OK.
I do not want Xmas spoilt by spending hours at my computer, troubleshooting.
Every night, before going to sleep, I say to myself, six time 'I am not
going to piss about in my Registry tomorrow'.
Season greetings to all you experts(no names - don't want to offend those
not mentioned)who have given me(and many others) great assistance over the
last 3 and a bit years, in this particular group.
Take care over the holiday, so you are ready for the first Black Tuesday of
2008.
Best wishes
Antioch
Susan Bradley
> 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!
>
>
of technical support in the Philippines would be answering phone calls.
While http://blogs.technet.com/msrc has the updated info on the IE6
patch issue, if you are going to be making claims like this, back it up
with a SRX or something more concrete than this claim.
I'm going to put this down as a communications problem. Mostly yours.
Don't mean to be brutal and mean here in a group who's folks that end up
here are here because something isn't working right on their computers,
but truly if you are going to be making statements like this, be
prepared to back it up with facts. SRX, names. Facts dude.
In the meantime check out http://blogs.technet.com/msrc for the REAL
facts in this issue.
For those impacted by this, they will get the needed automatic update
they need.
I consider this now closed.