KB5006669
詳細情報
KB番号 | KB5006669 EXPIRED |
---|---|
リリース日 | 2021/10/12 |
Windowsバージョン | Windows 10 1607 |
ビルド番号 | 14393.4704 |
URL(英語) | https://support.microsoft.com/en-us/help/5006669 |
URL(日本語) | https://support.microsoft.com/ja-jp/help/5006669 |
ダウンロード | Microsoft Update Catalog |
ハイライト
Updates security for your Windows operating system.
改良点
Package Point and Print - Approved Servers
Point and Print Restrictions
既知の不具合
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 KB5008207. |
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 KB5010359. |