Today, Aug. 31, Microsoft released two new Windows 10 builds.
For those of you using Windows 10 Anniversary Update (version 1607), it's the sixth cumulative update for version 1607, as three cumulative updates were released before 1607 shipped. KB 3176938 brings Win10 version 1607 to build 14393.105 (I call it Win 10.2.6).
There's a lengthy list of changes on the official Windows 10 update history page. You can wallow around in the details, but here's what hasn't been fixed:
- PowerShell DSC is still broken. If you need to use DSC, don't install Anniversary Update.
- The camera protocol problem that breaks Skype is still there.
- Plugging a Kindle into an Anniversary Update machine still triggers a blue screen. (Paul Thurrott has the definitive description of Kindlegate on thurrott.com.)
In addition, the double-print bug introduced by MS16-08/KB 3177725 may or may not be fixed by the update. It isn't mentioned in the changelog notes, at any rate. Seagull Scientific, proprietors of a package that was broken by Microsoft's buggy security patch, has not yet confirmed that this specific patch works, but they're looking at it.
I continue to recommend that you avoid installing the Windows 10 Anniversary Update.
The other comprehensible patch is the latest version of the Windows 10 "RS2" beta, now up to version 143915 for the beta Fast Ring only. You can see the details on the Windows blog, but the only significant change I could find involves Delivery Optimization -- the torrent-like ability to share patches. Starting with this beta build, Delivery Optimization is enabled by default. Gregg Keizer has the details on Computerworld.
Now for the utterly confusing stuff.
KB 3186988, titled "Cumulative Update for Windows 10 Version 1511: August 30, 2016," is in the Microsoft Update Catalog, but it hasn't been released. I think Microsoft has posted it in the Update Catalog as a way to emulate the Preview Ring for Win10 Fall Update.
KB 3187022, the patch that fixes the aforementioned double-print bug has appeared in two incarnations. Last Wednesday, it was released for Win7, 8.1, and analogous servers. On Tuesday, Aug. 30, it was released for Vista and Server 2008. Apparently it's the same patch, but you can only get it through the Update Catalog.
Seagull Scientific also says that the double-print bug fixes "for previous versions of Windows should be available on Windows Update in mid-September."
A reminder: You can use Firefox or Chrome to get into the Update Catalog by going through the associated RSS feed.
Also, it's worth noting that while MS16-098/KB 3177725 is identified by Microsoft as a security patch, KB 3187022 is not, at least at this point. That means if Microsoft broke your system with a security patch, you may have to apply a non-security patch in order to fix it. We'll know more as mid-September rolls around.
If you're confused by all of the rings within rings and little side-deals with unannounced Release Previews, believe me, you ain't the only one.