July 11, 2017—KB4025339 (OS Build 14393.1480)

2017-10-16T18:18:13
ID KB4025339
Type mskb
Reporter Microsoft
Modified 2017-10-17T17:00:07

Description

<html><body><p>July 11, 2017—KB4025339 (OS Build 14393.1480)</p><h2>Improvements and fixes</h2><div><p>This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:</p><ul><li>Addressed issue introduced by <a data-content-id="4022723" data-content-type="article" href="" managed-link="">KB4022723</a> where Internet Explorer 11 may close unexpectedly when you visit some websites.</li><li>Addressed issue with race condition that causes Lync Edge servers to randomly crash (Stop Error D1). Any active, open session within a federated domain loses connectivity for conference calls, instant messaging, etc.</li><li>Addressed issue with memory leaks in the nonpaged pool with the "NDnd" tag, which causes the OS to crash.</li><li>Addressed issue with race condition that occurs when two threads try to reconstruct the hash table simultaneously. </li><li>Addressed issue where Internet Explorer 11 stops responding when a user clicks an empty column header and then immediately holds down the SHIFT key and double-clicks.</li><li>Addressed issue where the NewWindow3 event handler is never called in a managed WebBrowser class of .NET 4.6.</li><li>Addressed issue in Internet Explorer 11 where a text node returned from the DOMParser may be incorrect when MutationObserver for childList and subtree is active.</li><li>Addressed issue in Internet Explorer 11 where a crash can occur in limited scenarios when using the Find feature (Ctrl+F).</li><li>Security updates to the Windows shell, Microsoft Graphics Component, <span>Windows Search, </span>Windows kernel, Windows kernel-mode drivers, the .NET Framework, Windows Server, Windows Virtualization, Windows Storage and File Systems, Datacenter Networking, Internet Explorer 11, Microsoft PowerShell, Microsoft Edge, and the Microsoft Scripting Engine.</li></ul><p>If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.</p></div><h2>Known issues in this update</h2><div><table class="table"><tbody><tr><td class="x-hidden-focus">Symptom</td><td>Workaround</td></tr><tr><td class="x-hidden-focus">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.</td><td>Microsoft is working on a resolution and will provide an update in an upcoming release.</td></tr></tbody></table></div><div class="faq-section" faq-section=""><div class="faq-panel"><div class="faq-panel-heading" faq-panel-heading=""><span class="link-expand-image"><span class="faq-chevron win-icon win-icon-ChevronUpSmall"></span></span><span class="bold btn-link link-expand-text">More Information about the iSCSI issue</span></div><div class="faq-panel-body" faq-panel-body=""><p class="ng-scope" role="document">Windows Server 2012 R2 and Server 2016 computers that experience disconnections to iSCSI attached targets may show many different symptoms. These include, but are not limited to:</p><ul class="ng-scope"><li>The operating system stops responding</li><li>You receive Stop errors (Bugcheck errors) 0x80, 0x111, 0x1C8, 0xE2, 0x161, 0x00, 0xF4, 0xEF, 0xEA, 0x101, 0x133, or 0xDEADDEAD.</li><li>User log on failures occur together with a "No Logon Servers Available" error.</li><li>Application and service failures occur because of ephemeral port exhaustion.</li><li>An unusually high number of ephemeral ports are being used by the System process.</li><li>An unusually high number of threads are being used by the System process.</li></ul><p class="ng-scope" role="document"><strong class="sbody-strong">Cause</strong><br/><br/>This issue is caused by a locking issue on Windows Server 2012 R2 and Windows Server 2016 RS1 computers, causing connectivity issues to the iSCSI targets. The issue can occur after installing any of the following updates:</p><p class="ng-scope" role="document"><strong class="sbody-strong">Windows Server 2012 R2</strong></p><table class="table"><tbody><tr><td width="124"><p>Release date</p></td><td width="126"><p>KB</p></td><td width="357"><p>Article title</p></td></tr><tr><td width="124"><p>May 16, 2017</p></td><td width="126"><p>KB<a href="https://support.microsoft.com/help/4015553"><u>4015553</u></a></p></td><td width="357"><p>April 18, 2017—KB4015553 (Preview of Monthly Rollup)</p></td></tr><tr><td width="124"><p>May 9, 2017</p></td><td width="126"><p>KB<a href="https://support.microsoft.com/help/4019215"><u>4019215</u></a></p></td><td width="357"><p>May 9, 2017—KB4019215 (Monthly Rollup)</p></td></tr><tr><td width="124"><p>May 9, 2017</p></td><td width="126"><p>KB<a href="https://support.microsoft.com/help/4019213"><u>4019213</u></a></p></td><td width="357"><p>May 9, 2017—KB4019213 (Security-only update)</p></td></tr><tr><td width="124"><p>April 18, 2017</p></td><td width="126"><p>KB<a href="https://support.microsoft.com/help/4015553"><u>4015553</u></a></p></td><td width="357"><p>April 18, 2017—KB4015553 (Preview of Monthly Rollup)</p></td></tr><tr><td width="124"><p>April 11, 2017</p></td><td width="126"><p>KB<a href="https://support.microsoft.com/help/4015550"><u>4015550</u></a></p></td><td width="357"><p>April 11, 2017—KB4015550 (Monthly Rollup)</p></td></tr><tr><td width="124"><p>April 11, 2017</p></td><td width="126"><p>KB<a href="https://support.microsoft.com/help/4015547"><u>4015547 </u></a></p></td><td width="357"><p>April 11, 2017—KB4015547 (Security-only update)</p></td></tr><tr><td width="124"><p>March 21, 2017</p></td><td width="126"><p>KB<a href="https://support.microsoft.com/help/4012219"><u>4012219</u></a></p></td><td width="357"><p>March 2017 Preview of Monthly Quality Rollup for Windows 8.1 and Windows Server 2012 R2</p></td></tr></tbody></table><p class="ng-scope" role="document"><strong class="sbody-strong">Windows Server 2016 RTM (RS1) </strong></p><table class="table"><tbody><tr><td width="124"><p>Release date</p></td><td width="126"><p>KB</p></td><td width="357"><p>Article title</p></td></tr><tr><td width="124"><p>May 16, 2017</p></td><td width="126"><p>KB<a href="https://support.microsoft.com/help/4023680"><u>4023680</u></a></p></td><td width="357"><p>May 26, 2017—KB4023680 (OS Build 14393.1230)</p></td></tr><tr><td width="124"><p>May 9, 2017</p></td><td width="126"><p>KB<a href="https://support.microsoft.com/help/4019472"><u>4019472</u></a></p></td><td width="357"><p>May 9, 2017—KB4019472 (OS Build 14393.1198)</p></td></tr><tr><td width="124"><p>April 11, 2017</p></td><td width="126"><p>KB<a href="https://support.microsoft.com/help/4015217"><u>4015217</u></a></p></td><td width="357"><p>April 11, 2017—KB4015217 (OS Build 14393.1066 and 14393.1083)</p></td></tr></tbody></table><p class="ng-scope" role="document"><br/><strong class="sbody-strong">Verification</strong></p><ul class="ng-scope"><li>Verify the version of the following MSISCSI driver on the system:<br/><br/>c:\windows\system32\drivers\msiscsi.sys<br/><br/>The version that will expose this behavior is 6.3.9600.18624 for Windows Server 2012 R2 and version 10.0.14393.1066 for Windows Server 2016.</li><li>The following events are logged in the System log:<table class="table"><tbody><tr><td width="99"><p>Event source</p></td><td width="79"><p>ID</p></td><td width="371"><p>Text</p></td></tr><tr><td width="99"><p>iScsiPrt</p></td><td width="79"><p>34</p></td><td width="371"><p>A connection to the target was lost, but the Initiator successfully reconnected to the target. Dump data contains the target name.</p></td></tr><tr><td width="99"><p>iScsiPrt</p></td><td width="79"><p>39</p></td><td width="371"><p>The Initiator sent a task management command to reset the target. The target name is given in the dump data.</p></td></tr><tr><td width="99"><p>iScsiPrt</p></td><td width="79"><p>9</p></td><td width="371"><p>Target did not respond in time for a SCSI request. The CDB is given in the dump data.</p></td></tr></tbody></table></li><li>Review the number of threads that are running under the System process, and compare this to a known working baseline.</li><li>Review the number of handles that are currently opened by the System process, and compare this to a known working baseline.</li><li>Review the number of ephemeral ports that are being used by the System process.</li><li>From an administrative Powershell, run the following command:<br/><br/><strong>Get-NetTCPConnection | Group-Object -Property State, OwningProcess | Sort Count</strong><br/><br/>Or, from an administrative CMD prompt, run the following NETSTAT command together with the "Q" switch. This shows "bound" ports that are no longer connected:<br/><br/><strong>NETSTAT –ANOQ </strong><br/><br/>Focus on ports that are owned by the SYSTEM process.<br/><br/>For the three previous points, anything more than 12,000 should be considered suspect. If iSCSI targets are present in the computer, there is high probability that the issue will occur.</li></ul><p class="ng-scope" role="document"><strong class="sbody-strong">Resolution</strong><br/><br/>If the event logs indicate that many reconnections are occurring, work with your iSCSI and network fabric vendor to help diagnose and correct the reason for the failure to maintain connections to iSCSI targets. Make sure that iSCSI targets can be accessed over the current network fabric. Install updated fixes when they become available. This article will be updated with the specific KB article number of the fix to install when it becomes available.<br/><br/><strong>Note</strong> We do not recommend that you uninstall any of the March, April, May, or June security rollups. Doing so will expose the computers to known security exploits and other bugs that are mitigated by monthly updates. We recommend that you first work with iSCSI target and network vendors to resolve the connectivity issues that are triggering target reconnects.</p></div></div></div><p> </p><h2>How to get this update</h2><div><p>This update will be downloaded and installed automatically from Windows Update. To get the stand-alone package for this update, go to the <a href="http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB4025339">Microsoft Update Catalog</a> website.</p><p> </p><p><strong>File information</strong></p><p>For a list of the files that are provided in this update, download the <a data-content-id="" data-content-type="" href="http://download.microsoft.com/download/B/4/B/B4B118EB-0C61-45C2-8714-D113BF1E6DF2/4025339.csv" target="">file information for cumulative update 4025339</a>.</p></div></body></html>