Windows 10 version 1709 getting a cumulative update too

Jul 25, 2018 05:56 GMT  ·  By

It’s not Patch Tuesday, but it certainly feels like it is given the batch of cumulative updates released by Microsoft earlier today.

This time, however, these cumulative updates do not bring any security improvements, but only bug fixes and general refinements to the operating system.

Systems running Windows 10 Fall Creators Update (version 1709) are provided with cumulative update KB4338817, increasing the OS build number to 16299.579.

The changelog is pretty huge, and you can read it in full in the box after the jump, but it’s worth highlighting that this cumulative update addresses issues with time zone information, while also bringing improvements for PDF file handling in Microsoft Edge.

Cumulative update KB4338817 also improves Windows Update reliability and fixes a problem causing black screens after installing patches and when trying to go back to the desktop.

Three known issues

It also repairs what Microsoft describes as sporadic authentication issues when using Web Account Manager, as well as problems that prevent systems from shutting down or entering Hibernation. “This issue occurs on the first boot after performing disk encryption on an SSD drive,” Microsoft says.

There is also an important bugfix for Windows 10 Fall Creators Update that fixes in-place upgrades reliability in the operating system.

“Addresses an issue that causes in-place upgrades to Windows 10 version 1709 to stop responding at the “Making sure you’re ready to install” screen. This occurs while performing device inventory on devices that have installed monthly updates since April 2018,” Microsoft explains.

This update comes with three different known issues, none of which is new. The first two have been plaguing cumulative updates for several months already, causing some non-English platforms to see a number of strings in English, while the third one showed up earlier this month and broke down .NET Framework.

A fix for all of them would be released in a future cumulative update, but for now, no workaround is available.

KB4338817