{"id":3185,"date":"2017-06-29T01:20:00","date_gmt":"2017-06-28T23:20:00","guid":{"rendered":"http:\/\/borncity.com\/win\/?p=3185"},"modified":"2017-06-29T10:56:38","modified_gmt":"2017-06-29T08:56:38","slug":"ie11-printing-issues-in-windows-are-fixed-june-2017","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2017\/06\/29\/ie11-printing-issues-in-windows-are-fixed-june-2017\/","title":{"rendered":"IE11 printing issues in Windows are fixed (June 2017)"},"content":{"rendered":"

[German<\/a>]Just for your information. Microsoft has finally fixed the printing issues in Internet Explorer 11 caused by June 13, 2017 security updates within all Windows versions. Note:<\/strong> Update KB4032782 may cause IE 11 crashes on several web pages.<\/p>\n

<\/p>\n

What's the problem?<\/h2>\n

\"\"User, who has installed security updates KB4021558, KB4022719, KB4022725 etc. from June 13, 2017  probably facing printing issues within Internet Explorer 11. The content of frames and iframes are printed as blank pages. The issue occurs an all Windows version (Windows 7 SP 1 up to Windows 10). I've addressed this issue within my blog posts June 2017 Patches causing Internet Explorer 11 printing issues<\/a> and June 2017 security updates IE 11 printing issues confirmed<\/a>. <\/p>\n

Microsoft's fixes<\/h2>\n

Microsoft has released Update KB4032782 for Windows 7 SP1 and Windows 8.1 to fix the Internet Explorer 11 printing issue. I've mentioned within my blog post Fix KB4032782 for Internet Explorer 11 printing issues (June 2017)<\/a>.<\/p>\n

Now Microsoft has also fixed the IE 11 printing issue for all Windows 10 builds. The cumulative updates released on June 27, 2017 are addressing also the Internet Explorer 11 printing issue (see Windows 10 Updates KB4023543, KB4022723, KB4032693, KB4032695 (June 2017)<\/a>).<\/p>\n

Addendum: KB4032782 may crash IE 11<\/h2>\n

Note that KB4032782 is causing another issue. According to some comments<\/a> within my German blog, IE 11 crashes on several complex pages (see also this discussion<\/a> in MS Answers). Microsoft has confirmed that in an addendum (June 29, 2017) within this KB article<\/a>: <\/p>\n

\n

After you install this update, Internet Explorer 11 may crash when you visit some websites. The problem may occur if the website is complex and uses certain web API's. <\/p>\n

Microsoft is researching this problem and will post more information in this article when the information becomes available.<\/p>\n<\/blockquote>\n

A workaround (proposed within the German comments<\/a>) is, set these website to the IE11 compapatibility list, that may avoid crashes. <\/p>\n

Microsoft's Security Update Release<\/h2>\n

Microsoft has also send out a Security Update Release via e-mail. Here are the details.  <\/p>\n

********************************************************************
Title: Microsoft Security Update Releases
Issued: June 27, 2017
********************************************************************<\/p>\n

Summary
=======<\/p>\n

The following CVEs have undergone a major revision increment:<\/p>\n

* CVE-2017-0173  * CVE-2017-0299  * CVE-2017-8482  * CVE-2017-8522 
* CVE-2017-0193  * CVE-2017-0300  * CVE-2017-8483  * CVE-2017-8523 
* CVE-2017-0215  * CVE-2017-8460  * CVE-2017-8484  * CVE-2017-8524 
* CVE-2017-0216  * CVE-2017-8462  * CVE-2017-8485  * CVE-2017-8527 
* CVE-2017-0218  * CVE-2017-8464  * CVE-2017-8488  * CVE-2017-8528 
* CVE-2017-0219  * CVE-2017-8465  * CVE-2017-8489  * CVE-2017-8529 
* CVE-2017-0282  * CVE-2017-8466  * CVE-2017-8490  * CVE-2017-8530 
* CVE-2017-0283  * CVE-2017-8468  * CVE-2017-8491  * CVE-2017-8531 
* CVE-2017-0284  * CVE-2017-8469  * CVE-2017-8492  * CVE-2017-8532 
* CVE-2017-0285  * CVE-2017-8470  * CVE-2017-8493  * CVE-2017-8533 
* CVE-2017-0286  * CVE-2017-8471  * CVE-2017-8494  * CVE-2017-8534 
* CVE-2017-0287  * CVE-2017-8472  * CVE-2017-8496  * CVE-2017-8543 
* CVE-2017-0288  * CVE-2017-8473  * CVE-2017-8497  * CVE-2017-8544 
* CVE-2017-0289  * CVE-2017-8474  * CVE-2017-8498  * CVE-2017-8547 
* CVE-2017-0291  * CVE-2017-8475  * CVE-2017-8499  * CVE-2017-8548 
* CVE-2017-0292  * CVE-2017-8476  * CVE-2017-8504  * CVE-2017-8549 
* CVE-2017-0294  * CVE-2017-8477  * CVE-2017-8515  * CVE-2017-8553 
* CVE-2017-0295  * CVE-2017-8478  * CVE-2017-8517  * CVE-2017-8554 
* CVE-2017-0296  * CVE-2017-8479  * CVE-2017-8519  * CVE-2017-8555 
* CVE-2017-0297  * CVE-2017-8480  * CVE-2017-8520  * CVE-2017-8575 
* CVE-2017-0298  * CVE-2017-8481  * CVE-2017-8521  * CVE-2017-8576 
                                                   * CVE-2017-8579 
 
Revision Information:
=====================<\/p>\n

– – https:\/\/portal.msrc.microsoft.com\/en-us\/security-guidance<\/a>
– Version: 4.0
– Reason for Revision: Microsoft is announcing the release of the
   following updates to address a known issue customers may experience
   when printing from Internet Explorer or Microsoft Edge: 4032782 for
   Internet Explorer 10 on Windows Server 2012, Internet Explorer 9 on
   Windows Server 2012; 4032695 for Internet Explorer 11 and Microsoft
   Edge on Windows 10; 4032693 for Internet Explorer 11 and Microsoft
   Edge on Windows 10 1511; 4022723 for Internet Explorer 11 and Microsoft
   Edge on Windows 10 1607; 4022716 for Internet Explorer 11 and Microsoft
   Edge on Windows 10 1703; 4022720 which is the monthly rollup preview for
   Windows 8.1 and Windows Server 2012 R2; 4022721 which is the monthly
   rollup preview for Windows Server 2012; 4022168 which is the monthly  
   rollup preview for Windows 7 Service Pack 1 and Windows Server 2008 R2
   Service Pack 1. \u00c2 This update removes the protection from CVE-2017-8529.
   All updates are available only on the Microsoft Update Catalog, with
   the exceptions of 4022720, 4022721, 4022168, and 4022716, which are
   also available through Windows Update.
– Originally posted: June 27, 2017 
– Aggregate CVE Severity Rating: Critical<\/p>\n","protected":false},"excerpt":{"rendered":"

[German]Just for your information. Microsoft has finally fixed the printing issues in Internet Explorer 11 caused by June 13, 2017 security updates within all Windows versions. Note: Update KB4032782 may cause IE 11 crashes on several web pages.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,22,2],"tags":[816,903,390,194],"class_list":["post-3185","post","type-post","status-publish","format-standard","hentry","category-issue","category-update","category-windows","tag-internet-explorer-11","tag-kb4032782","tag-printing-issue","tag-windows"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/3185","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=3185"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/3185\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=3185"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=3185"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=3185"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}