The big remaining bugaboo — the Dec. 19 emergency release of Internet Explorer patches for all supported versions of Windows — remains shrouded in secrecy. That said, it looks like early reports of devastating bugs in the IE update are overstated; at this point, I’m not aware of any replicable problems.

That’s very good news, actually, given Microsoft’s exceedingly poor recent history with emergency patches.

Where we stand with Windows

That Internet Explorer patch — KB 4483235 (1809), KB 4483234 (1803), KB 4483232 (1709), KB 4483187 (Win7 and 8.1), or KB 4483187 (19H1 beta) — has had a series of workarounds posted, reworked, then reposted, over the past week. If you took Microsoft’s advice a few days ago and manually implemented the workaround (basically blocking access to jscript), you should check back and make sure that your old method is the same as the new method.

The relatively small crop of December Patch Tuesday patches turned out just fine. There were no non-security patch “previews” this month, so we dodged the usual monthly second chance at screwing up systems.

The rest of the December patches seem good to go, with two exceptions:

  • The Outlook Manage Rules & Alerts “operation failed…” error is still out there. Microsoft says it has fixed the bug, introduced in November, for Outlook 2013. The other six versions of Outlook with acknowledged errors (two “perpetual” versions and four rented Office 365 versions) still bear the bug.
  • Windows Server 2016 (nee Windows 10 version 1607) has a list of acknowledged bugs that should give you Server savants pause. In many cases the bugs — an exception thrown for SqlConnection, SCVMM errors, “Outlook cannot perform the search,” NERR_PasswordTooShort, Lenovo startup failure — have been around for months, but the list isn’t getting any shorter.  

The ongoing question of 1809 and seekers

I’m seeing more and more reports that Microsoft is pushing Win10 version 1809 on Win10 machines that aren’t “seekers” — the machines get upgraded even if the user doesn’t click “Check for updates.”

Source link


Please enter your comment!
Please enter your name here