Yesterday afternoon, Microsoft released KB 3176934 for those PCs running Windows 10 Anniversary Update. It's the fifth cumulative update for version 1607 (three were released before the product rolled out on Aug. 2) and brings the build number up to 14393.82.
[...]
There was some hope that the cumulative update would fix one of the two widespread problems with the Windows 10 Anniversary Update that I talked about last week, but no such luck. Based on reports as of very early Wednesday morning, it looks like the freeze problem is still there.
[...]
The second widely reported problem -- that Anniversary Update broke Skype for those who use many popular webcams, including the Logitech C920 -- doesn't seem to have been addressed by the patch either. The MSDN thread on the topic contains no news, only repeated remonstrations about Microsoft's ability to test Windows updates with the Skype team.
There's also a new problem, specific to patch KB 3176934. As theWindows PowerShell Blog reported last night:
Due to a missing .MOF file in the build package, the update breaks DSC. All DSC operations will result in an "Invalid Property" error. If you are using DSC from or on any Windows client, take the following steps:
Uninstall the update if already installed…
If using WSUS, do not approve the update. Otherwise, Use Group Policy to set the ‘Configure Automatic Updates' to ‘2 -- Notify for download and notify for install'… A fix for this issue will be included in the next Windows update which is due out 8/30/2016.[...]
We now have two examples of significant internal patching screwups with build 1607. First, Microsoft's Skype people didn't raise the red flag when they were testing 14393.0 with C920 cameras. Now, Microsoft's PowerShell people didn't raise the red flag when they were testing 14393.82 with DSC. The problem with yesterday's update, it seems, is a simple missing file.
The Skype team had weeks -- months -- to halt the rollout of 1607 or at least warn users in advance that 1607 would break Skype with the C920. The PowerShell team had at least a week to test 14393.82 with DSC. In both cases, Microsoft released patches that broke its own products.
Yes, Microsoft's streak of terrible update releases continues, with the Redmond team releasing a "fix" which break a new part of their "best ever" version of Windows, while failing to fix issues which have incensed users (or, at least, tech writers) for weeks. And yet, Microsoft has the sheer unmitigated gall to tell us that switching Win7 and Win8 to this same broken update scheme is some kind of favour to users, rather than being a steep downgrade in the level of service that users were promised when they bought those OSes.
Seriously, Microsoft... fuck you.