KB4093120

詳細情報

KB番号 KB4093120
リリース日 2018/04/17
Windowsバージョン Windows 10 1607
ビルド番号 14393.2214
URL https://support.microsoft.com/en-us/help/4093120
ダウンロード Microsoft Update Catalog

ハイライト

改良点

  • Addresses an issue that generates certificate validation error 0x800B0109 (CERT_E_UNTRUSTEDROOT) from http.sys. 

  • Addresses an issue that prevents ReFS partitions from being expanded if the volume was originally formatted using ReFS v1.

  • Addresses an issue that causes the host Hyper-V node to stop working when starting the hosted VM.

  • Addresses a Kernel deadlock that affects server availability.

  • Addresses an issue with Windows Update that prevents VMs from being saved after restarting or shutting down a computer after applying an update. vmms.exe doesn't wait for vmwp.exe to finish copying VM memory data.

  • Addresses an issue in which DTC stops responding in msdtcprx!CIConnSink::SendReceive during an XA recovery. During this failure, IXaMapper objects with identical RMIDs become corrupted.

  • Addresses an issue that prevents you from modifying or restoring Active Directory objects that have invalid backlink attributes populated in their class. The error you receive is, “Error 0x207D An attempt was made to modify an object to include an attribute that is not legal for its class.”

  • Addresses an unhandled refresh token validation issue. It generates the following error: “Microsoft.IdentityServer.Web.Protocols.OAuth.Exceptions.OAuthInvalidRefreshTokenException: MSIS9312: Received invalid OAuth refresh token. The refresh token was received earlier than the permitted time in the token.”

  • Addresses an issue that prevents ADDS DSAC from running on a client that has PowerShell Transcripting enabled. The following error appears: “Cannot connect to any domain. Refresh or try again when connection is available.”

  • Addresses an issue that causes the failover of an NFS server cluster resource to take a long time if the communication from the NFS server to the NFS client is blocked. If the failover takes more than 20 minutes, stop error 0x9E (USER_MODE_HEALTH_MONITOR) occurs.

  • Addresses an issue that may generate a capacity reserve fault warning during cluster validation or while running the Debug-StorageSubSystem cmdlet even though enough capacity is actually reserved. The warning is "The storage pool does not have the minimum recommended reserve capacity. This may limit your ability to restore data resiliency in the event of drive failure(s)."

  • Addresses an issue that may cause some files to be skipped and may create duplicate files in the Work Folder locations during full enumeration sync sessions.

  • Addresses an issue in Windows Multipoint Server 2016 that may generate the error “The MultiPoint service is not responding on this machine. To fix the issue try restarting the machine.”

  • Addresses an issue that prevents User Profile Disks (UPDs) from loading. This loading failure generates the error "We can't sign into your account", and users receive a temporary profile.

  • Addresses an issue that causes the high contrast theme setting to be applied incorrectly when a user logs in using RDP.

  • Addresses an issue that causes a pairing problem for low-energy Bluetooth devices.

  • Addresses a reliability issue with Microsoft Outlook.

  • Addresses a reliability issue that occurs while pressing the Alt key when using a Microsoft Office application hosted in an ActiveX container.

既知の不具合

After you install the March 13, 2018 or later Cumulative Update for Windows 10 Version 1607, only the latest Windows 10 feature update is returned as applicable. This prevents the deployment of previously released feature updates using ConfigMgr (current branch) and Windows 10 servicing plans.

This issue is resolved in KB4103723.

Reliability issues have been observed during the creation of shielded VMs and the required artifacts for their deployment. There are also reliability issues for the Shielding File Wizard with or without the SCVMM interface.

Note: Existing shielded VMs and HGSs are not affected.

This issue is resolved in KB4284880.