Patch aimed at systems running the Anniversary Update

Jul 11, 2017 17:15 GMT  ·  By

Microsoft has released new cumulative updates for Windows 10 systems as part of its Patch Tuesday cycle, and PCs running the Anniversary Update are getting their own version.

Windows 10 cumulative update KB4025339 pushes version number to 14393.1480 and it includes fixes for issues that were introduced by a previous cumulative update, namely KB4022723, which caused Internet Explorer 11 to close unexpectedly when certain websites were loaded.

Additionally, the cumulative update addresses a bug causing some PCs to randomly crash after users connect USB devices, as well as a BSOD experienced when the Unified Writer Filter is enabled.

Fixes for bugs caused by previous cumulative updates

The changelog is huge and you can check it out in the box after the jump, but one of the highlights refers to a bug that was experienced by users after installing other cumulative updates, including issues with Internet Explorer 11.

For example, this update fixes a problem in the browser that makes it "stop responding when a user clicks an empty column header and then immediately holds down the SHIFT key and double-clicks," as well as an issue "where a text node returned from the DOMParser may be incorrect when MutationObserver for childList and subtree is active."

While the update installed fine on our systems, it’s important to know that the cumulative update comes with two known issues and users should check them out before anything else.

For example, Microsoft says it’s aware that after installing this update, users might experience problems with iSCSI, but the company says it's aware of the problem and working on a fix. Most likely, this fix will arrive with the next cumulative update, probably later this month.

"If an iSCSI target becomes unavailable, attempts to reconnect will cause a leak. Initiating a new connection to an available target will work as expected," Microsoft explains.

There are no workarounds for this bug right now, but Microsoft says that it’s already investigating and will post solutions and more information when it becomes available.

KB4025339