IE11 KB3191492 - PDF viewer hangs when in an iframe that is removed from DOM

Won’t fix Issue #9600600


Chris H.
Oct 31, 2016
This issue is public.
Found in
  • Internet Explorer
Found in build #
Reported by 7 people

Sign in to watch or report this issue.

Steps to reproduce

Using IE 11 version 11.0.9600.18499 update versions 11.0.36 (KB3191492) with Adobe Reader XI (11.0.18). Open the attached example page and first click the “Inject iframe” button. Then click the “Close iframe” button to show that the built in PDF viewer hangs when it is present in an iframe and that iframe is removed from the DOM.

This works with IE11 after uninstalling the KB3191492 security update and also works with other browsers such as Chrome.


Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Brad E.”

  • I can confirm this bug on IE11 with Win 7 (on Win10 I can’t reproduce it). The complete browser page (not only the iframe) is completely blank several seconds, after removing the iframe from the DOM. This makes IE11 unusable for viewing PDF files. I hope this is fixed soon.

  • We have been able to reproduce the problem on both Win7 and Win8. As we are using the PDF viewer in our corporate software, and a large number of our clients are still using IE11, this is issue has quite a large impact for us. It would be nice if you, Microsoft, could let us know if you are planning on solving this issue, and if so, what the timeline is going to be (can be a ball-park estimation). With this information, we can perform expectation management to our clients, and/or decide to develop around the problem.

  • Microsoft Edge Team

    Changed Status to “Won’t fix”

  • Thank
    you for the feedback and sorry for the delay in getting back to you. This issue appears to have been fixed in Microsoft Edge.
    We’re not presently working on feature bugs in Internet Explorer outside of
    security-related issues. If you have a premier support contract you can visit

    and open
    a support incident and work with an engineer to address this issue.


    Microsoft Edge Team

  • Thanks for getting back to us on this. Good to know that you are not planning on fixing this, so we can take the necessary steps on our side to solve it.

  • Dear Brad,
    I was very surprised about your answer to this bug and can’t really understand why you are not willing to fix it. IE users have been viewing PDF files inside iframes for years without any problems and after the latest security patches this is not possible anymore. I understand that you don’t want to add any new features to IE11, but preventing features to work, that have been used for years, seems completely unreasonable to me. What should I tell a Win7 user, that can’t switch to Edge?

  • I have to agree with Matthias that not fixing this bug in IE does seem unreasonable when it is not possible to use Edge on Windows 7. We have a corporate client using our application with the majority of users running Windows 7 and they also enforce the use of IE. With that in mind, are MS able to offer any suggestions for how we can workaround this bug or is there any means to appeal your decision not to fix the bug?

  • A fix is available at

    We build a workaround to solve this problem, therefore we didn’t test this fix so far.

  • I downloaded the Win7 32-bit version of the fix and tried to install it, but says "The update is not applicable to your computer". Has anybody else tried?

  • I tested the Windows 7 64-bit version on IE 11.0.37 and the issue is fixed in both the test case attached on this issue report and within our application. Appears to be working as expected.


  • We installed windows updates recently over 11.0.37 with the provided fix by Wolfgang B. and discovered that afterwards the fix was no longer effective. Internet explorer moved to 11.0.38 in this process.

    The items installed were:

    • December, 2016 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB3207752)
    • December, 2016 Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 on Windows 7 and Windows Server 2008 R2 for x64 (KB3205402)
    • Windows Malicious Software Removal Tool x64 - December 2016 (KB890830)
    • December, 2016 Security Only Quality Update for Windows 7 for x64-based Systems (KB3205394)

    I feel it would be frowned upon if we were to ask our customers to ensure they install this patch after every round of windows updates that are installed. That doesn’t seem like a good way to go forward.

    Do you know if this fix going to be rolled up into Januarys updates, or have an idea when it will be on general release?

  • I notice the status of the issue is now WON’T FIX. This is very disappointing. Is there a workaround at least which doesn’t involve complicated windows update planning?

  • The problem should be fixed.
    You just need to make sure you follow the steps:

    1. Install the December cumulative update:
       2. Install the OOB fix:


  • Thanks for the reply Adrian G. The problem is that after installing the “OOB fix” when you next update through Windows Update. The OOB fix appears to be removed. Presumably because the relevant DLL file is overwritten.

  • Hi Stuart,

    There was a problem with the first release of the OOB (in December), that was built on the November update and thus installing the December update and trying the OOB was not working properly as it was replacing the DLL.
    If you are in the above situation just remove the OOB, remove the December Cumulative Update and reinstall them again based on the above links I provided.

    The links provided above, the OOB was rebuild on the December cumulative update so it just adds the functionalities that come with the OOB and not replace.

    So if you have a machine you have never tested the fix, please try the above actions by making sure you download what I provided above and not the old KB’s.

  • Wenn got the Information from Microsoft, that the fix is planed for the February cumulative update.

  • Thanks for the answers Adrian and Wolfgang. I see it was updated on the 8th Jan in the catalog. We will try this version and report on how it behaves.

You need to sign in to your Microsoft account to add a comment.

Sign in