Microsoft’s foray into quantum computing certain sounds neat, though those of us stranded with genuine programs on genuine computers have been in something of a quandary. Once again this month, we’ve strike a garland of stumbling blocks, many of that were pushed down a Automatic Update chute.
Before we disintegrate a creepy-crawlies this month, it’s critical to remember that we have to get a .Net rags installed, unless we fastidiously refrain from clicking a “Enable Editing” symbol in Word.
After telling us that Windows 10 Creators Update, version 1703, is “the many performant and arguable chronicle of Windows 10 ever!” we competence design some fortitude with chronicle 1703 patches. This month, that didn’t happen. After releasing accumulative refurbish KB 4038788 on Patch Tuesday, we got a new out-of-band repair for bugs introduced by that same update. The new accumulative update, KB 4040724, seemed in Windows Update on Monday, Sept. 25. It brings 1703 adult to build 15063.632. So far, we haven’t listened of any problems with a new accumulative refurbish — though it’s been reduction than a day.
The conditions with Win10 Anniversary Update, version 1607, isn’t as straightforward. Apparently, there were a horde of problems that seemed after this month’s Patch Tuesday accumulative update, KB 4038782. It isn’t transparent if that refurbish introduced bugs of a own, though a situation’s bad adequate that we got a second accumulative refurbish this month, again on Monday. KB 4038801 brings Win10 chronicle 1607 to build 14393.1736. It’s a hotfix; it isn’t distributed around Automatic Update. You have to download KB 4038801 and implement it manually. we haven’t seen a minute research of a confidence holes bound by this peculiar Monday patch – though to date we haven’t seen any complaints, either. The day is still young.
For reasons as nonetheless unexplained, KB 4038801 is usually for Win10 1607; it’s categorically not expelled for Server 2016.
There’s a note on a 1607 patch site that says:
Windows Update Client Improvement
Microsoft will recover an refurbish directly to a Windows Update Client to urge Windows Update reliability. It will usually be offering to inclination that have not commissioned any new accumulative updates and are not now managed (e.g., domain joined).
As remarkable by @abbodi86 on AskWoody.com:
The note means [they] are going to recover a apart “small” refurbish for WUC, identical to this one for chronicle 1507. They could also recover a refurbish directly as a SelfUpdate for WUC like they used to do with Windows before [to] Windows 8 (for example, latest for Windows 7 is v7.6.7600.320 before they shifted to apart WUC updates starting with KB2990214).
Windows Server 2016
When we run a Get-PhysicalDisk cmdlet, some disks might arrangement an operational standing of “In Maintenance Mode.” The Get-VirtualDisk cmdlet might also arrangement a operational standing of a practical hoop as “Degraded.” There’s a primer workaround described in KB 4043361.
On Windows Server 2016, when we try to download updates by regulating Windows Update (stand-alone or WSUS), a routine hangs during 0 percent completion. Microsoft has a outline of a problem and dual primer overrides in KB 4039473.
Everyone’s favorite defeat child only took another lash. Many folks news that, after installing KB 4038792 — a Sep Monthly Rollup for Win 8.1 — they can no longer record on to their computers with a Microsoft account. we posted a sum yesterday. Still no word from Microsoft – not even an acknowledgment of a problem on a KB article.
There’s a well-publicized problem with Internet Explorer 11 unexpected growing a hunt box on a residence bar after installing KB 4038777 (the Windows 7 Monthly Rollup) or KB 4036586 (the Sep Internet Explorer Security-only patch). For a minute demeanour during what’s happening, with screenshots, see ElderN’s post on a Microsoft Answers forum. Turns out adult a flim-flammery is a outcome of rise sizes altered behind a scenes and a probable undocumented switcheroo in one of a IE settings. See @PKCano’s post.
Poster Richard has also identified a problem with starting IE 11 after this month’s Windows 7 updates — and he found a solution. Again, it’s associated to undocumented changes in a Tab View settings and in rise size. See post 8 on a AskWoody Lounge.
I’ve seen no change from a sorry state we were in a week ago: Microsoft pulled a Sep Outlook 2007 confidence patch KB 4011086 and transposed it with KB 4011110, though we have to manually uninstall a bad patch before we implement a new one. Microsoft posted incorrect information about a uninstallation method. Both that patch and a Outlook 2010 patch, KB 4011089, have a nasty robe of changing languages in menus.
The .NET Security and Quality Rollups make certain tradition images spin black. As Microsoft puts it: “After we implement a Sep 12, 2017, .NET Security and Quality Rollups that request to a .NET Framework 4.6, 4.6.1, 4.6.2, and 4.7, we knowledge digest issues in Windows Presentation Foundation (WPF) applications that use WPF forms in a Windows service.”
In addition, Microsoft has released a preview of subsequent month’s .Net Framework patches.
Assuming we don’t click “Enable Editing” in Word, there are no immediately dire Sep patches. we contend it’s correct to wait and see if any of a superb bugs get bound — and wait to see if a patches-of-patches beget new problems of their own.
Remember when patching was easy?
Please join us for an ongoing Patch Festschrift on the AskWoody Lounge.