Newsletter Archives

• More June security patching bugs: You can patch an IE security hole, or print inside iFrames – but not both

  Posted on July 19, 2017 at 13:21 CDT by woody • Comment in the Forums

  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

  Windows Patches/Security KB 4021558, KB 4022714, KB 4022715, KB 4022716, KB 4022719, KB 4022724, KB 4022725, KB 4022726, KB 4022727

• Widespread problems with last week’s Win10 1703 patch, KB 4022716

  Posted on July 3, 2017 at 21:29 CDT by woody • Comment in the Forums

  There’s a reason why I keep recommending that you avoid Windows 10 Creators Update. It ain’t baked yet.

  Case in point: KB 4022716, the June 27 cumulative update for Win10 version 1703, which is supposed to bring the version up to build 15063.447.

  There’s a lengthy Microsoft Answers forum thread about how KB4022716 kills web browser Google Chrome, Firefox, Internet Explorer. Another one about black screens with flickering cursor after unlocking, which is repeated on a Lenovo forum. A laundry list of additional problems.

  Comodo says:

  We strongly advise Comodo users not to update to latest MS update KB4022716, which is available for Windows 10 users till they have new fixed version of Comodo internet security products installed.

  Some people are reporting that the patch has been pulled. Others say that it’s still being offered.

  If you ignored my advice and upgraded to Win10 Creators Update, you would be well advised to avoid the latest cumulative update.

  Windows Patches/Security build 15063.447, KB 4022716, Win10 1703

• Massive batch of bug fixes for Windows, Office – KB 4022716, 4022723, with known problems

  Posted on June 27, 2017 at 23:06 CDT by woody • Comment in the Forums

  The dust is still settling, but here’s what people are seeing right now:

  • Win10 version 1703 – KB 4022716 includes a long list of bug fixes, brings build up to 15063.447. Known problem with iSCSI targets.
    UPDATE: Neowin reports that, nine hours after announcing this patch, it’s now available via Windows Update. MS also pulled the warning about connecting to iSCSI targets. (Thx, @Kirsty)
  • Win10 version 1607 – KB 4022723 also includes lots and lots of fixes, build 14393.1378, also has a problem with iSCSI. The KB article states that you have to manually download and install this patch, if you want it. Confused yet?
  • Win10 version 1511 – KB 4032693 has a much shorter list of fixes, build 10586.965, no identified problems. You also have to manually download and install this one, if you want it. (Thx, @MrBrian.)
  • Win 8.1 – KB 4022720, the preview of next month’s (July’s) non-security patches, also has a massive list of bug fixes, with a known problem with iSCSI attachment.
  • Win 7 – KB 4022168, also a preview of next month’s patches, has a much shorter list of fixes. I have no idea why Microsoft released the Previews on this, the fourth Tuesday of the month. They’re supposed to come out on the third Tuesday.

  I believe the 1703, Win 8.1 and Win7 patches are currently available through Windows Update and WSUS – but please drop a line if you aren’t seeing yours.

  Just to make life a little more complicated, Microsoft has officially announced that it has released KB 4022716 — the 1703 patch, mentioned above — to the Insiders Program Slow ring. Yes, if the documentation is correct, that means this same patch is available to Insiders Slow Ring (currently at build 10563.413, the same as the “old” build of 1703), but is not available to Insiders Fast Ring — nor is it available to Insiders Release Preview Ring. I think somebody at Microsoft didn’t press the right red button.

  Please tell me if you can translate this paragraph from the announcement:

  When we release a new Windows 10 Fall Creators Update build to Insiders in the Slow ring, they can wait to be targeted to install the new build, or instead of waiting Insiders can manually check for updates via Windows Update to get the new build. We know this is different from our usual “everyone at once” model to the WIP rings, however this testing will provide invaluable insights to ensure this new targeting framework is functioning as expected.

  I’m seeing confused/confusing reports about the Outlook patches – do they fix all of the identified issues, or only some? What and where are they? According to the Outlook known issues in the June 2017 security updates page, these fixes are available:

  • June 27, 2017, update for Outlook 2010 (KB3015545) – for Issues #1 and #2 but there’s no analogous patch for Outlook 2007 as yet.
  • June 27, 2017, update for Outlook 2013 (KB3191849) – for Issue #2 and #3 but, similarly, there’s no analogous patch for Outlook 2007 as yet, nor is there a fix for Outlook 2016.

  Microsoft also says it has fixed the Outlook Search problems, as well as the Internet Explorer printing problems… by the above-mentioned fixes to Windows.

  And of course MrBrian’s reports from the Internet Explorer bug trenches remain clouded.

  Can anybody remember back when patching Windows wasn’t so complicated? Yeah, me neither. It’s becoming increasingly difficult to put lipstick on the pig.

  Until we have some indication of the problems generated by this latest round of patches, I’m keeping us at MS-DEFCON 1:  Current Microsoft patches are causing havoc. Don’t patch.

  Windows Patches/Security KB 4022168, KB 4022716, KB 4022720, KB 4022723, KB 4032693