May 16, 2017—KB4019217 (Preview of Monthly Rollup)
Applies To
Windows 8.1 Windows Server 2012 R2Release Date:
5/16/2017
Version:
Preview of Monthly Rollup
Improvements and fixes
This non-security update includes improvements and fixes that were a part of Monthly Rollup KB4019215 (released May 9, 2017) and also includes these new quality improvements as a preview of the next Monthly Rollup update:
-
Addressed issue related to establishing a secure connection to a server using the TLS protocol. The application may hang when the server certificate specifies a secure URL (HTTPS) for the Certificate Revocation List (CRL) or for the Authority Information Access (AIA) values within the certificate.
-
Addressed issue where changing your password while not directly connected to the enterprise network, such as with a VPN, will cause your private keys to become inaccessible. Symptoms vary including the inability to encrypt/decrypt or sign documents.
-
Addressed issue where performing a factory reset fails because a new authenticated variable that was added to the firmware cannot be deleted during factory reset. When the factory reset encounters this variable, it gets an error and does not complete the reset.
-
Addressed issue where users may experience slow logons when logging on to Windows Server 2012 R2 servers that have a high amount of open connections. The issue is caused by the collection of bandwidth statistics on the open connections for the processing of group policy.
-
Addressed issue where the Server Message Block 3.0’s Continuous Availability feature degrades software performance when the FindFirstFileEx() function receives a path that ends with ".." or ".".
-
Addressed issue where the Common Log File System references an invalid parameter when users create new folders and new tasks using Task Scheduler, which generates Stop Error 0x24.
-
Addressed issue where removable devices do not work as expected after applying KB3179574 and when auditing of removable devices is enabled.
-
Addressed issue where a Virtual Machine sporadically loses its network connection completely.
-
Addressed issue where Windows Event Forwarding between two 2012 R2 servers makes reports incompatible with third-party Security Information and Event Management software.
-
Addressed an issue where LSASS consumes large amounts of memory on 2012 R2 Domain Controllers during a security descriptor propagation operation. This issue occurs when a security descriptor change is made on a root object with lots of descendants. Additionally, Applies To is set to "This object and all descendant objects."
-
Addressed issue where Work Folders clients using token broker do not work (“Access denied” error) when using an Active Directory Federation Services Server 2012 R2.
Known issues in this update
|
Symptom |
Workaround |
|---|---|
|
If the PC uses an AMD Carrizo DDR4 processor, installing this update will block downloading and installing future Windows updates. |
This issue is resolved by KB4022726. |
|
If a Server 2012 R2 system uses an Intel Xeon (E3 v6) family of processors, installing this update will block downloading and installing future Windows updates. |
This issue is resolved by KB4022726. |
|
This update introduced an issue in which, 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 is working on a resolution and will provide an update in an upcoming release. For more information about this issue, see the following section. |
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:
-
The operating system stops responding
-
You receive Stop errors (Bugcheck errors) 0x80, 0x111, 0x1C8, 0xE2, 0x161, 0x00, 0xF4, 0xEF, 0xEA, 0x101, 0x133, or 0xDEADDEAD.
-
User log on failures occur together with a "No Logon Servers Available" error.
-
Application and service failures occur because of ephemeral port exhaustion.
-
An unusually high number of ephemeral ports are being used by the System process.
-
An unusually high number of threads are being used by the System process.
Cause 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:
Windows Server 2012 R2
|
Release date |
KB |
Article title |
|
May 16, 2017 |
KB 4015553 |
April 18, 2017—KB4015553 (Preview of Monthly Rollup) |
|
May 9, 2017 |
KB 4019215 |
May 9, 2017—KB4019215 (Monthly Rollup) |
|
May 9, 2017 |
KB 4019213 |
May 9, 2017—KB4019213 (Security-only update) |
|
April 18, 2017 |
KB 4015553 |
April 18, 2017—KB4015553 (Preview of Monthly Rollup) |
|
April 11, 2017 |
KB 4015550 |
April 11, 2017—KB4015550 (Monthly Rollup) |
|
April 11, 2017 |
KB 4015547 |
April 11, 2017—KB4015547 (Security-only update) |
|
March 21, 2017 |
KB 4012219 |
March 2017 Preview of Monthly Quality Rollup for Windows 8.1 and Windows Server 2012 R2 |
Windows Server 2016 RTM (RS1)
|
Release date |
KB |
Article title |
|
May 16, 2017 |
KB 4023680 |
May 26, 2017—KB4023680 (OS Build 14393.1230) |
|
May 9, 2017 |
KB 4019472 |
May 9, 2017—KB4019472 (OS Build 14393.1198) |
|
April 11, 2017 |
KB 4015217 |
April 11, 2017—KB4015217 (OS Build 14393.1066 and 14393.1083) |
Verification
-
Verify the version of the following MSISCSI driver on the system: c:\windows\system32\drivers\msiscsi.sys 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.
-
The following events are logged in the System log:
Event source
ID
Text
iScsiPrt
34
A connection to the target was lost, but the Initiator successfully reconnected to the target. Dump data contains the target name.
iScsiPrt
39
The Initiator sent a task management command to reset the target. The target name is given in the dump data.
iScsiPrt
9
Target did not respond in time for a SCSI request. The CDB is given in the dump data.
-
Review the number of threads that are running under the System process, and compare this to a known working baseline.
-
Review the number of handles that are currently opened by the System process, and compare this to a known working baseline.
-
Review the number of ephemeral ports that are being used by the System process.
-
From an administrative Powershell, run the following command:Get-NetTCPConnection | Group-Object -Property State, OwningProcess | Sort Count 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:NETSTAT –ANOQ Focus on ports that are owned by the SYSTEM process. 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.
Resolution 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.Note 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.
How to get this update
This is provided as an Optional update on Windows Update. For more information about how to run Windows Update, see How to get an update through Windows Update. To get the stand-alone package for this update, go to the Microsoft Update Catalog website.
-
Prerequisites To apply this update, you must have the Windows 8.1 and Windows Server 2012 R2 update from April 2014, KB2919355, installed.
-
File information For a list of the files that are provided in this update, download the file information for update 4019217.
Need more help?
Want more options?
Explore subscription benefits, browse training courses, learn how to secure your device, and more.
Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.
