Re: KB942615 December IE Cumulative Update - Crashing IE

"Bob Held" <> schrieb:

> IE was crashing, Application Event log showed Event ID: 1000 involving
> URLMON.DLL
>
> This behavior started immediately after installing the December security
> updates.

That's a known issue, see
http://groups.google.com/groups?thre...individual.net
for a workaround.

> I un-installed KB942615 IE Cumulative Update, restarted and everything is
> back working fine.

Please let the critical update install again and apply the workaround.

> Windows XP SP2
> IE 6

Bye,
Freudi

Chillax, d00d.

gayboylaca wrote:
> That might be fine for sophisticated computer people like you Freudi, but
> for the vast majority, Microsoft has to issue an apology and easy to fix
> update for the masses.
>
>
> "Ottmar Freudenberger" wrote:
>
>> "Bob Held" <> schrieb:
>>
>>> IE was crashing, Application Event log showed Event ID: 1000 involving
>>> URLMON.DLL
>>>
>>> This behavior started immediately after installing the December security
>>> updates.
>>
>> That's a known issue, see
>> http://groups.google.com/groups?thre...individual.net
>> for a workaround.
>>
>>> I un-installed KB942615 IE Cumulative Update, restarted and everything
>>> is
>>> back working fine.
>>
>> Please let the critical update install again and apply the workaround.
>>
>>> Windows XP SP2
>>> IE 6
>>
>> Bye,
>> Freudi

"gayboylaca" <> schrieb:
> "Ottmar Freudenberger" wrote:
>
>> "Bob Held" <> schrieb:
>>
>> > IE was crashing, Application Event log showed Event ID: 1000 involving
>> > URLMON.DLL
>> >
>> > This behavior started immediately after installing the December security
>> > updates.
>>
>> That's a known issue, see
>> http://groups.google.com/groups?thre...individual.net
>> for a workaround.
>>
>> > I un-installed KB942615 IE Cumulative Update, restarted and everything is
>> > back working fine.
>>
>> Please let the critical update install again and apply the workaround.
>>
>> > Windows XP SP2
>> > IE 6

> That might be fine for sophisticated computer people like you Freudi, but for
> the vast majority, Microsoft has to issue an apology and easy to fix update
> for the masses.

Now, please re-read my posting linked to above. Read what I've written
in MS's direction. Read what I've written to workaround the issue. And
afterwards read the Security Bulletin MS07-069 mentioning the security
holes which are trageted to be fixed with KB942615.

After having done all this, you may want to call your "MS Philippines
Tech Supporter" rubbish and re-think what you've written in my direction.

No, I'm not related to MS anyhow else but as a user of some of their
products.

Bye,
Freudi

"gayboylaca" <> schrieb:

> Microsoft said they are working on a fix for the problem with URLMON.DLL
> which is causing errors on some computers.

True.

> The technical support
> representative said I should wait until the fix is available from the
> Microsoft Update website, and keep KB942615 removed and hidden until that
> time.

That's a *bad advise* in case it was given. See also
http://groups.google.com/groups?thre...TNGP04.phx.gbl
for your reference.

Bye,
Freudi

"gayboylaca" <> schrieb:

> What do you advise exactly that I should do since I have Windows XP SP2
> using Internet Expolorer 6 and I am experiencing crashes after installing
> security update 942615 on my computer?
>
> Please consider these 3 options:
>
> 1. should I install KB942615 and then go through steps 1 - 9 for the
> WORKAROUND
> mentiioned at http://support.microsoft.com/kb/946627
>
> 2. or should I do the WORKAROUND steps mentioned at
> http://support.microsoft.com/kb/946627 first and then install KB942615

It doesn't/shouldn't matter when the registry key is beeing set (before or
after installing KB942615). But they need to be set in case you're running
Windows XP SP2 with IE6 and are seeing IE crashing in urlmon.dll after
having KB942615 applied.

Instead of manually munging in the registry, you may want to download
http://patch-info.de/IE/Downloads/IE..._dll-Crash.zip and open
it.
By double clicking on the contained IE6SP2_Hotfix_KB942367_aktivieren.reg
the registry entries mentioned in KB946627 (and KB942367) and letting it
merge into the registry, you're done.

> 3. or should I leave KB942615 hidden and wait for new updates from Microsoft
> to be released

Nope, since KB942615 is closing some security holes in IE, which are
actively beeing exploited already "in the wild".

Bye,
Freudi

"gayboylaca" <> schrieb:

> 5. Do you think it will be necessary to remove this key when the next
> cumulative update comes out from Microsoft or at some time in the future?

While I doubt it will, I don't *know* as of now.
In case you'll need to delete the registry key, you'll find an announcement
in this very newsgroup. If you want/need to delete the registry key for what-
ever reason, you can find and run the "IE6SP2_Hotfix_KB942367_deaktivieren.reg"
contained in the IE6SP2_urlmon_dll-Crash.zip already.

> 6. If Microsoft fixes the issue by releasing a "repairing" update would I
> need to run that update, or would I skip it?

Since there are no announcements nor other informations from MS, this
question can't be answered yet.

> 7. If i ran the Microsoft update, would I need to remove the registry key
> before running the Microsoft update?

See above, most likely not, but noone *knows* as of now.

> 8. How can I be personally notified what I should do if Microsoft releases
> their own fix?

Subscribe the Security Bulletin Newsletter for instance:
http://www.microsoft.com/technet/sec...in/notify.mspx

> 9. How can I find out if Microsoft will provide a repair officially as a new
> update and when?

See above.

> 10. How can I avoid having my computer exploited by security holes in
> Internet Explorer 6 which are corrected by KB942615 if I keep the update
> hidden and wait until Microsoft provides the fix if they even do so?

There are no real practicable workarounds. See the Security Bulletin for
details: http://www.microsoft.com/technet/sec.../MS07-069.mspx
(section "Vulnerability Information").

Bye,
Freu"Do you need to know my banking account?"di

This order intead, please: #4, #1 thru #3.
--
~PA Bear

gayboylaca wrote:
> Dear Freudi:
>
> Before I do these 4 steps:
>
> 1. download http://patch-info.de/IE/Downloads/IE..._dll-Crash.zip
>
> 2. open it by double clicking on the contained
> IE6SP2_Hotfix_KB942367_aktivieren.reg
>
> (which are the registry entries mentioned in KB946627 and KB942367)
>
> 3. let it merge into the registry
>
> 4. install update KB942615
>
> __________________________________________________ _________________
>
> I would like to know the answer to these questions:
>
> 5. Do you think it will be necessary to remove this key when the next
> cumulative update comes out from Microsoft or at some time in the future?
>
> 6. If Microsoft fixes the issue by releasing a "repairing" update would I
> need to run that update, or would I skip it?
>
> 7. If i ran the Microsoft update, would I need to remove the registry key
> before running the Microsoft update?
>
> 8. How can I be personally notified what I should do if Microsoft releases
> their own fix?
>
> 9. How can I find out if Microsoft will provide a repair officially as a
> new
> update and when?
>
> __________________________________________________ __________________
>
> Regarding the protection provided by KB942615:
>
> 10. How can I avoid having my computer exploited by security holes in
> Internet Explorer 6 which are corrected by KB942615 if I keep the update
> hidden and wait until Microsoft provides the fix if they even do so?
>
> Please reply to each of these questions in easy to understand English
> because I do not understand tech talk and abbreviations.
>
> I believe this is an elaboration of questions asked by Vince in posting
> number 39 at Google Group microsoft.public.windowsupdate at
>
> http://groups.google.com/group/micro...171f826a1bb17a
>
> Thank you again for your time in this matter. I am very concerned about
> finding out if Microsoft will provide a fix for everyone in an upcoming
> update and when that will be.
>
> Sincerely,
>
> gayboylaca
>
>
>
>
>
>
> "Ottmar Freudenberger" wrote:
>
>> "gayboylaca" <> schrieb:
>>
>>> What do you advise exactly that I should do since I have Windows XP SP2
>>> using Internet Expolorer 6 and I am experiencing crashes after
>>> installing
>>> security update 942615 on my computer?
>>>
>>> Please consider these 3 options:
>>>
>>> 1. should I install KB942615 and then go through steps 1 - 9 for the
>>> WORKAROUND
>>> mentiioned at http://support.microsoft.com/kb/946627
>>>
>>> 2. or should I do the WORKAROUND steps mentioned at
>>> http://support.microsoft.com/kb/946627 first and then install KB942615
>>
>> It doesn't/shouldn't matter when the registry key is beeing set (before
>> or
>> after installing KB942615). But they need to be set in case you're
>> running
>> Windows XP SP2 with IE6 and are seeing IE crashing in urlmon.dll after
>> having KB942615 applied.
>>
>> Instead of manually munging in the registry, you may want to download
>> http://patch-info.de/IE/Downloads/IE..._dll-Crash.zip and open
>> it.
>> By double clicking on the contained IE6SP2_Hotfix_KB942367_aktivieren.reg
>> the registry entries mentioned in KB946627 (and KB942367) and letting it
>> merge into the registry, you're done.
>>
>>> 3. or should I leave KB942615 hidden and wait for new updates from
>>> Microsoft to be released
>>
>> Nope, since KB942615 is closing some security holes in IE, which are
>> actively beeing exploited already "in the wild".
>>
>> Bye,
>> Freudi

"PA Bear" <> schrieb:
> gayboylaca wrote:
>> Dear Freudi:
>>
>> Before I do these 4 steps:
>>
>> 1. download http://patch-info.de/IE/Downloads/IE..._dll-Crash.zip
>>
>> 2. open it by double clicking on the contained
>> IE6SP2_Hotfix_KB942367_aktivieren.reg
>>
>> (which are the registry entries mentioned in KB946627 and KB942367)
>>
>> 3. let it merge into the registry
>>
>> 4. install update KB942615

> This order intead, please: #4, #1 thru #3.

It doesn't matter if the registry entry is beeing set before or after
the installation of KB942615 in case it (the registry key) is need to
be set.

FWIW,
Freu"Yup, I've tested that"di