IE 6.0 returns error when the Favorites pane is displayed

[Bridget Dorward]

We have encountered this problem on several PCs. So far,
there is no common thread. We've seen it on different
operating systems and hardware platforms.

If you click the File Menu when your Favorites pane is
displayed, you receive the following error:

"MS Internet Explorer has encountered a problem and needs
to close."

The problem goes away if you close the Favorites pane.

Any ideas?

Thanks

Bridget

 

[H Leboeuf]

IE 6.

Try this: Tools > Internet Options > Advanced > Browsing
Uncheck the Enable 3rd party browser extensions

If this clears your problem then find out who the culprit(s) is/are with
these tools.

Let AD-Aware Scan your system for advertising Spyware
http://www.lavasoftusa.com

and:

SpyBot-S&D
http://security.kolla.de/

p.s Reset the 3rd party browser setting.


Dealing with Unwanted Spyware, Parasites, Toolbars and Search Engines
http://mvps.org/winhelp2002/unwanted.htm

 

[Robert Aldwinckle]

Details? Which module is the crash occurring in? What version?
Which OS? Have you tried an IE Repair (if applicable)?
Alternatively (e.g. XP) simulate one:

For that (inferior) alternative here is an excerpt from a previous reply
to an XP user:

<excerpt>
FWIW this is a list of commands created by extracting from fixie.inf
what an IE Repair would do for Windows 2000 users:

regsvr32 /i browseui.dll
regsvr32 /i shdocvw.dll
regsvr32 /i mshtml.dll
regsvr32 mshtmled.dll
regsvr32 actxprxy.dll
regsvr32 /i urlmon.dll

What that represents is the set of re-registrations which
FixIE.inf indicates would be done for Base.W2K.AddReg

N.B. that neither mshtmled.dll nor actxprxy.dll have an entry point
called DllInstall and hence the /i option can not be used for them.

Neither msjava.dll nor shell32.dll are referred to by FixIE.inf
but those are two other modules which are often suggested to XP users
as needing re-registration for repairing in various circumstances.

Note that such re-registrations are normally done by an IE Repair
during a boot while nothing is running so at the very least I think
that it would be best to ensure that iexplore.exe is not active in your
task list. (Close all visible IE windows and then check that the
iexplore.exe is not in the list of Processes in Task Manager.
Ctrl-Shift-Esc,Ctrl-Tab,i,i,...)
</excerpt>


However, just a brief amount of reading in this newsgroup
should convince anyone that the first thing to check for these days
is the presence of known malware.


HTH

Robert Aldwinckle