I don’t know if this has ever been covered (i searched, but came up naught), but I can not open Internet Explorer. On the plus side, if any pop-ups try to pop up in IE, they get snuffed out. But the ol’ “Internet Explorer has encountered a problem and needs to close. We are sorry for the inconvenience…Send Error ReportDon’t Send”-message pops up instead.
This becomes a problem when I try to manually open IE, or I try to run an update that opens in IE. I can’t even open up Internet Options in my Control Panel (it opens, then immediately closes).
Is this worthy of a new thread? Or can someone point me to an existing thread?
help!
What version of Windows are you using? With 2000 or XP you can go to Start|Run and type sfc /scannow. It may prompt you for your Windows CD. It will then scan your system files and replace any corrupted ones.
With all due respect, my response was helpful because that is how I solved the problem. When neither I nor my computer guru could figure out how to stop IE from mysteriously crashing, we decided to bypass the problem by going to another browser. Since doing so two years ago my non-IE browser hasn’t crashed.
I have seen the CoolWebSearch “virus” cause IE to crash on opening. After running CWSShredder.exe, IE resumed operating normally.
By the way, I switched to Firefox a couple of months ago, and am very happy with it. I am contemplating offering it to my users as part of the standard workstation configuration. If I do so, I will continue to offer IE, as there are sites that seem to require it (bad webmaster! Bad! Bad!), but will put the link to it a level or two down in the startup menus.
I had this problem the other day; certain websites would crash IE6 (under Win98 in my case) - it turned out that one or other of the applications I’d recently installed had brought along its own copy of msvcrt.dll (the Visual C Runtime Library) - in the end, I booted from a floppy, deleted msvcrt.dll from the C drive and extracted a fresh copy from the windows .cab files on my install CD. Worked like a dream.
I meant to say that I diagnosed the fault by scrutinising the report file that it wanted to send; there’s a bit where it tells you the ‘modname’ in which the error occurred and in my case, this said msvcrt.dll.