IE11 crashing when opening mht files after installing KB3185330 or KB3192391

Has anyone found a solution to KB3185330 and KB3192391 crashing IE11 when trying to open a mht file from another program(ex. Outlook 2013 attachment).  It seems that if the file is saved to a different directory first then it works fine.  Otherwise IE will crash with the faulting module varying from INETCOMM.DLL, ntdll.dll or StackHash_xxxx.  It works fine again after uninstalling the updates.  Thank you for your help.

Machines consist of Windows 7 Pro, IE11, Office 2013.

I haven't found any talk about this yet but it seems similar to what I found here. 
http://answers.microsoft.com/en-us/ie/forum/ie11-windows_7/vs-2005-application-web-browser-control-crashes/a7010104-1fbc-4db0-a8bc-6dc1b53f6947

 

Question Info


Last updated February 20, 2019 Views 6,764 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

I also got the same problem on several of a customers computers. I've tried everything I could think of (besides removing all of the recently installed updates). I've chosen to just use Chrome for the time being, until a solution has been found. 

I couldn't find the updates you were referring to. I do however hope that a solution/hotfix will soon be found. 

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I also got the same problem on several of a customers computers. I've tried everything I could think of (besides removing all of the recently installed updates). I've chosen to just use Chrome for the time being, until a solution has been found. 

I couldn't find the updates you were referring to. I do however hope that a solution/hotfix will soon be found. 

check this out!

> https://support.microsoft.com/en-us/kb/3185330

> https://support.microsoft.com/en-us/kb/3192391

Nothing will go wrong on my watch.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Yeah, I had to do a System Restore and slowly add the patches to find the culprits.  Unfortunately Microsoft in their "Infinite Wisdom" wants to send out cumulative patches now for Window 7 so if I don't install these on our workstations they'll be vulnerable to a whole host of other problems.  Hopefully more people see this and a fix is released.  Seems like it's not exclusive to Outlook attachments, but any application that is trying to open a mht file in Internet Explorer.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I too have this issue as well.  Only uninstalling KB3192391 would resolve the issue.  MS please resolve the issue.  Thank you.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Yes I've encountered this issue and have found more specifics about what seems to trigger it, the trigger being really odd.

http://imgur.com/L4Y7LCI

http://imgur.com/SeH9PjF

For both KBs the error was the same, an access exception (bad pointer) in ntdll.dll

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    IEXPLORE.EXE
  Application Version:    11.0.9600.18500
  Application Timestamp:    57edec53
  Fault Module Name:    ntdll.dll
  Fault Module Version:    6.1.7601.23543
  Fault Module Timestamp:    57d2f8a2
  Exception Code:    c0000005
  Exception Offset:    00032ed5
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1033
  Additional Information 1:    0a9e
  Additional Information 2:    0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:    0a9e
  Additional Information 4:    0a9e372d3b4ad19135b953a78882e789

Like you I discovered the issue after installing KB3185330 and found that restoring to the previous system state fixed it. From there I created a clean virtual machine image of Windows 7 Pro x64 SP1 US-EN (MSDN ISO, no OEM cruft) and activated it with a developer key. After using Windows Update to install all required and optional updates until only KB3185330 remained in the list I tested it with a MHT file I had problems with and did not encounter the error. Then I proceeded with installing KB3185330 (October rollup) and got the error. Reverting removed the error but then manually installing KB3192391 (October rollup, security fixes only) brought the error back. I then carried out a battery of tests with this clean VM image to try and identify the problem or find a work around.

What I found is that some MHT files triggered the error while others did not. I found that the contents of the file didn't matter (even blank files), instead I found the filename triggers the crash.

For example create or rename an MHT file to this name and it will work with either patch installed:

    A A A A A A A A A A A A A A A A A A A A A A.mht

But add one more space and another A. This filename will trigger the crash:

    A A A A A A A A A A A A A A A A A A A A A A A.mht

Here are some more working filenames (it seems you can substitute the A for other letters, only spaces are important)

    a a a a a a a a a a a a a a a a a a a a a a.mht

    A   A   A   A   A   A   A   A   A.mht
    A    A    A    A    A    A    A.mht

    AAAAAAAAA AAAAA AAAAAAAAAAA  AAAAAAAA A A AAAA AA AAA AAAAA AAAA.mht
    AAAAAAAAA AAAAA AAAAAAAAAAA  AAAAAAAA A A AAAA AA AAA AAAAAAAAAAA.mht
    AAAAAAAAA AAAAA AAAAAAAAAAA  AAAAAAAA A A AAAA AA AAA AAAAAAAAAAAA.mht
    AAAAAAAAA AAAAA AAAAAAAAAAA  AAAAAAAA A A AAAA AA AAA AA AAAAAAA.mht

And their similar but not working (crashes) counterparts:

    a a a a a a a a a a a a a a a a a a a a a a a.mht
    A   A   A   A   A   A   A   A   A   A.mht
    A    A    A    A    A    A    A    A.mht

    AAAAAAAAA AAAAA AAAAAAAAAAA  AAAAAAAA A A AAAA AA AAA AAAAA AAAAA.mht
    AAAAAAAAA AAAAA AAAAAAAAAAA  AAAAAAAA A A AAAA AA AAA AA AAAAAAAA.mht
    AAAAAAAAA AAAAA AAAAAAAAAAA  AAAAAAAA A A AAAA AA AAA AA AAAAAAAAA.mht
    AAAAAAAAA AAAAA AAAAAAAAAAA  AAAAAAAA A A AAAA AA AAA AA AAA AAA.mht

Moving the file to another folder or the root of the drive has no effect, nor does moving it to another drive (I've used the boot drive, a secondary partition and a network drive all with identical results). Typing the file path into the address bar instead of double clicking in explorer made no difference either. The same names but with the .htm or .html extension do work (no crash) but this is useless for MHT files since it displays the raw contents.

I've also tried all of the following individually with no effect on the crash or additional information found:

  • Booting in Safe Mode
  • Turning off Windows Defender real time protection
  • Toggling Compatiblity Mode off in IE for all zones
  • Toggling Compatiblity Mode on in IE for all zones
  • Changing all zones security to High in IE
  • Changing all zones security to Low in IE
  • Setting Temporary Internet Files to 'Never'
  • Setting History retention to 0 days
  • Setting Privacy to allow all cookies
  • Turning off the Pop-up Blocker
  • Enabling Script Debugging
  • Turning on 'Always record developer console messages'
  • Running as an administrator
  • Running as a guest

So all I can conclusively find is that the issue has to do with the name of MHT files and spaces seem to be factor in which names trigger an exception and which don't.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Yes I've encountered this issue and have found more specifics about what seems to trigger it, the trigger being really odd.

http://imgur.com/L4Y7LCI

http://imgur.com/SeH9PjF

For both KBs the error was the same, an access exception (bad pointer) in ntdll.dll

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    IEXPLORE.EXE
  Application Version:    11.0.9600.18500
  Application Timestamp:    57edec53
  Fault Module Name:    ntdll.dll
  Fault Module Version:    6.1.7601.23543
  Fault Module Timestamp:    57d2f8a2
  Exception Code:    c0000005
  Exception Offset:    00032ed5
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1033
  Additional Information 1:    0a9e
  Additional Information 2:    0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:    0a9e
  Additional Information 4:    0a9e372d3b4ad19135b953a78882e789

Like you I discovered the issue after installing KB3185330 and found that restoring to the previous system state fixed it. From there I created a clean virtual machine image of Windows 7 Pro x64 SP1 US-EN (MSDN ISO, no OEM cruft) and activated it with a developer key. After using Windows Update to install all required and optional updates until only KB3185330 remained in the list I tested it with a MHT file I had problems with and did not encounter the error. Then I proceeded with installing KB3185330 (October rollup) and got the error. Reverting removed the error but then manually installing KB3192391 (October rollup, security fixes only) brought the error back. I then carried out a battery of tests with this clean VM image to try and identify the problem or find a work around.

What I found is that some MHT files triggered the error while others did not. I found that the contents of the file didn't matter (even blank files), instead I found the filename triggers the crash.

For example create or rename an MHT file to this name and it will work with either patch installed:

    A A A A A A A A A A A A A A A A A A A A A A.mht

But add one more space and another A. This filename will trigger the crash:

    A A A A A A A A A A A A A A A A A A A A A A A.mht

Here are some more working filenames (it seems you can substitute the A for other letters, only spaces are important)

    a a a a a a a a a a a a a a a a a a a a a a.mht

    A   A   A   A   A   A   A   A   A.mht
    A    A    A    A    A    A    A.mht

    AAAAAAAAA AAAAA AAAAAAAAAAA  AAAAAAAA A A AAAA AA AAA AAAAA AAAA.mht
    AAAAAAAAA AAAAA AAAAAAAAAAA  AAAAAAAA A A AAAA AA AAA AAAAAAAAAAA.mht
    AAAAAAAAA AAAAA AAAAAAAAAAA  AAAAAAAA A A AAAA AA AAA AAAAAAAAAAAA.mht
    AAAAAAAAA AAAAA AAAAAAAAAAA  AAAAAAAA A A AAAA AA AAA AA AAAAAAA.mht

And their similar but not working (crashes) counterparts:

    a a a a a a a a a a a a a a a a a a a a a a a.mht
    A   A   A   A   A   A   A   A   A   A.mht
    A    A    A    A    A    A    A    A.mht

    AAAAAAAAA AAAAA AAAAAAAAAAA  AAAAAAAA A A AAAA AA AAA AAAAA AAAAA.mht
    AAAAAAAAA AAAAA AAAAAAAAAAA  AAAAAAAA A A AAAA AA AAA AA AAAAAAAA.mht
    AAAAAAAAA AAAAA AAAAAAAAAAA  AAAAAAAA A A AAAA AA AAA AA AAAAAAAAA.mht
    AAAAAAAAA AAAAA AAAAAAAAAAA  AAAAAAAA A A AAAA AA AAA AA AAA AAA.mht

Moving the file to another folder or the root of the drive has no effect, nor does moving it to another drive (I've used the boot drive, a secondary partition and a network drive all with identical results). Typing the file path into the address bar instead of double clicking in explorer made no difference either. The same names but with the .htm or .html extension do work (no crash) but this is useless for MHT files since it displays the raw contents.

I've also tried all of the following individually with no effect on the crash or additional information found:

  • Booting in Safe Mode
  • Turning off Windows Defender real time protection
  • Toggling Compatiblity Mode off in IE for all zones
  • Toggling Compatiblity Mode on in IE for all zones
  • Changing all zones security to High in IE
  • Changing all zones security to Low in IE
  • Setting Temporary Internet Files to 'Never'
  • Setting History retention to 0 days
  • Setting Privacy to allow all cookies
  • Turning off the Pop-up Blocker
  • Enabling Script Debugging
  • Turning on 'Always record developer console messages'
  • Running as an administrator
  • Running as a guest

So all I can conclusively find is that the issue has to do with the name of MHT files and spaces seem to be factor in which names trigger an exception and which don't.

Interesting results.  However, I was able to drag(save) the attached mht file from Outlook 2013 to my desktop and it opened perfectly fine.  Just not when double-clicked from the email.

3 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

We have the same problem and it stopped our customers from being able to work until the specific problematic was found. this needs to be fixed ASAP by Microsoft!

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Same symptoms here on Windows 8.1/IE11; in this case the culprit appears to be KB3192392.  Would rather not uninstall this KB and lose other security "improvements" in the process...

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Happens in Windows 10 as well. Removing KB3192441  resolved the problem.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

We have had customers impacted by this windows update around mht files - we've provided details in this bulletin update on the specifics we found around the cause.

<Advertisement removed>

In summary, the length of the full path including the filename seems to be causing the issue... any more than 121 characters and the host application crashes.  Hope MS fixes this soon.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.