Improvements and fixes
This non-security update includes improvements and fixes that were a part of Monthly Rollup KB4015550 (released April 11, 2017) and also includes these new quality improvements as a preview of the next Monthly Rollup update:
- Addressed an issue that may cause the WSMan Service (WsmSvc) to crash randomly when multiple Windows Remote Management (WinRM) requests are being executed in the WSMan Service.
- Addressed issue where the Event subscription service stops working, does not send events to the collector server, and drop events when using Windows Remote Management (WinRM) and event forwarding.
- Addressed high CPU utilization by the Wmiprvse.exe process on a computer that is running Windows 8.1 or Windows Server 2012 R2. If you run scripts or use software that queries WMI, the Wmiprvse.exe process may consume a lot of CPU resources even after you stop the script or software.
- Addressed issue where Hyper-V hosts may crash when performing incremental backups with Change Block Tracking (CBT) enabled.
- Addressed issue where the Network File System (NFS) server may not return all the directory entries to the NFS client that issues the ‘ls’ command using the NFS v3 protocol.
- Addressed issue where the read or write operation on a file that is being archived (converted) is declined, which causes a crash.
- Addressed issue where Active Directory servers become unresponsive and must be rebooted when they have a heavy load of services using group-managed service accounts (gMSAs).
- Addressed issue that caused backups to fail on Hyper-V clusters with CSV volumes enabled.
- Addressed issue where MPIO did not properly restore service after the check condition "Illegal request, LUN not available (sense codes 05/25/00)" occurs.
- Addressed issue where a node cluster experiences sporadic crashes during high I/O activities such as backup or maintenance windows. Error: Common bucket ID (WIN8_DRIVER_FAULT) - 0x3B_msiscsi!iSpReleaseConnectionReferences
- Addressed issue where the printer cannot print OPENGL rastered graphics after installing any of the following updates: KB3164035, KB3205394, KB3207752, KB3212646 and KB4012215.
- Updated the Access Point Name database.
- Addressed issue where the BADVERS return path is broken for queries with an unknown Extension Mechanisms for DNS (EDNS) version.
- Addressed issue that causes poor CPU performance when Virtual Switch Ports leak when a machine is migrated live from one host to another.
- Addressed issue where Internet Information Server returns an incorrect 500.19 internal server error for certain URIs.
- Addressed issue to updated time zone information.
- Addressed issue where thin clients connected to the server fail (STOP 0x3B) and unsaved data is lost.
- Addressed issue where an application that uses Windows Presentation Foundation technology, the mouse, and the touchscreen intermittently stop responding.
- Addressed issue where retrieval of the Certificate Revocation List (CRL) from Certification Authority (CA) using the Simple Certificate Enrollment Protocol (SCEP) fails.
- Addressed excessive memory usage in LSASS when evaluating an LDAP filter over a large record set on domain controllers.
Known issues in this update
|Symptom||Workaround / Resolution|
|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.|
After installing this update on computers where event forwarding is enabled, the WinRM service may crash. You may also experience a system performance issue, or logon may stop responding because of a deadlock in the WinRM service.
Note This applies to all KBs released from April 18, 2017 through January 8, 2018.
|This issue is resolved in KB4057401.|
|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.|
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.