enter image description here

This started happening shortly after Meltdown/Spectre was in the news. I've tried:

  • Uninstalling and reinstalling IE.
  • Resetting IE settings
  • Uninstalling KB4056892.

Searching yields results for AMD processor PCs having boot problems, but I'm on an Intel and have no other noticeable symptoms. I'm on Win 10 Enterprise (1709 build 16299.125).


Uninstall IE and then reinstall it:

  • Press Win, type programs, and select Add or remove programs.
  • Select Turn Windows features on or off.
  • Clear the box for Internet Explorer 11.
  • After uninstallation completes (reboot may be needed), check the box for Internet Explorer 11) and complete reinstallation.

Reinstall IE

That said, IE11 is deprecated, and Microsoft would prefer you use Edge, , whether or not it meets your needs.

  • I performed these steps and it did not help. I use IE to test web site changes since a small percentage of my users still use IE. I use Chrome :) – Dzejms Feb 14 '18 at 17:44
  • IE11 isn't deprecated. Microsoft just recently as this week, continues to fix issues with IE11, they have not announced an EOS (End of Support) for IE11 at this time for Windows 10 either. – Ramhound Feb 14 '18 at 18:41

Open and admin cmd window and issue the following command:

C:\WINDOWS\system32>sfc /scannow

I received the following results:

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

After that, IE launched without issue. The command was obtained from this post: https://answers.microsoft.com/en-us/ie/forum/ie10-windows_8/ie10-wont-open-ieframedll-error-pops-on-startup/9c6a60d8-8769-4d98-9f61-11cc99e750c5

Thanks to @Ramhound for walking me through the debug process where ieframe.dll was listed as one of the faulting modules.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.