Microsoft Releases KB4343884 Cumulative Update for Windows 10 Anniversary Update
Please note that the Windows 10 Anniversary Update is currently out of the lifecycle and security updates are not available for Windows 10 Home and Professional.
Microsoft provides additional half-year support for the Enterprise and Education editions of the Windows 10 Anniversary Update. For other versions, please upgrade to the latest version as soon as possible.
For the Anniversary Update users, if the cumulative update is successfully installed, the system version will be upgraded to Windows 10 Build 14393.2457.
The following is the specific update log:
- Updates the music metadata service provider used by Windows Media Player.
- Addresses an issue from the March 2018 update that prevents the correct lock screen image from appearing when the following GPO policies are enabled:
- Computer Configuration\Administrative Templates\Control Panel\Personalization\Force a specific default lock screen and logon image
- Computer Configuration\Administrative Templates\Control Panel\Personalization\Prevent changing lock screen and logon image
- Addresses an issue that prevents users of PIV/CAC smart cards from authenticating to use enterprise resources or prevents Windows Hello for Business from configuring on first logon.
- Addresses an issue that prevented the Device Guard PackageInspector.exe application from including all the files needed for an application to run correctly once the Code Integrity policy was completed.
- Addresses an issue that, in some cases, failed to clear decrypted data from memory after a CAPI decryption operation was completed.
- Addresses an issue that causes PowerShell scripts to stop working when attempting operations such as Get-Credentials.
- Addresses an issue that causes the Wi-Fi EAP-TTLS (CHAP) authentication to fail if a user saves credential information before authentication.
- Addresses a Windows Task Scheduler issue that occurs when setting up an event to start on a specific day of the month. Instead of starting on the specific day of the month you selected, the event starts one week ahead of schedule. For example, if you set an event to start on the third Tuesday of August 2018, instead of starting on 08/21/18, the event starts on 08/14/18.
Addresses an issue that prevents Hypervisor from automatically launching on restart when running a nested or non-nested virtualization scenario after enabling Device Guard.
- More…
