Microsoft releases Windows 10 builds 16299.755, 15063.1418 - here's what's new

Today, Microsoft released new cumulative updates for older yet supported versions of Windows 10 for PCs. Today's builds are for versions 1709, 1703, and 1607, meaning that there's nothing new for the current version, 1803, and no news on version 1809, which was pulled from Windows Update due to files getting deleted after installing the upgrade.

Microsoft seems to be doing something new with cumulative updates, and this is the second month in a row that the firm has done it this way. the second Tuesday of the month is still Patch Tuesday when every supported version gets an update, but the changelogs are pretty minor. Then, the longer lists of fixes show up in new updates later in the month.

If you're still on the Windows 10 Fall Creators Update, or version 1709, you'll get KB4462932, which brings the build number to 16299.755. You can manually download it here, and it contains the following fixes:

  • Addresses the redenomination of local currency that the Central Bank of Venezuela implemented to enter the Bolivar Soberano into circulation.

  • Addresses an issue in which searching using Microsoft Outlook’s Social Connector returns nothing, which causes the People's pane results to always be empty.

  • Addresses additional issues with updated time zone information.

  • Addresses an issue that prevents the clock and date flyout from appearing when the region format is Spanish (Spain) and the sorting method is Traditional.

  • Addresses an issue with navigation from the Decade view in the Japanese calendar. When the user tries to go from the Current era to the next era, navigation does not work properly.

  • Addresses an issue to support Microsoft Office events in the “Limit Enhanced” Group Policy setting list.

  • Addresses an issue in which applications on systems with more than 4 GB of memory receive Access Denied error code “0x5” when calling CreateProcessWithLogonW().

  • Addresses an issue that makes it impossible to disable TLS 1.0 and TLS 1.1 when the Federal Information Processing Standard (FIPS) mode is enabled.

  • Addresses an issue in which the AccountName in the Event Log entry for the Microsoft-Windows-Kerberos-Key-Distribution-Center source and Event ID 7 sometimes appears corrupted.

  • Addresses an issue in which applications have handle leaks when using client authentication certificates with the TLS protocol. This issue occurs when the FreeCredentialsHandle call occurs before the DeleteSecurityContext call in application code.

  • Addresses an issue that might cause TCP connections opened for an application running on Windows Container to fail sporadically. This occurs when the container runs on a Network Address Translation (NAT) Network provided by Windows Network Address Translation (WinNAT). A SYN timeout occurs after reaching the maximum SYN Retransmit count.

  • Addresses an issue that prevents the deletion of Immediate Tasks when their deletion timer occurs, such as when you configure Group Policy preferences for Immediate Task actions.

  • Addresses an issue that can cause App-V packages to fail because of a missing file or DLL error.

  • Addresses an issue that may cause certain applications to stop responding after installation.

  • Addresses an issue that fails to mount a volume when running Mount-SRDestination to bring a destination volume online as part of the Test Failover feature.

  • Addresses an issue in which the System.Security.Cryptography.Algorithms reference was not correctly loaded on .NET Framework 4.7.1 after the July 10, 2018 and August 14, 2018 patches.

  • Addresses an issue that may cause the system to stop working during the shutdown of some Windows Presentation Foundation (WPF) apps because of TaskCanceledException. Apps that are vulnerable to this issue perform work involving weak events or data binding after the Application.Run() function returns values.

  • Addresses a race condition in temporary files and some antivirus scanners that causes .NET Framework applications to stop working. The error message is, "The process cannot access the file ".

  • Updates the .NET Framework's support for the formatting of Japanese dates for the first year in the eras. When the format pattern is “y年”, the year format will use the symbol 元 and not use year number 1. Additionally, the .NET Framework will support dates that include 元.

  • Updates Venezuela currency information. This will affect the culture of “es-VE” as follows:

    • The currency symbol is “Bs.S”.

    • The English currency name is “Bolívar Soberano”.

    • The local currency name is “bolívar soberano”.

    • The International Currency Code is “VES”.

  • Addresses an issue with a dialog box that may appear with a non-applicable message beginning with the words, “Hosted by...” when first starting Microsoft Edge. The dialog box only appears if you have turned on “Block only third-party cookies” in Microsoft Edge and applied certain language packs after installing the October 9, 2018 update.

  • Addresses an issue that may cause an application that has a child window to stop processing mouse inputs. This issue occurs when a precision touchpad triggers a WM_MOUSEWHEEL event.

Next up is the Windows 10 Creators Update, or version 1803. Users on that version will get KB4462939, and that will bring the build number to 15063.1418. To be clear, version 1703 is unsupported for most users, and if your PC is on the Creators Update, you won't get this update. The only SKUs still supported are Enterprise and Education. You can manually download the update here, and it contains the following fixes:

  • Addresses the redenomination of local currency that the Central Bank of Venezuela implemented to enter the Bolivar Soberano into circulation.

  • Addresses additional issues with updated time zone information.

  • Addresses an issue that may cause the operating system to stop responding when transitioning from Sleep to Hibernation.

  • Addresses an issue with navigation from the Decade view in the Japanese calendar. When the user tries to go from the Current era to the next era, navigation does not work properly.

  • Addresses an issue with cloud authentication performance for accounts that create logon sessions very quickly.

  • Addresses an issue that makes it impossible to disable TLS 1.0 and TLS 1.1 when the Federal Information Processing Standard (FIPS) mode is enabled.

  • Addresses an issue in which applications on systems with more than 4 GB of memory receive Access Denied error code “0x5” when calling CreateProcessWithLogonW().

  • Addresses an issue in which applications have handle leaks when using client authentication certificates with the TLS protocol. This issue occurs when the FreeCredentialsHandle call occurs before the DeleteSecurityContext call in application code.

  • Addresses an issue that can cause App-V packages to fail because of a missing file or DLL error.

  • Addresses an issue in which the System.Security.Cryptography.Algorithms reference was not correctly loaded on .NET Framework 4.7.1 after the July 10, 2018 and August 14, 2018 patches.

  • Addresses an issue that may cause the system to stop working during the shutdown of some Windows Presentation Foundation (WPF) apps because of TaskCanceledException. Apps that are vulnerable to this issue perform work involving weak events or data binding after the Application.Run() function returns values.

  • Addresses a race condition in temporary files and some antivirus scanners that causes .NET Framework applications to stop working. The error message is, "The process cannot access the file ".

  • Updates the .NET Framework's support for the formatting of Japanese dates for the first year in the eras. When the format pattern is “y年”, the year format will use the symbol 元 and not use year number 1. Additionally, the .NET Framework will support dates that include 元.

  • Updates Venezuela currency information. This will affect the culture of “es-VE” as follows:

    • The currency symbol is “Bs.S”.

    • The English currency name is “Bolívar Soberano”.

    • The local currency name is “bolívar soberano”.

    • The International Currency Code is “VES”.

  • Addresses an issue with a dialog box that may appear with a non-applicable message beginning with the words, “Hosted by...” when first starting Microsoft Edge. The dialog box only appears if you have turned on “Block only third-party cookies” in Microsoft Edge and applied certain language packs after installing the October 9, 2018 update.

Finally, those on the Windows 10 Anniversary Update (version 1607) or Windows Server 2016 will get KB4462928, bringing the build number to 14393.2580. This update is also for Enterprise and Education SKUs, as well as for Long-Term Servicing Channel (LTSC) customers. You can manually download it here, and it contains the following fixes:

  • Addresses the redenomination of local currency that the Central Bank of Venezuela implemented to enter the Bolivar Soberano into circulation.

  • Addresses additional issues with updated time zone information.

  • Addresses an issue in which no error message appears when a blocked app is invoked from the Start menu.

  • Addresses an issue in which the AccountName in the Event Log entry for the Microsoft-Windows-Kerberos-Key-Distribution-Center source and Event ID 7 sometimes appears corrupted.

  • Addresses an issue with cloud authentication performance for accounts that create logon sessions very quickly.

  • Addresses an issue that makes it impossible to disable TLS 1.0 and TLS 1.1 when the Federal Information Processing Standard (FIPS) mode is enabled.

  • Addresses an issue that maps two or more certificates for authentication to the same user. The user receives the message, “Duplicates found” and receives the error, “STATUS_CERTIFICATE_MAPPING_NOT_UNIQUE”.

  • Addresses an issue in which applications have handle leaks when using client authentication certificates with the TLS protocol. This issue occurs when the FreeCredentialsHandle call occurs before the DeleteSecurityContext call in application code.

  • Addresses memory leak issues on svchost.exe (netsvcs and IP Helper Service).

  • Addresses an issue that depletes the storage space on a cluster-shared volume (CSV) because of a Hyper-V virtual hard disk (VHDX) expansion. As a result, a Virtual Machine (VM) might continue writing data to its disk until it becomes corrupted or stops working. The VM might also restart and then resume writing data until a corruption occurs.

  • Addresses an issue that causes the promotion of a read-only domain controller (RODC) to fail. This might occur if application partitions are defined, but the DNS name resolution failed with the “Name error”. The errors are “While promoting Read-only Domain Controller, the expected state objects could not be found” and “More data is available” (error code 234).

  • Addresses interoperation issues between Active Directory Federation Services (ADFS) Extranet Smart Lockout (ESL) and Alternate Login ID. When Alternate Login ID is enabled, calls to AD FS Powershell cmdlets, Get-AdfsAccountActivity and Reset-AdfsAccountLockout, return "Account not found" errors. When Set-AdfsAccountActivity is called, a new entry is added instead of editing an existing one.

  • Addresses an issue with navigation from the Decade view in the Japanese calendar. When the user tries to go from the Current era to the next era, navigation does not work properly.

  • Addresses an issue that causes the Remote Desktop Services Gateway to stop working effectively in a load balanced scenario after 12 to 24 hours of uptime.

  • Addresses an issue that occurs when using multiple Windows Server 2016 Hyper-V clusters. The following event appears in the log:

  • “Cluster Shared Volume 'CSVName' ('CSVName') has entered a paused state because of 'STATUS_USER_SESSION_DELETED(c0000203)'. All I/O will temporarily be queued until a path to the volume is reestablished.”

  • Addresses an issue that may cause the creation of a single node cluster or the addition of more nodes to a cluster to fail intermittently.

  • Addresses an issue that occurs when restarting a node after draining the node. Event ID 5120 appears in the log with a “STATUS_IO_TIMEOUT c00000b5” message. This may slow or stop input and output (I/O) to the VMs, and sometimes the nodes may drop out of cluster membership.

  • Addresses an issue in which the System.Security.Cryptography.Algorithms reference was not correctly loaded on .NET Framework 4.7.1 after the July 10, 2018 and August 14, 2018 patches.

  • Addresses an issue that may cause the system to stop working during the shutdown of some Windows Presentation Foundation (WPF) apps because of TaskCanceledException. Apps that are vulnerable to this issue perform work involving weak events or data binding after the Application.Run() function returns values.

  • Addresses a race condition in temporary files and some antivirus scanners that causes .NET Framework applications to stop working. The error message is, "The process cannot access the file ".

  • Updates the .NET Framework's support for the formatting of Japanese dates for the first year in the eras. When the format pattern is “y年”, the year format will use the symbol 元 and not use year number 1. Additionally, the .NET Framework will support dates that include 元.

  • Updates Venezuela currency information. This will affect the culture of “es-VE” as follows:

    • The currency symbol is “Bs.S”.

    • The English currency name is “Bolívar Soberano”.

    • The local currency name is “bolívar soberano”.

    • The International Currency Code is “VES”.

  • Addresses an issue that may cause the addition of nodes to fail intermittently after creating a single node in a Windows Server 2016 Cluster. The error code is, “0x0000001e”.

  • Addresses an issue that may cause an application that has a child window to stop processing mouse inputs. This issue occurs when a precision touchpad triggers a WM_MOUSEWHEEL event.

Unlike the other issues, this one has a known issue to be aware of:

Symptom Workaround
After installing this update, installing Window Server 2019 Key Management Service (KMS) host keys (CSVLK) on Window Server 2016 KMS hosts does not work as expected. Microsoft is working on a resolution and will provide an update in an upcoming release.


As always, there's no need to manually install the updates if you don't want to, as Windows Update will install them automatically.

Report a problem with article
1529077124_screen_shot_2018-06-15_at_8.36.55_am
Next Article

New patent suggests Apple may introduce smart systems to its mapping app

1539818746_img_4535
Previous Article

Unboxing and first impressions of Microsoft's Surface Go

6 Comments - Add comment

Advertisement