I'm running XP with all of the current patches
The only thing that I can think of is an IE Repair.
Unfortunately unless you installed IE6sp1 before XPsp1
you can not do a conventional IE Repair
but you can simulate one by doing a bunch of regsvr32 commands.
For that (inferior) alternative here is an excerpt from a previous reply:
<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>
For your particular problem my guess would be that if this fixes
the problem that mshtml.dll or mshtmled.dll will have been
the cause. BTW before doing this you really should make
sure that the versions of the the modules you are going to
re-register are the appropriate ones for your maintenance level.
That is another thing that an IE Repair can do for us automatically.
Good luck
Robert Aldwinckle
---
David said:
I'm very interested in the answer to this problem, as I have the exact same symptoms. I'm running XP with all of the current
patches, and my IE version number is 6.0.2800.1106.xpsp2.030422-1633. This seems to have spontaneously started last weekend,
although there's obviously some direct cause. I'm guessing that some registry key has been modified, but I haven't figured it out
yet.