This month’s Home windows and .Web patches maintain all kinds of nasty surprises — some acknowledged, some not, some straightforward to skirt, some ready to swallow the unwary entire. Right here’s a fast overview of what’s happening with this month’s missives.
Most essential: If you happen to can’t preserve your self (or your purchasers) from clicking “Allow Enhancing” in Phrase, you have to set up a broad vary of .NET patches (in case you’re working Home windows 7 or eight.1) or cumulative updates (in case you’re working Home windows 10), like, NOW.
Home windows 10 Creators Replace model 1703
Cumulative Replace KB 4038788, which brings the construct quantity as much as 15063.608, has two acknowledged (however not mounted) bugs:
- Putting in KB4034674 could change Czech and Arabic languages to English for Microsoft Edge and different purposes.
- After putting in this replace, some customers could observe efficiency or unresponsiveness points on the primary launch of the Microsoft Edge browser. Microsoft advises: Closing and restarting Microsoft Edge will alleviate this challenge. This challenge could seem periodically. Microsoft is engaged on a decision and can present an replace in an upcoming launch.
I’m listening to studies that 4038788 brings out all kinds of issues with Edge — it’s not simply on first launch, and re-starting Edge doesn’t resolve the issues.
There’s a further bug in 4038788, which has been mounted: On some OEM techniques (learn: HP), Home windows logon has registry keys that battle with the app readiness service. After 5-10 minutes of black display, customers regain use of their machine. This challenge is triggered each time that Home windows is restarted. Microsoft mounted the issue with KB 4043292, which have to be downloaded and put in manually.
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 can also show the operational standing of the digital disk as "Degraded." There’s a guide workaround described in KB 4043361.
On Home windows Server 2016, whenever you attempt to obtain updates by utilizing Home windows Replace (stand-alone or WSUS), the method hangs at zero p.c completion. Microsoft has an outline of the issue and two guide overrides in KB 4039473.
There was a rollup for all variations that covers a distant code execution vulnerability often called CVE-2017-8759 along with a handful of non-security bug fixes. For unknown causes, Home windows 10 Creators Replace received the safety patch however didn’t get the bug fixes.
The .NET four.5.2 rollup installer in some variations consists of some weird non-English prompts, just like the one within the screenshot beneath. Microsoft assures that it’s solely a glitch within the installer and never dangerous.
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) purposes 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.
Home windows 7 and eight.1
There’s a well-publicized downside with Web Explorer 11 abruptly 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. Finally ends 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 adjustments within the Tab View settings and in font measurement. See put up eight on the AskWoody Lounge.
Then again, it seems to be like the entire formally acknowledged bugs within the August Home windows 7 Month-to-month Rollup have been mounted.
Because of @MrBrian, @PKCano and dozens of extra testers – and complainers – on the AskWoody Lounge.