Microsoft Windows Vista Community Forums - Vistaheads
Recommended Download



Welcome to the Microsoft Windows Vista Community Forums - Vistaheads, YOUR Largest Resource for Windows Vista related information.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so , join our community today!

If you have any problems with the registration process or your account login, please contact us.

Driver Scanner

BUGFIX: Crashes in Internet Explorer 6 under WXP-SP2 after December Patch Tuesday

microsoft.public.windowsupdate






Speedup My PC
Reply
  #1 (permalink)  
Old 12-15-2007
Bill Drake
 

Posts: n/a
BUGFIX: Crashes in Internet Explorer 6 under WXP-SP2 after December Patch Tuesday
Two days ago, I posted regarding the problem with Internet
Explorer 6 crashing when starting up if the default homepage
was set to "My MSN" and the page was heavily customized.

Other users chimed in to say they were experiencing similar
problems. All the problems resulted in a dialog box saying
that "Internet Explorer has encountered a serious error and
must close". If the user checked the technical info on the
error, the readout confirmed a problem with urlmon.dll.

With the help of several MVPs, other users with the problem,
and Kurt Falde from Microsoft - the problem has now been
localized and a fix has been tested and verified for the last
24 hours.

Those who are experiencing this problem need to make a
Registry Edit after the December Patch Tuesday update
installs the latest Internet Explorer Cumulative Update.
(The technical name for this update is KB942615.)

The problem occurs because the KB942615 update
installs an updated copy of urlmon.dll - but does NOT
install the required Registry Edit that applies the bugfix
so that urlmon.dll works properly in IE6.

The required Registry Entry is as follows:

---------------------begin KB942615FIX.reg--------------------

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Internet Explorer\Main\FeatureControl\
FEATURE_PROTECT_DECOMPRESSION_FILTER_FROM_ABORT_KB 942367]
"*"=dword:00000001

-----------------------end KB942615FIX.reg--------------------

Note: 1. The information within the two square brackets should
all be on ONE line. If your newsgroup reader has split
that information onto two or more lines - remove the
carriage returns so that all the info in between the
square brackets is on the third line in the
KB942615FIX.reg file, and the fourth line starts with "*".

2. There MUST be a blank line at the very bottom of the file.
Do NOT let the last character in the file end at the far
right of the last line. The registry edit will FAIL if there
is not a valid single carriage return as the last item in the
KB942615FIX.reg file.

To make the file and apply the patch:

1. Open Notepad and copy all the information between the
"Begin" and "End" lines above - from the beginning of the
word "Windows" to the beginning of the next line following
"00000001" - into Notepad. Save the notepad file as
KB942615FIX.reg, open Notepad and remove the extra
carriage returns as per Note 1 above. Also confirm the
presence of the final carriage return as per Note 2 above.
Save whatever changes to the KB94615FIX.reg file were
required to bring the file into a workable form.

2. Once you have the working file, close Notepad. Open
Windows Explorer and go to wherever you saved the file.
Double-click the file. Windows will ask you if you want
to merge the data in the Registry file into the Windows
Registry. Click Yes. Windows should respond that it
has successfully merged the KB942615FIX.reg file
info into the Registry.

3. Shut down and reboot your computer. Open Internet
Explorer and navigate to whatever web page was giving
you trouble before. You should now find that Internet
Explorer works properly again, just as it did before the
December version of the Internet Explorer Cumulative
Security Update was installed.


Comment to MVPs:

Kelly, could you please incorporate this info into one of your
Regfix files so the rest of the MVPs can point users at that
entry on your webpage - rather than require that users have
to mess with Notepad and/or Regedit to install this fix?

Thanks for whatever help you can provide.



Best I can do for now. <tm>


Bill




Reply With Quote
Sponsored Links
  #2 (permalink)  
Old 12-15-2007
Plato
 

Posts: n/a
Re: BUGFIX: Crashes in Internet Explorer 6 under WXP-SP2 after December Patch Tuesday
Bill Drake wrote:
>
> Two days ago, I posted regarding the problem with Internet
> Explorer 6 crashing when starting up if the default homepage


Use Firefox.

--
http://www.bootdisk.com/


Reply With Quote
  #3 (permalink)  
Old 12-15-2007
Ottmar Freudenberger
 

Posts: n/a
Re: BUGFIX: Crashes in Internet Explorer 6 under WXP-SP2 after December Patch Tuesday
"Bill Drake" <bdrake@telus.net> schrieb:

> The problem occurs because the KB942615 update
> installs an updated copy of urlmon.dll - but does NOT
> install the required Registry Edit that applies the bugfix
> so that urlmon.dll works properly in IE6.
>
> The required Registry Entry is as follows:
>
> ---------------------begin KB942615FIX.reg--------------------
>
> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
> Internet Explorer\Main\FeatureControl\
> FEATURE_PROTECT_DECOMPRESSION_FILTER_FROM_ABORT_KB 942367]
> "*"=dword:00000001
>
> -----------------------end KB942615FIX.reg--------------------
>
> Note: 1. The information within the two square brackets should
> all be on ONE line. If your newsgroup reader has split
> that information onto two or more lines - remove the
> carriage returns so that all the info in between the
> square brackets is on the third line in the
> KB942615FIX.reg file, and the fourth line starts with "*".
>
> 2. There MUST be a blank line at the very bottom of the file.
> Do NOT let the last character in the file end at the far
> right of the last line. The registry edit will FAIL if there
> is not a valid single carriage return as the last item in the
> KB942615FIX.reg file.
>
> To make the file and apply the patch:
>
> 1. Open Notepad and copy all the information between the
> "Begin" and "End" lines above - from the beginning of the
> word "Windows" to the beginning of the next line following
> "00000001" - into Notepad. Save the notepad file as
> KB942615FIX.reg, open Notepad and remove the extra
> carriage returns as per Note 1 above. Also confirm the
> presence of the final carriage return as per Note 2 above.
> Save whatever changes to the KB94615FIX.reg file were
> required to bring the file into a workable form.
>
> 2. Once you have the working file, close Notepad. Open
> Windows Explorer and go to wherever you saved the file.
> Double-click the file. Windows will ask you if you want
> to merge the data in the Registry file into the Windows
> Registry. Click Yes. Windows should respond that it
> has successfully merged the KB942615FIX.reg file
> info into the Registry.
>
> 3. Shut down and reboot your computer. Open Internet
> Explorer and navigate to whatever web page was giving
> you trouble before. You should now find that Internet
> Explorer works properly again, just as it did before the
> December version of the Internet Explorer Cumulative
> Security Update was installed.
>
>
> Comment to MVPs:
>
> Kelly, could you please incorporate this info into one of your
> Regfix files so the rest of the MVPs can point users at that
> entry on your webpage - rather than require that users have
> to mess with Notepad and/or Regedit to install this fix?


I'm not Kelly nor an MVP, but you may find
http://groups.google.com/groups?selm...individual.net
useful in the meantime.

BTW: Rebooting Windows or logging out isn't neccessary to get
the "fix" working. Shutting all IE6 windows after or before
applying the "fix" is sufficent.

Bye,
Freudi
Reply With Quote
  #4 (permalink)  
Old 12-15-2007
Peter
 

Posts: n/a
RE: BUGFIX: Crashes in Internet Explorer 6 under WXP-SP2 after Decembe
As much as I appreciate the help I do not understand a word of the supposed
Fix.
Can you tell us what to do in laymans language please as I am not and I
suspect a lot of others are not PC Literate.

Thanks

"Bill Drake" wrote:

> Two days ago, I posted regarding the problem with Internet
> Explorer 6 crashing when starting up if the default homepage
> was set to "My MSN" and the page was heavily customized.
>
> Other users chimed in to say they were experiencing similar
> problems. All the problems resulted in a dialog box saying
> that "Internet Explorer has encountered a serious error and
> must close". If the user checked the technical info on the
> error, the readout confirmed a problem with urlmon.dll.
>
> With the help of several MVPs, other users with the problem,
> and Kurt Falde from Microsoft - the problem has now been
> localized and a fix has been tested and verified for the last
> 24 hours.
>
> Those who are experiencing this problem need to make a
> Registry Edit after the December Patch Tuesday update
> installs the latest Internet Explorer Cumulative Update.
> (The technical name for this update is KB942615.)
>
> The problem occurs because the KB942615 update
> installs an updated copy of urlmon.dll - but does NOT
> install the required Registry Edit that applies the bugfix
> so that urlmon.dll works properly in IE6.
>
> The required Registry Entry is as follows:
>
> ---------------------begin KB942615FIX.reg--------------------
>
> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
> Internet Explorer\Main\FeatureControl\
> FEATURE_PROTECT_DECOMPRESSION_FILTER_FROM_ABORT_KB 942367]
> "*"=dword:00000001
>
> -----------------------end KB942615FIX.reg--------------------
>
> Note: 1. The information within the two square brackets should
> all be on ONE line. If your newsgroup reader has split
> that information onto two or more lines - remove the
> carriage returns so that all the info in between the
> square brackets is on the third line in the
> KB942615FIX.reg file, and the fourth line starts with "*".
>
> 2. There MUST be a blank line at the very bottom of the file.
> Do NOT let the last character in the file end at the far
> right of the last line. The registry edit will FAIL if there
> is not a valid single carriage return as the last item in the
> KB942615FIX.reg file.
>
> To make the file and apply the patch:
>
> 1. Open Notepad and copy all the information between the
> "Begin" and "End" lines above - from the beginning of the
> word "Windows" to the beginning of the next line following
> "00000001" - into Notepad. Save the notepad file as
> KB942615FIX.reg, open Notepad and remove the extra
> carriage returns as per Note 1 above. Also confirm the
> presence of the final carriage return as per Note 2 above.
> Save whatever changes to the KB94615FIX.reg file were
> required to bring the file into a workable form.
>
> 2. Once you have the working file, close Notepad. Open
> Windows Explorer and go to wherever you saved the file.
> Double-click the file. Windows will ask you if you want
> to merge the data in the Registry file into the Windows
> Registry. Click Yes. Windows should respond that it
> has successfully merged the KB942615FIX.reg file
> info into the Registry.
>
> 3. Shut down and reboot your computer. Open Internet
> Explorer and navigate to whatever web page was giving
> you trouble before. You should now find that Internet
> Explorer works properly again, just as it did before the
> December version of the Internet Explorer Cumulative
> Security Update was installed.
>
>
> Comment to MVPs:
>
> Kelly, could you please incorporate this info into one of your
> Regfix files so the rest of the MVPs can point users at that
> entry on your webpage - rather than require that users have
> to mess with Notepad and/or Regedit to install this fix?
>
> Thanks for whatever help you can provide.
>
>
>
> Best I can do for now. <tm>
>
>
> Bill
>
>
>
>
>

Reply With Quote
  #5 (permalink)  
Old 12-15-2007
Bill Drake
 

Posts: n/a
Re: BUGFIX: Crashes in Internet Explorer 6 under WXP-SP2 after Decembe
Hi, Peter. If you don't understand this, then you wait for the
bugfix regfile that I asked Kelly (one of the MS MVPs) to create.

Note: This work is NOT something that should be attempted by
those who are unable to read, comprehend and follow
instructions. If you aren't willing or able to deal with this
in a competent technical manner, DON'T do the work.

Bill


Peter wrote:
> As much as I appreciate the help I do not understand a word of the
> supposed Fix.
> Can you tell us what to do in laymans language please as I am not
> and I suspect a lot of others are not PC Literate.
>
> Thanks
>
> "Bill Drake" wrote:
>
>> Two days ago, I posted regarding the problem with Internet
>> Explorer 6 crashing when starting up if the default homepage
>> was set to "My MSN" and the page was heavily customized.
>>
>> Other users chimed in to say they were experiencing similar
>> problems. All the problems resulted in a dialog box saying
>> that "Internet Explorer has encountered a serious error and
>> must close". If the user checked the technical info on the
>> error, the readout confirmed a problem with urlmon.dll.
>>
>> With the help of several MVPs, other users with the problem,
>> and Kurt Falde from Microsoft - the problem has now been
>> localized and a fix has been tested and verified for the last
>> 24 hours.
>>
>> Those who are experiencing this problem need to make a
>> Registry Edit after the December Patch Tuesday update
>> installs the latest Internet Explorer Cumulative Update.
>> (The technical name for this update is KB942615.)
>>
>> The problem occurs because the KB942615 update
>> installs an updated copy of urlmon.dll - but does NOT
>> install the required Registry Edit that applies the bugfix
>> so that urlmon.dll works properly in IE6.
>>
>> The required Registry Entry is as follows:
>>
>> ---------------------begin KB942615FIX.reg--------------------
>>
>> Windows Registry Editor Version 5.00
>>
>> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
>> Internet Explorer\Main\FeatureControl\
>> FEATURE_PROTECT_DECOMPRESSION_FILTER_FROM_ABORT_KB 942367]
>> "*"=dword:00000001
>>
>> -----------------------end KB942615FIX.reg--------------------
>>
>> Note: 1. The information within the two square brackets should
>> all be on ONE line. If your newsgroup reader has split
>> that information onto two or more lines - remove the
>> carriage returns so that all the info in between the
>> square brackets is on the third line in the
>> KB942615FIX.reg file, and the fourth line starts with
>> "*".
>>
>> 2. There MUST be a blank line at the very bottom of the
>> file. Do NOT let the last character in the file end
>> at the far right of the last line. The registry edit
>> will FAIL if there is not a valid single carriage
>> return as the last item in the KB942615FIX.reg file.
>>
>> To make the file and apply the patch:
>>
>> 1. Open Notepad and copy all the information between the
>> "Begin" and "End" lines above - from the beginning of the
>> word "Windows" to the beginning of the next line following
>> "00000001" - into Notepad. Save the notepad file as
>> KB942615FIX.reg, open Notepad and remove the extra
>> carriage returns as per Note 1 above. Also confirm the
>> presence of the final carriage return as per Note 2 above.
>> Save whatever changes to the KB94615FIX.reg file were
>> required to bring the file into a workable form.
>>
>> 2. Once you have the working file, close Notepad. Open
>> Windows Explorer and go to wherever you saved the file.
>> Double-click the file. Windows will ask you if you want
>> to merge the data in the Registry file into the Windows
>> Registry. Click Yes. Windows should respond that it
>> has successfully merged the KB942615FIX.reg file
>> info into the Registry.
>>
>> 3. Shut down and reboot your computer. Open Internet
>> Explorer and navigate to whatever web page was giving
>> you trouble before. You should now find that Internet
>> Explorer works properly again, just as it did before the
>> December version of the Internet Explorer Cumulative
>> Security Update was installed.
>>
>>
>> Comment to MVPs:
>>
>> Kelly, could you please incorporate this info into one of your
>> Regfix files so the rest of the MVPs can point users at that
>> entry on your webpage - rather than require that users have
>> to mess with Notepad and/or Regedit to install this fix?
>>
>> Thanks for whatever help you can provide.
>>
>>
>>
>> Best I can do for now. <tm>
>>
>>
>> Bill




Reply With Quote
  #6 (permalink)  
Old 12-15-2007
Peter
 

Posts: n/a
Re: BUGFIX: Crashes in Internet Explorer 6 under WXP-SP2 after Dec
Thanks Bill.

"Bill Drake" wrote:

> Hi, Peter. If you don't understand this, then you wait for the
> bugfix regfile that I asked Kelly (one of the MS MVPs) to create.
>
> Note: This work is NOT something that should be attempted by
> those who are unable to read, comprehend and follow
> instructions. If you aren't willing or able to deal with this
> in a competent technical manner, DON'T do the work.
>
> Bill
>
>
> Peter wrote:
> > As much as I appreciate the help I do not understand a word of the
> > supposed Fix.
> > Can you tell us what to do in laymans language please as I am not
> > and I suspect a lot of others are not PC Literate.
> >
> > Thanks
> >
> > "Bill Drake" wrote:
> >
> >> Two days ago, I posted regarding the problem with Internet
> >> Explorer 6 crashing when starting up if the default homepage
> >> was set to "My MSN" and the page was heavily customized.
> >>
> >> Other users chimed in to say they were experiencing similar
> >> problems. All the problems resulted in a dialog box saying
> >> that "Internet Explorer has encountered a serious error and
> >> must close". If the user checked the technical info on the
> >> error, the readout confirmed a problem with urlmon.dll.
> >>
> >> With the help of several MVPs, other users with the problem,
> >> and Kurt Falde from Microsoft - the problem has now been
> >> localized and a fix has been tested and verified for the last
> >> 24 hours.
> >>
> >> Those who are experiencing this problem need to make a
> >> Registry Edit after the December Patch Tuesday update
> >> installs the latest Internet Explorer Cumulative Update.
> >> (The technical name for this update is KB942615.)
> >>
> >> The problem occurs because the KB942615 update
> >> installs an updated copy of urlmon.dll - but does NOT
> >> install the required Registry Edit that applies the bugfix
> >> so that urlmon.dll works properly in IE6.
> >>
> >> The required Registry Entry is as follows:
> >>
> >> ---------------------begin KB942615FIX.reg--------------------
> >>
> >> Windows Registry Editor Version 5.00
> >>
> >> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
> >> Internet Explorer\Main\FeatureControl\
> >> FEATURE_PROTECT_DECOMPRESSION_FILTER_FROM_ABORT_KB 942367]
> >> "*"=dword:00000001
> >>
> >> -----------------------end KB942615FIX.reg--------------------
> >>
> >> Note: 1. The information within the two square brackets should
> >> all be on ONE line. If your newsgroup reader has split
> >> that information onto two or more lines - remove the
> >> carriage returns so that all the info in between the
> >> square brackets is on the third line in the
> >> KB942615FIX.reg file, and the fourth line starts with
> >> "*".
> >>
> >> 2. There MUST be a blank line at the very bottom of the
> >> file. Do NOT let the last character in the file end
> >> at the far right of the last line. The registry edit
> >> will FAIL if there is not a valid single carriage
> >> return as the last item in the KB942615FIX.reg file.
> >>
> >> To make the file and apply the patch:
> >>
> >> 1. Open Notepad and copy all the information between the
> >> "Begin" and "End" lines above - from the beginning of the
> >> word "Windows" to the beginning of the next line following
> >> "00000001" - into Notepad. Save the notepad file as
> >> KB942615FIX.reg, open Notepad and remove the extra
> >> carriage returns as per Note 1 above. Also confirm the
> >> presence of the final carriage return as per Note 2 above.
> >> Save whatever changes to the KB94615FIX.reg file were
> >> required to bring the file into a workable form.
> >>
> >> 2. Once you have the working file, close Notepad. Open
> >> Windows Explorer and go to wherever you saved the file.
> >> Double-click the file. Windows will ask you if you want
> >> to merge the data in the Registry file into the Windows
> >> Registry. Click Yes. Windows should respond that it
> >> has successfully merged the KB942615FIX.reg file
> >> info into the Registry.
> >>
> >> 3. Shut down and reboot your computer. Open Internet
> >> Explorer and navigate to whatever web page was giving
> >> you trouble before. You should now find that Internet
> >> Explorer works properly again, just as it did before the
> >> December version of the Internet Explorer Cumulative
> >> Security Update was installed.
> >>
> >>
> >> Comment to MVPs:
> >>
> >> Kelly, could you please incorporate this info into one of your
> >> Regfix files so the rest of the MVPs can point users at that
> >> entry on your webpage - rather than require that users have
> >> to mess with Notepad and/or Regedit to install this fix?
> >>
> >> Thanks for whatever help you can provide.
> >>
> >>
> >>
> >> Best I can do for now. <tm>
> >>
> >>
> >> Bill

>
>
>
>

Reply With Quote
  #7 (permalink)  
Old 12-15-2007
Ottmar Freudenberger
 

Posts: n/a
Re: BUGFIX: Crashes in Internet Explorer 6 under WXP-SP2 after Decembe
"Peter" <Peter@discussions.microsoft.com> schrieb:

> As much as I appreciate the help I do not understand a word of the supposed
> Fix.


http://groups.google.com/groups?selm...individual.net

Bye,
Freudi
Reply With Quote
  #8 (permalink)  
Old 12-15-2007
realcestmoi
 

Posts: n/a
Re: BUGFIX: Crashes in Internet Explorer 6 under WXP-SP2 after December Patch Tuesday
the fix as attachement


"Bill Drake" <bdrake@telus.net> wrote in message
news:OD5or4rPIHA.5400@TK2MSFTNGP04.phx.gbl...
> Two days ago, I posted regarding the problem with Internet
> Explorer 6 crashing when starting up if the default homepage
> was set to "My MSN" and the page was heavily customized.
>
> Other users chimed in to say they were experiencing similar
> problems. All the problems resulted in a dialog box saying
> that "Internet Explorer has encountered a serious error and
> must close". If the user checked the technical info on the
> error, the readout confirmed a problem with urlmon.dll.
>
> With the help of several MVPs, other users with the problem,
> and Kurt Falde from Microsoft - the problem has now been
> localized and a fix has been tested and verified for the last
> 24 hours.
>
> Those who are experiencing this problem need to make a
> Registry Edit after the December Patch Tuesday update
> installs the latest Internet Explorer Cumulative Update.
> (The technical name for this update is KB942615.)
>
> The problem occurs because the KB942615 update
> installs an updated copy of urlmon.dll - but does NOT
> install the required Registry Edit that applies the bugfix
> so that urlmon.dll works properly in IE6.
>
> The required Registry Entry is as follows:
>
> ---------------------begin KB942615FIX.reg--------------------
>
> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
> Internet Explorer\Main\FeatureControl\
> FEATURE_PROTECT_DECOMPRESSION_FILTER_FROM_ABORT_KB 942367]
> "*"=dword:00000001
>
> -----------------------end KB942615FIX.reg--------------------
>
> Note: 1. The information within the two square brackets should
> all be on ONE line. If your newsgroup reader has split
> that information onto two or more lines - remove the
> carriage returns so that all the info in between the
> square brackets is on the third line in the
> KB942615FIX.reg file, and the fourth line starts with "*".
>
> 2. There MUST be a blank line at the very bottom of the file.
> Do NOT let the last character in the file end at the far
> right of the last line. The registry edit will FAIL if
> there
> is not a valid single carriage return as the last item in
> the
> KB942615FIX.reg file.
>
> To make the file and apply the patch:
>
> 1. Open Notepad and copy all the information between the
> "Begin" and "End" lines above - from the beginning of the
> word "Windows" to the beginning of the next line following
> "00000001" - into Notepad. Save the notepad file as
> KB942615FIX.reg, open Notepad and remove the extra
> carriage returns as per Note 1 above. Also confirm the
> presence of the final carriage return as per Note 2 above.
> Save whatever changes to the KB94615FIX.reg file were
> required to bring the file into a workable form.
>
> 2. Once you have the working file, close Notepad. Open
> Windows Explorer and go to wherever you saved the file.
> Double-click the file. Windows will ask you if you want
> to merge the data in the Registry file into the Windows
> Registry. Click Yes. Windows should respond that it
> has successfully merged the KB942615FIX.reg file
> info into the Registry.
>
> 3. Shut down and reboot your computer. Open Internet
> Explorer and navigate to whatever web page was giving
> you trouble before. You should now find that Internet
> Explorer works properly again, just as it did before the
> December version of the Internet Explorer Cumulative
> Security Update was installed.
>
>
> Comment to MVPs:
>
> Kelly, could you please incorporate this info into one of your
> Regfix files so the rest of the MVPs can point users at that
> entry on your webpage - rather than require that users have
> to mess with Notepad and/or Regedit to install this fix?
>
> Thanks for whatever help you can provide.
>
>
>
> Best I can do for now. <tm>
>
>
> Bill
>
>
>
>





Reply With Quote
  #9 (permalink)  
Old 12-15-2007
HeyBub
 

Posts: n/a
Re: BUGFIX: Crashes in Internet Explorer 6 under WXP-SP2 after December Patch Tuesday
Plato wrote:
> Bill Drake wrote:
>>
>> Two days ago, I posted regarding the problem with Internet
>> Explorer 6 crashing when starting up if the default homepage

>
> Use Firefox.


Can't. Firefox causes the cat to develop warts.


Reply With Quote
  #10 (permalink)  
Old 12-15-2007
grandpa59
 

Posts: n/a
Re: BUGFIX: Crashes in Internet Explorer 6 under WXP-SP2 after Dec


"realcestmoi" wrote:

> the fix as attachement
>
>
> "Bill Drake" <bdrake@telus.net> wrote in message
> news:OD5or4rPIHA.5400@TK2MSFTNGP04.phx.gbl...
> > Two days ago, I posted regarding the problem with Internet
> > Explorer 6 crashing when starting up if the default homepage
> > was set to "My MSN" and the page was heavily customized.
> >
> > Other users chimed in to say they were experiencing similar
> > problems. All the problems resulted in a dialog box saying
> > that "Internet Explorer has encountered a serious error and
> > must close". If the user checked the technical info on the
> > error, the readout confirmed a problem with urlmon.dll.
> >
> > With the help of several MVPs, other users with the problem,
> > and Kurt Falde from Microsoft - the problem has now been
> > localized and a fix has been tested and verified for the last
> > 24 hours.
> >
> > Those who are experiencing this problem need to make a
> > Registry Edit after the December Patch Tuesday update
> > installs the latest Internet Explorer Cumulative Update.
> > (The technical name for this update is KB942615.)
> >
> > The problem occurs because the KB942615 update
> > installs an updated copy of urlmon.dll - but does NOT
> > install the required Registry Edit that applies the bugfix
> > so that urlmon.dll works properly in IE6.
> >
> > The required Registry Entry is as follows:
> >
> > ---------------------begin KB942615FIX.reg--------------------
> >
> > Windows Registry Editor Version 5.00
> >
> > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
> > Internet Explorer\Main\FeatureControl\
> > FEATURE_PROTECT_DECOMPRESSION_FILTER_FROM_ABORT_KB 942367]
> > "*"=dword:00000001
> >
> > -----------------------end KB942615FIX.reg--------------------
> >
> > Note: 1. The information within the two square brackets should
> > all be on ONE line. If your newsgroup reader has split
> > that information onto two or more lines - remove the
> > carriage returns so that all the info in between the
> > square brackets is on the third line in the
> > KB942615FIX.reg file, and the fourth line starts with "*".
> >
> > 2. There MUST be a blank line at the very bottom of the file.
> > Do NOT let the last character in the file end at the far
> > right of the last line. The registry edit will FAIL if
> > there
> > is not a valid single carriage return as the last item in
> > the
> > KB942615FIX.reg file.
> >
> > To make the file and apply the patch:
> >
> > 1. Open Notepad and copy all the information between the
> > "Begin" and "End" lines above - from the beginning of the
> > word "Windows" to the beginning of the next line following
> > "00000001" - into Notepad. Save the notepad file as
> > KB942615FIX.reg, open Notepad and remove the extra
> > carriage returns as per Note 1 above. Also confirm the
> > presence of the final carriage return as per Note 2 above.
> > Save whatever changes to the KB94615FIX.reg file were
> > required to bring the file into a workable form.
> >
> > 2. Once you have the working file, close Notepad. Open
> > Windows Explorer and go to wherever you saved the file.
> > Double-click the file. Windows will ask you if you want
> > to merge the data in the Registry file into the Windows
> > Registry. Click Yes. Windows should respond that it
> > has successfully merged the KB942615FIX.reg file
> > info into the Registry.
> >
> > 3. Shut down and reboot your computer. Open Internet
> > Explorer and navigate to whatever web page was giving
> > you trouble before. You should now find that Internet
> > Explorer works properly again, just as it did before the
> > December version of the Internet Explorer Cumulative
> > Security Update was installed.
> >
> >
> > Comment to MVPs:
> >
> > Kelly, could you please incorporate this info into one of your
> > Regfix files so the rest of the MVPs can point users at that
> > entry on your webpage - rather than require that users have
> > to mess with Notepad and/or Regedit to install this fix?
> >
> > Thanks for whatever help you can provide.
> >
> >
> >
> > Best I can do for now. <tm>
> >
> >
> > Bill
> >
> >
> >
> >

> Looks like MS found a way to shove IE7 down our throats.I had the same problem after that update.I uninstalled the update,installed IE7 wich reinstall the update again,but with IE7 the problem went away.
>
>

Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
December black tuesday overview, (Tue, Dec 11th) Steve Security News 0 12-11-2007 20:20
Microsoft to launch test build of Internet Explorer refresh in December BlogFeed Windows Vista Blogs Forum 0 11-11-2007 09:10
Patch Tuesday.. Paul Security News 0 10-10-2007 02:40
Patch Tuesday -- What You Need to Know Steve Security News 0 07-11-2007 05:40
Patch Tuesday THIS Tuesday Steve Security News 0 04-03-2007 21:31




All times are GMT +1. The time now is 23:47.




Driver Scanner - Free Scan Now

Vistaheads.com is part of the Heads Network. See also XPHeads.com , Win7Heads.com and Win8Heads.com.


Design by Vjacheslav Trushkin for phpBBStyles.com.
Powered by vBulletin® Version 3.6.7
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.6.0 RC 2

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120