IE11 Window 7 IFrame print error since kb4021558

Won’t fix Issue #12349663


andrew F.
Jun 15, 2017
This issue is public.
Found in
  • Internet Explorer
Found in build #
Reported by 19 people

Sign in to watch or report this issue.

Steps to reproduce

I’m not sure if this is the correct place to raise this bug but since kb4021558 our users are having issues printing. From testing it seems to be with IFrames. When the user clicks the Printer icon the resulting print shows 404 Page Not Found. This is also apparent when using javascript window.print() method. Non IFrame pages seem to be ok. Looking at the network trace It would seem that IE creates a temp .htm file in the local directory like D3CD911.htm, it then downloads css/js resources and then finally it makes this call /D3CD911.htm. This is making a call to This obviously does not exist on the website so the 404 is returned.

I have raised this question in 2 other Q&A sites as follows:

From the responses so far it would seem to be affecting lots of people.

Can you please advise soonest next steps for fixing this bug.


0 attachments

    Comments and activity

    • We are also impacted by this bug, several of our clients are complaining that they can no longer print.

      Is there a way to get around this issue, or better a fix planned ?

    • Benjamin G. 2 Workarounds so far. Either use Print Preview instead of print button or if currently using window.print() in javascript change this to document.execCommand('print’, false, null)

    • We are also seeing this issue. I saw on another site that it is recommended to uninstall KB4021558 to resolve this. This fix has not been tested as of yet.

    • Microsoft Edge Team

      Changed Assigned To to “James M.”

    • Hello,

      Thank you for providing your feedback on IE11. We are not accepting feedback on Internet Explorer through this portal any longer (unless security related). We welcome any feedback you have on Microsoft Edge through this website.

      If this is blocking enterprise deployment, please follow the CSS escalation process to engage MS support (GES, General Escalation Service) and file a servicing request.

      Support URL:

      Best Wishes,
      The MS Edge Team

    • Microsoft Edge Team

      Changed Status to “Won’t fix”

    • Can confirm that Andrew F’s suggestion works as a workaround for this issue on Windows 10 for IE11 as well.

    • We are having the same issue in our company; our clients are complaining that they can no longer print.

    • Update- This behavior is being seen in Windows 7 and Windows 10. Confirmed workaround is to uninstall KB4021558 or KB4022719 once this is removed and computer restarts printing works correctly.

    • We found this solution in Stack overflow, for window.print() case:
      if (document.queryCommandSupported(‘print’)) {
      document.execCommand('print’, false, null);
      else {

    • We found this solution in Stack overflow, for window.print() case:
      if (document.queryCommandSupported(‘print’)) {
      document.execCommand('print’, false, null);
      else {

    • Why is this report marked "Won’t Fix"?


    • Our clients have the same problem on IE 11 and Windows 7 or Windows 10. We use IE 11 engine via Web Browser Control in our desktop C++ application.

    • @James M. It was your security fix that has broke printing for many many people. Really bad show just to say won’t fix. If any other software company released a fix which broke fundamental functionality they would fix their mistake as a matter of urgency. I do hope you pass this on to someone that can do the right thing and provide a patch.

    • The same issue on on IE 8 and Windows XP with installed KB4021558 (for WES09 и POSReady 2009). After uninstall this update, problem is gone.

    • Experiencing the issue here as well. Going to open a PSS case.

    • After I uninstall KB4021558 we don’t have anymore problem.

    • Why have you flagged this as “Won’t fix” when Microsoft have just introduced this problem with the latest update?

    • An uninstall is not a fix.

    • We are not accepting feedback on Internet Explorer through this portal any longer (unless security related).

      So, you release a broken, poorly tested security “fix” breaking printing functionality used by tons of people on every single supported OS version out there, and then tell people to GTFO when they report the bug. Wow, just wow. You sure must hate your business customers. Get your act together, really. Maintaining your OSes patched at least for security has become a royal PITA and your QA sucks.

    • See the update to “Known issues in this security update” here:

      From that acknowledgement it appears that a fix is under development by the IE team.

      So we can probably take it that “Won’t fix” is a response from the Edge team … as a result of not fully understanding the severity of the issue in the corporate space, or it simply being seen as “not our problem” maybe?

    • As the issue tracker specifically for Edge, which is not the same as Internet Explorer, this is simply not the right place to file bugs against the old IE. It’s not a "microsoft won’t fix this, ever", it’s "this is not getting fixed here, because it’s a completely different project that we do not work on", in the same way that filing a bug about Works won’t get fixed by the Office 365 team. A “wont fix” label takes a bug report out of the active queue and archives it, quite reasonably in this case because the people who work on this bug queue don’t work on IE.

    • I noted above that t
      This is also an issue with EDGE

    • Hello,

      Thank you for providing this information about the issue. For troubleshooting, please uninstall the update and confirm the expected behavior has been restored. Next, please reinstall the update KB4021558 and confirm the expected behavior has been lost.

      Best Wishes,
      The MS Edge Team

    • Hey James M. I can confirm this for you. Our support department for our software has been instructing customers for 2 days on uninstalling that update. Once uninstalled the customer can print again. For testing, I installed it on a known working and printing machine to confirm it would break it and it did. I then removed the update and I could print again.

    • Hi any fix so far released?? If uninstall and reinstall the update KB4021558 it would be work?

    • Uninstalling KB4021558 is not a solution. Will not work.

    • Uninstall KB4021558 first and then reboot. Go to IE 11, click the gear, click about internet explorer and update version should no longer show KB4021558 . If the KB still shows KB4021558, you then need to uninstall the Security Monthly Quality Rollup that is KB4022719. Reboot and check IE11 again. It should no longer show KB4021558. It seems KB4022719 has KB4021558 rolled into it.

    • @Jayson K. we have tested your solution without success :( not working.

    • Hi Pedro

      Uninstall every update that was installed on June 14th. There’s more that one KB that this IE update is part of.

    • Just chiming-in that for our Win7/IE11 users, removing KB4022719 and the roll-up KB4021558 resolved the problem. I wouldn’t call this a “fix” but at least it restores our users’ ability to print from mission critical web-apps again (they print reports to take into the field where mobile devices are not an option).

      BTW - The issue manifested in 2, possibly 3 different ways:

      1. Users printed a blank page … but the footer indicated “res://ieframe.dll” instead of the page’s URL.

      2. Users getting a 404 error as mentioned in the “Known Issues” of KB4021558.

      3. Not sure if this one is related yet but user’s browser (IE11) is freezing with a message box that says, “Cannot find …[some URL] … Make sure the path of Internet address is correct.” The vendor seems to suspect it is related to one of the updates but has yet to confirm.

    • my workaround was use metadata of compatibility with IE mode 8: , because the issue is only in version 9 or superior.

    • this metadata: < meta http-equiv="X-UA-Compatible" content="IE=8"/>

    • On our 2012 r2 servers we had to remove both KB4021558 and kb4022726

    • No fix for Windows 10?

    • Was told the fix for Windows 10 will be at the end of the month.

    • That’s right – and will be pushed out in another Cumulative Update.

    • Just tried KB4032782 mentioned earlier by Rod T. and it worked for Win7 32 and 64. Resolved issues 1 & 2 that I mentioned in my earlier post.

    • We are still having issues with Win 10. Where have you heard this about the update ?

    • ++++++++++++++++++++++++++++++++

      June 27, 2017—KB4022716 (OS Build 15063.447)

      This non-security update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:

      •Addressed an issue introduced by KB4022725 where Internet Explorer and Microsoft Edge printing from a frame may result in 404 not found or blank page printed.

      And lots more …


      So it looks like “Won’t fix” - of a bug that also affected Edge along with the well-proven, versatile and useful corporate tool “old IE” - got fixed anyway.

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

    Sign in