Windows 8.1 July 2016 Update Rollup KB3172614

[German]Microsoft has released a July 2016 Update Rollup KB3172614 for Windows 8.1 and the corresponding Server platforms. Here are a few details about this update rollup.

Update rollup KB3172614 (July 2016 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2) includes quality improvements and fixes for Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Standard, Windows Server 2012 R2 Essentials, Windows Server 2012 R2 Foundation, Windows 8.1 Enterprise, Windows 8.1 Pro, Windows 8.1, and Windows RT 8.1.

The July 2016 update rollup includes some new improvements and fixes, dicussed in Windows 8.1 update history, including the improvements from June 2016 update rollup KB3161606 and May 2016 update rollup KB3156418 for the Windows RT 8.1, Windows 8.1, and 2012 R2 platform.

Microsoft recommends to apply this update rollup as part of your regular maintenance routines. To apply this update, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows 8.1 or Windows Server 2012 R2. And you must restart the computer after you apply this update. The packet is available via Windows Update, as a download (Links here) and via Update Catalog.

What has been fixed?

The Update-History lists many fixes and improvements for this update rollup.

• Added support for multiple account authentication using Active Directory Federation Services (ADFS) through "prompt" query parameter.
• Addressed issue in Host Bus Adapters (HBA) that was including non-Fibre Channel HBA devices in the Fibre Channel HBA list.
• Added support to set the idle timeout value of a TCP connection used by WinHTTP.
• Addressed issue where print jobs are no longer working when v4 printer drivers are configured to use Enhanced Driver Configuration.
• Remote Desktop service may hang when IP Virtualization is configured and there are a high number of remote desktop sessions.
• Improved support in Microsoft Cryptographic Application Programming Interface (CryptoAPI) to help identify websites that use Secure Hash Algorithm 1 (SHA-1).
• Running the GPRESULT command with the verbose option results in a crash and customers are unable to audit user or machine policies.
• The system reports a string corruption problem for AccessReason in the Audit logs for Event ID 4656 (Details in der Update-History).
• This update extends support of the Key Management Service (KMS) for Windows 8 and Windows Server 2012, in order to enable the activation of clients running Windows 10 Anniversary Update-based long-term servicing branch (LTSB) and Windows Server 2016 clients, when they become available.
• When you deploy Windows Server 2008 R2 Service Pack 1 (SP1) through Windows Deployment Services (WDS), if clients are Unified Extensible Firmware Interface (UEFI) and in a routed environment, they don't receive the Dynamic Host Configuration Protocol (DHCP) packets correctly. This results in WDS deployment failing on these clients.
• When you enable BitLocker on the volume and then expand the volume on Windows Server 2012 R2, there cache manager errors are shown and the commands fail. These are logged in the System log with error 141 – STATUS_MEDIA_WRITE_PROTECTED.
• When a non-administrator user opens an Access file in a WebDav folder, they might not be able save the file because of a Delete Pending error.
• When an application is writing data using the VirtualChannelWrite API closes the virtual channel right after it gets write completion event, it could result in data being discarded. 
• When you use the NVM Express (NVMe) driver to retrieve the firmware and model numbers of the solid-state drive (SSD), the NVMe driver will truncate the firmware and model numbers returned from the NVMe devices.
• When you try to configure connecting a SCSI storage device to a Windows Hyper-V Host, the Host will not recognize the SCSI storage device when Logical Unit (LUN) 0 is not present.
• When there is more logging session churn on the system because of workloads that are being run, Event Tracking (ETW) will crash.
• When you change application settings using Set-ADFSRelyingPartyTrust, without explicitly setting AlwaysRequireAuthentication, it will reset AlwaysRequireAuthentication bit to the default (false) and users won't be prompted for Multi Factor Authentication (MFA).
• When you configure Windows Server 2012 R2 for cloud based authentication, there is a high latency on the tenants for authentication and provisioning which causes the CPU usage to drop to less than 10%.
• When you try to import a certificate into a Virtual Smart Card (VSC) on a Windows based tablet (into the TPM), it might fail. This may cause the certificate to be suspended and prevent enrollment of additional certificates.
• Addressed issue in Microsoft Secure Channel (SChannel) that sometimes causes Transport Layer Security (TLS) 1.2 connections to fail depending on whether the root certificate is configured as part of the certificate chain for server authentication.
• When an Exchange server attempts to reestablish the Kerberos client session during a cluster failover it may cause the system to become unresponsive.
• Updated the inbox component in Windows Server 2012 R2 Essentials to use the new client connector, so that the inbox component won't get uninstalled during Windows 10 upgrades.
• Improved reliability of Hyper-V Replica (HVR) by increasing the timeout value and making the timeout configurable for replication to complete. Also improved logging, so that HVR doesn't stop logging when the storage left on the device is 300MB.
• If you installed the May 2016 update rollup for Windows 8.1 and Windows Server 2012 R2 (KB3156418), the DFSRS.exe process may consume a high percentage of CPU processing power (up to 100 percent). This may cause the DFSR service to become unresponsive and you may be unable to stop the service. You must hard-boot affected computers to restart them.

The last item (DFSRS. exe causes high CPU usage) may be relevant for server administrators. I haven't found any hits concerning the bluetooth issuse caused by its Windows 7 SP1 pendant so far (see Update Rollup KB3172605 for Windows 7 SP1/Server 2008 R2 SP1 screws up Bluetooth).