KB5006672
詳細情報
KB番号 | KB5006672 |
---|---|
リリース日 | 2021/10/12 |
Windowsバージョン | Windows 10 1809 |
ビルド番号 | 17763.2237 |
URL(英語) | https://support.microsoft.com/en-us/help/5006672 |
URL(日本語) | https://support.microsoft.com/ja-jp/help/5006672 |
ダウンロード | Microsoft Update Catalog |
ハイライト
Updates security for your Windows operating system.
改良点
Addresses a known issue that prevents an internet print server from properly packaging modified printer properties before sending the package to the client.
Addresses an issue that prevents some applications, such as Microsoft Office and Adobe Reader, from opening or causes them to stop responding. This occurs on devices that are subject to Microsoft Exploit Protection for Export Address Filtering (EAF).
Addresses a known issue with Windows Server 2019 virtual machines (VMs) that use Software Defined Networks (SDN) or traditional multi-tenant Routing and Remote Access service (RRAS) gateways. These VMs might lose connectivity with external networks that use gateway connections. This issue occurs after installing KB5005102 or a later Windows update.
Addresses a known issue that might ask for administrative credentials every time you attempt to print. This occurs in environments in which the print server and print client are in different times zones.
既知の不具合
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND." |
Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows:
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. |
After installing KB5005568, installation of printers using Internet Printing Protocol (IPP) might not complete successfully. Devices which had connected to and installed the printer prior to the installation of KB5005568 are unaffected and print operations to that printer will succeed as usual. Note IPP is not commonly used by devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations. | This issue is resolved in KB5006744. |
After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server:
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 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:
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. |