This non-security update includes improvements and fixes that were a part of KB4034681 (released August 8, 2017) and also includes these new quality improvements as a preview of the next Monthly Rollup update:
- This package contains d3dcompiler_47.dll; for more information, read the blog post, HLSL, FXC, and D3DCompile.
- Addressed issue in the event collector data that caused data corruption with % symbols in the user logon events (ID 4624) from other Domain Controllers (DCs).
- Addressed issue where the AppLocker rules wizard crashes when selecting accounts.
- Addressed an issue where spoolsv.exe crashes.
- Addressed issue where unsynchronized access within NTFS may lead to an error.
- Addressed issue where a LUN connection that was received after the buffer allocation during iSCSI statistic collection overflowed the buffer and caused error 0x19.
- Addressed a UI issue that hides the iSCSI targets from the iSCSI initiator property windows.
- Addressed issue where an extremely high number of I/O flushes may lead to an error.
- Addressed issue where deleting an object that has many links in Active Directory causes replication to fail with Event 1084, error 8409 "A database error has occurred". For additional information, read KB3149779.
- Addressed issue with an access violation in LSASS that occurs when Active Directory receives a malformed LsaLookupNames response. The signature of the LSASS AV is "The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code -1073741819”. The system shuts down and restarts. Error 107374181 maps to 0xc0000005/STATUS_ACCESS_VIOLATION.
- Addressed issue where running chkdsk /scan unexpectedly triggers spotfix. Sometimes spotfix times out, and the system goes down.
- Addressed issue where the PowerShell cmdlet export-dfsrclone, which clones the DFSR database, fails for clustered volumes with 0x00000490=ERROR_NOT_FOUND. This prevents cloning of the DFSR databases from volumes that are already clustered.
- Addressed issue with a 4 to 17-second delay that occurs when you mount an NFS share on the Network Attached Storage from the client and execute the touch command on a file or folder. The application on the NFS clients crashes because the storage system doesn't respond to clients for a few seconds.
-
Addressed issue where Office applications may stop responding when trying to open an alternate data streams (ADS) file when that file is stored on a server that has deduplication installed.
- Addressed issue where when you enable quota on the storage servers and attempt to do backups on them, a crash may occur that results in data loss.
- Addressed issue where adding a new session host to an existing RDS collection fails. The error, "Brokername unable to configure the RD Session Host servers", occurs if the UPDs are stored in a clustered file share.
- Addressed issue where the hardware clock may drift by hours or days when running Linux VM's on Hyper-V.
For more information about the resolved security vulnerabilities, please refer to the Security Update Guide.