KB5006744

詳細情報

KB番号 KB5006744 Preview
リリース日 2021/10/19
Windowsバージョン Windows 10 1809
ビルド番号 17763.2268
URL(英語) https://support.microsoft.com/en-us/help/5006744
URL(日本語) https://support.microsoft.com/ja-jp/help/5006744
ダウンロード Microsoft Update Catalog

ハイライト

  • Adds miscellaneous non-security improvements. 

改良点

  • Addresses an issue with PropertyGet in JScript9.dll.

  • Addresses an issue with Assigned Access kiosks that are configured with Microsoft Edge as a kiosk application. These kiosks might sometimes fail to restart Microsoft Edge if users close the browser window.

  • Addresses an issue in which the use of App-V intermittently causes black screens to appear when signing in on the credentials page.

  • Addresses an issue that causes Windows to go into BitLocker recovery after a servicing update.

  • Addresses an issue that causes searchindexer.exe to keep handles to the per user search database in the path below after you sign out: “C:\Users\username\AppData\Roaming\Microsoft\Search\Data\Applications\<SID>\” As a result, searchindexer.exe stops working and duplicate profile names are created.

  • Addresses an issue that causes the DnsPsProvider.dll module to leak memory within a WmiPrvSE.exe process.

  • Addresses an issue that prevents Windows 10 virtual private network (VPN) users from connecting to Windows Server 2019 Routing and Remote Access service (RRAS) servers.

  • Addresses an issue that prevents Software-Defined Networking (SDN) virtual machines from working when you configure the Generic Routing Encapsulation (GRE) VPN bandwidth limitation.

  • Addresses an issue in Code Integrity that might cause a memory leak.

  • Enhances Microsoft Defender for Endpoint’s ability to identify and intercept ransomware and advanced attacks.

  • Addresses a memory leak issue in lsass.exe on domain controllers in the forest root domain that occurs when you have multiple forests and multiple domains in each forest. The SID-Name mapping functions leak memory when a request comes from another domain in the forest and crosses forest boundaries.

  • Improves the Windows Server Storage Migration Service by adding support for migration Windows Servers configured with Azure File Sync cloud tiering. Additionally, this update addresses multiple issues and improves reliability. For more information, see Storage Migration Service overview.

  • Addresses an issue with the virtual machine (VM) Load Balancing feature, which ignores a site’s fault domain.

  • Addresses a known issue that might prevent the successful installation of printers using the Internet Printing Protocol (IPP).

  • Addresses an issue that affects network interface controller (NIC) disconnect and reconnect scenarios and might cause NICs to remain in a failed state.

既知の不具合

SymptomWorkaround

After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."

  1. Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10.

  2. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10.

Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows:

  1. Go to the Settings app > Recovery.

  2. Select Get Started under the Reset this PC recovery option.

  3. Select Keep my Files.

Microsoft is working on a resolution and will provide an update in an upcoming release.

After installing KB5001342 or later, the Cluster Service might fail to start because a Cluster Network Driver is not found.

This issue occurs because of an update to the PnP class drivers used by this service.  After about 20 minutes, you should be able to restart your device and not encounter this issue.
For more information about the specific errors, cause, and workaround for this issue, please see KB5003571.

After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server:

  • 0x000006e4 (RPC_S_CANNOT_SUPPORT)

  • 0x0000007c (ERROR_INVALID_LEVEL)

  • 0x00000709 (ERROR_INVALID_PRINTER_NAME)

Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations.

This issue is resolved in KB5007266.

After installing this or later updates, Microsoft Defender for Endpoint might fail to start or run on devices with a Windows Server Core installation. 

Note This issue does not affect Microsoft Defender for Endpoint on Windows 10.

This issue is resolved in KB5008218.

After installing updates released April 22, 2021 or later, an issue occurs that affects versions of Windows Server that are in use as a Key Management Services (KMS) host. Client devices running Windows 10 Enterprise LTSC 2019 and Windows 10 Enterprise LTSC 2016 might fail to activate. This issue only occurs when using a new Customer Support Volume License Key (CSVLK). 

Note This does not affect activation of any other version or edition of Windows. 

Client devices that are attempting to activate and are affected by this issue might receive the error, "Error: 0xC004F074. The Software Licensing Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information."

Event Log entries related to activation are another way to tell that you might be affected by this issue. Open Event Viewer on the client device that failed activation and go to Windows Logs > Application. If you see only event ID 12288 without a corresponding event ID 12289, this means one of the following:

  • The KMS client could not reach the KMS host.

  • The KMS host did not respond.

  • The client did not receive the response.

For more information on these event IDs, see Useful KMS client events - Event ID 12288 and Event ID 12289.

This issue is resolved in KB5009616.

ハイライト

準備中です

改良点

準備中です

既知の不具合

準備中です