Microsoft’s foray into quantum computing certain sounds neat, however these of us caught with actual packages on actual computer systems have been in one thing of a quandary. As soon as once more this month, we’ve hit a bunch of obstacles, lots of which had been pushed down the Computerized Replace chute.
Earlier than we dissect the creepy-crawlies this month, it’s necessary to do not forget that you must get the .Web patches put in, until you fastidiously chorus from clicking the “Allow Enhancing” button in Phrase.
Home windows 10
After telling us that Home windows 10 Creators Replace, model 1703, is “probably the most performant and dependable model of Home windows 10 ever!” you may count on some stability with model 1703 patches. This month, that didn’t occur. After releasing cumulative replace KB 4038788 on Patch Tuesday, we obtained a brand new out-of-band repair for bugs launched by that very same replace. The brand new cumulative replace, KB 4040724, appeared in Home windows Replace on Monday, Sept. 25. It brings 1703 as much as construct 15063.632. Thus far, I haven’t heard of any issues with the brand new cumulative replace — however it’s been lower than a day.
The scenario with Win10 Anniversary Replace, model 1607, isn’t as simple. Apparently, there have been a number of issues that appeared after this month’s Patch Tuesday cumulative replace, KB 4038782. It isn’t clear if that replace launched bugs of its personal, however the scenario’s dangerous sufficient that we obtained a second cumulative replace this month, once more on Monday. KB 4038801 brings Win10 model 1607 to construct 14393.1736. It’s a hotfix; it isn’t distributed by way of Computerized Replace. You must obtain KB 4038801 and set up it manually. I haven’t seen an in depth evaluation of the safety holes fastened by this odd Monday patch – however thus far I haven’t seen any complaints, both. The day remains to be younger.
For causes as but unexplained, KB 4038801 is just for Win10 1607; it’s explicitly not launched for Server 2016.
There’s a word on the 1607 patch website that claims:
Home windows Replace Consumer Enchancment
Microsoft will launch an replace on to the Home windows Replace Consumer to enhance Home windows Replace reliability. It should solely be supplied to units that haven't put in any current cumulative updates and are usually not at present managed (e.g., area joined).
As famous by @abbodi86 on AskWoody.com:
The word means [they] are going to launch a separate “small” replace for WUC, just like this one for model 1507. They may additionally launch the replace straight as a SelfUpdate for WUC like they used to do with Home windows prior [to] Home windows eight (for instance, newest for Home windows 7 is v7.6.7600.320 earlier than they shifted to separate WUC updates beginning with KB2990214).
Home windows Server 2016
Once you run the Get-PhysicalDisk cmdlet, some disks could show an operational standing of "In Upkeep Mode." The Get-VirtualDisk cmdlet may additionally show the operational standing of the digital disk as "Degraded." There’s a guide workaround described in KB 4043361.
On Home windows Server 2016, while you attempt to obtain updates by utilizing Home windows Replace (stand-alone or WSUS), the method hangs at zero % completion. Microsoft has an outline of the issue and two guide overrides in KB 4039473.
Home windows eight.1
Everybody’s favourite whipping boy simply took one other lash. Many people report that, after putting in KB 4038792 — the September Month-to-month Rollup for Win eight.1 — they'll now not go browsing to their computer systems with a Microsoft account. I posted the small print yesterday. Nonetheless no phrase from Microsoft – not even an acknowledgment of the issue on the KB article.
Home windows 7
There’s a well-publicized drawback with Web Explorer 11 immediately sprouting a search field on the tackle bar after putting in KB 4038777 (the Home windows 7 Month-to-month Rollup) or KB 4036586 (the September Web Explorer Safety-only patch). For an in depth have a look at what’s occurring, with screenshots, see ElderN’s put up on the Microsoft Solutions discussion board. Seems up the flim-flammery is a results of font sizes modified behind the scenes and a doable undocumented switcheroo in one of many IE settings. See @PKCano’s put up.
Poster Richard has additionally recognized an issue with beginning IE 11 after this month’s Home windows 7 updates — and he discovered an answer. Once more, it’s associated to undocumented modifications within the Tab View settings and in font dimension. See put up eight on the AskWoody Lounge.
I’ve seen no change from the sorry state we had been in every week in the past: Microsoft pulled the September Outlook 2007 safety patch KB 4011086 and changed it with KB 4011110, however you must manually uninstall the dangerous patch prior to installing the brand new one. Microsoft posted incorrect data concerning the uninstallation technique. Each that patch and the Outlook 2010 patch, KB 4011089, have a nasty behavior of fixing languages in menus.
The .NET Safety and High quality Rollups make sure customized pictures flip black. As Microsoft places it: “After you put in the September 12, 2017, .NET Safety and High quality Rollups that apply to the .NET Framework four.6, four.6.1, four.6.2, and four.7, you expertise rendering points in Home windows Presentation Basis (WPF) functions that use WPF sorts in a Home windows service.”
There’s an outline of the issue on the Visible Studio discussion board and a workaround in KB 4043601. The workaround suggests that you simply uninstall the Safety and High quality Rollup and set up the Safety-only patch.
As well as, Microsoft has launched a preview of subsequent month’s .Web Framework patches.
Assuming you don’t click on “Allow Enhancing” in Phrase, there aren't any instantly urgent September patches. I say it’s clever to attend and see if any of the excellent bugs get fastened — and wait to see if the patches-of-patches generate new issues of their very own.
Keep in mind when patching was simple?
Please be part of us for an ongoing Patch Festschrift on the AskWoody Lounge.