windows

Yesterday, the third Tuesday of the month, Microsoft dumped another big bucket of patches:

• KB 4093117 brings Win10 1703 up to build 15063.1058, many miscellaneous fixes, no known issues.
• KB 4093120 brings Win10 1607 to build 14393.2214, a similarly large bunch of fixes, no known issues.
• KB 4093113 is the regular Monthly Rollup Preview for Win7.
• KB 4093121 is the similar Monthly Rollup Preview for Win 8.1.
• The Update Catalog says there’s a new version of KB 4099950, the abandoned patch for fixing the NIC/static IP bug in Win7.

There are lots of oddities in this motley collection.

To read this article in full, please click here

A Windows Ink engineer has confirmed that there’s a bug in the third Win10 1709 March Cumulative Update, KB 4089848, that breaks common pen movements in Photoshop, Lightroom and CS Paint. Looks as if the same problem bedevils this month’s 1709 Cumulative Update, KB 4093112, as well. Microsoft, it seems, decided to break pen behavior in Win10 1709 without any notification or explanation.

Early this month, DavideV, on the Microsoft Answers forum, posted a rather strange observation:

To read this article in full, please click here

With all of the problems in the January, February and March patches for Windows and Office, you’d think we would catch a break in April. In one sense we did — some of the worst bugs in the earlier patches now seem to be behind us. But we’re definitely not out of the woods just yet.

To read this article in full, please click here

Most of us expected Microsoft to drop its latest and greatest version of the last version of Windows yesterday. The highly anticipated version 1803, Redstone 4 — which many of us have been testing for weeks — looked ready to go … until it wasn’t.

Rumors are flying but, as of this writing, the actual cause for the delay isn’t public.

Microsoft, of course, has never committed to a release date. Or a build number. Or even a hokey “Spring after Fall Creators Update” style name, for that matter. (I’m still plugging for “Terry Myerson Swansong version” but doubt it’ll gain traction.)

To read this article in full, please click here

March Windows patches were a mess. With the revelation of Total Meltdown, we recently discovered that all of this year’s Win7 patches left gaping security holes. It’s fair to say that the initial Patch Tuesday patches for almost every version of Windows, for every month this year, have had confirmed bugs. Every one.

If you want to help test this month’s Windows and Office patches, hey, I salute you! Most folks, though, would be well advised to turn off Automatic Update and wait for the initial wave of devastation to pass.

To read this article in full, please click here

The quality of March’s patches set new lows, even by Windows’ tarnished standards. The Win10 patches flew fast and furious, with new Microsoft-induced bugs introduced and swatted multiple times over the month. The Word 2016 security patch demands that you first install the Word 2016 non-security patch, or Word refuses to open files. That bug hasn’t been fixed. Windows 8.1/Server 2012R2 escaped relatively unscathed. Server 2008 got a fix for its buggy patch, KB 4090450, on April 3. But Windows 7… ah, that’s a dying horse of a completely different color.

To read this article in full, please click here

Last night we were treated to new versions of the badly banged-up March Win7 patches. It looks like the new ones are the same as the old ones, but the internal handling instructions (the metadata) now force installation of a “Total Meltdown” fix-up patch prior to installing the old patch.

Of course, none of this is documented anywhere.

Starting with Günter Born’s report, and checking the Microsoft Update Catalog, I can see modified versions of:

To read this article in full, please click here