Newsletter Archives
-
More June security patching bugs: You can patch an IE security hole, or print inside iFrames – but not both
The latest IE patching conundrum deals with a bug in the June patches that broke the ability to print in iFrames. Automatic Update flops between one choice and the other.
Computerworld Woody on Windows
-
Microsoft admits IE printing problems after installing the June security patches KB 4021558, KB 4022719, KB 4021558
Remember the report about this month’s security patches and Monthly Rollups triggering problems in Internet Explorer? The behavior has been confirmed.
EP just sent me this message:
Microsoft has finally acknowledged/confirmed the printing problems with the IE11 KB4021558 security update for Windows 7 & 8.1 as well as the printing problems with the KB4022719 security monthly update for Win7 SP1 & the KB4022726 security monthly update for Win8.1:
https://support.microsoft.com/
en-us/help/4022719/windows-7- update-kb4022719 https://support.microsoft.com/
en-us/help/4022726/windows-8- update-kb4022726 These MS KB articles were revised today June 20.
There is no workaround for the problem other than to uninstall any of those updates.
All three of the articles say:
When you print a specific iframe or frame in a web page, the print output may be blank, or text is printed that resembles the following:
404 – Not Found(A frame is a part of a web page or browser window that displays content independent of its container. A frame can load content independently.)
This problem has also been observed in both Internet Explorer 11, and in applications that host the IE Web Browser Control.
There is currently no workaround for this issue. However, if you print the entire web page, it will print correctly.
Microsoft is researching this problem and will post more information in this article when the information becomes available.
Which is sure to make you feel warm and fuzzy. If you’re having problems printing in IE, you need to back out:
- KB 4021558 the “Cumulative security update for Internet Explorer: June 13, 2017”
- KB 4022719– the Win7 “June 13, 2017—KB4022719 (Monthly Rollup)”
- KB 4022726 – the Win 8.1 “June 13, 2017—KB4022726 (Monthly Rollup)”
-
Win7 Monthly Rollup KB 4022719 triggers printing problems in Internet Explorer
EverWilli, posting on the Microsoft Answers forum, describes a problem with the latest Win7 Monthly Rollup, KB 4022719:
After installing KB4022719 our users cannot print certain items from Internet Explorer 11. If a users opens a page in a *frame and attempts to print they only get a blank page.
We have tired all the basic fixes, resetting IE, cleaning temp files, printer files, checking for a low folder but the only solution at this time is to uninstall KB4022719. Thus far we have only uninstalled on 2 pc’s with the issue and that fixed the printing on both machines.
There are now reported sightings of the bug with the Win7 Monthly Rollup KB 4022719, as well as the standalone IE security patch KB 4021558.
Only solution so far is to roll back the security patch.
UPDATE: The problem now appears on the Edge Developer’s forum, marked by Microsoft as “Won’t Fix.” More than a few people are aghast. It’s not clear if that’s Microsoft response to a bug of its own creation – or if it’s an indicator that the Edge folks really don’t care much about IE 11.
-
Finally, a fix for Microsoft’s draconian block on Win7 updates for recent processors
Remember Microsoft’s not-so-subtle hint that it won’t support Win7 on newer processors? Remember how the April security and Monthly Rollup patches knocked out Windows Update on systems that were running older processors?
Looks like MS is atoning for at least one of its sins.
Tucked away at the bottom of the Win7 update info for KB 4022719 is a note that goes like this:
Installation steps for systems using AMD Carrizo DDR4 processor:
- Download KB4022719 from Microsoft update catalog.
- Extract the CAB file from the downloaded .msu file from step 1. Note the path where you stored the CAB file for use in step 3.
- Run the DISM /Online /Add-Package command to install the update: DISM.exe /Online /Add-Package /PackagePath: CAB file path from step 2.
So if you don’t mind downloading the patch from the Update Catalog, and installing it with a DISM command, you can restore Windows Update functionality to computers with older Carrizo DDR4 chips.
I have no idea if this fix works on the other machines that Microsoft inadvertently clobbered, but at least it’s a start.