14 DAY TRIAL // UPDATE: This cumulative update is not shipped via Windows Update, but only through Microsoft's Update Catalog website. You can find the download links in the KB page below.
Microsoft has just released Windows 10 cumulative update KB3216755 to users running the Anniversary Update, only two days after the company
published it for the Release Preview ring in the Insider program.
Fortunately, there’s also a KB page this time, so we do know that this cumulative update pushes Windows 10 version to 14393.726, with no new features added, as the focus was exclusively on fixing bugs and improving performance.
What’s new in Windows 10 cumulative update KB3216755
First and foremost, Microsoft uses this cumulative update to fix a bug that Windows 10 adopters first reported after installing patch KB3213986 and which caused some delays while running 3D rendering apps with multiple monitors. For what it’s worth, this older cumulative update was released earlier this month and updated Windows 10 AU to version 14393.693.
Additionally, this update fixes a bug preventing the conversion of a 24-bit image to 32 bits, while also repairing the loss of Windows Firewall rules after upgrading from RTM.
Internet Explorer and Microsoft Edge browsers are getting their own shares of improvements, first with a bugfix repairing an issue leading file downloads to fail, and then with other smaller tweaks addressing general performance errors.
There are several important security updates included too, as is the case of a patch for the bug that allowed the loading of websites that bypass the proxy server in the local intranet zone when the Intranet Sites: Include all sites that bypass the proxy server (Disabled) is set.
This cumulative update also comes with a known issue, as Microsoft says that there’s a good chance the Cluster Service might not start automatically on the first reboot after applying the update, and the company adds that you can deal with this by rebooting the node or starting the service with the Start-ClusterNode PowerShell cmdlet.
Keep in mind that this cumulative update requires a restart and you need to save your work before beginning deployment. There are no reports of failed installs just yet.