Windows 10: Cumulative Update KB4507459 Windows 10 v1607 Build 14393.3115 July 16

Brink · Jul 16, 2019

July 16, 2019 - KB4507459 (OS Build 14393.3115)

Applies to: Windows 10 version 1607, Windows Server 2016

Reminder: The additional servicing for Windows 10 Enterprise, Education, and IoT Enterprise editions ends on April 9, 2019 and doesn't extend beyond this date. To continue receiving security and quality updates, Microsoft recommends updating to the latest version of Windows 10.

Reminder: March 12 and April 9 will be the last two Delta updates for Windows 10, version 1607. For Long-Term Servicing Branch (LTSB) customers, security and quality updates will continue to be available via the express and full cumulative update packages. For more information on this change please visit our blog.

Windows 10, version 1607, reached end of service on April 10, 2018. Devices running Windows 10 Home or Pro editions will no longer receive monthly security and quality updates that contain protection from the latest security threats. To continue receiving security and quality updates, Microsoft recommends updating to the latest version of Windows 10.
IMPORTANT: Windows 10 Enterprise and Windows 10 Education editions will receive additional servicing at no cost until April 9, 2019. Devices on the Long-Term Servicing Channels (LTSC) will continue to receive updates until October 2026 per the Lifecycle Policy page. Windows 10 Anniversary Update (v. 1607) devices running the Intel “Clovertrail” chipset will continue to receive updates until January 2023 per the Microsoft Community blog.

Windows Server 2016 Standard edition, Nano Server installation option and Windows Server 2016 Datacenter edition, Nano Server installation option reached end of service on October 9, 2018. These editions will no longer receive monthly security and quality updates that contain protection from the latest security threats. To continue receiving security and quality updates, Microsoft recommends updating to the latest version of Windows 10.

Windows 10 Mobile, version 1607, reached end of service on October 8, 2018. Devices running Windows 10 Mobile and Windows 10 Mobile Enterprise will no longer receive monthly security and quality updates that contain protection from the latest security threats. To continue receiving security and quality updates, Microsoft recommends updating to the latest version of Windows 10.

For more information about the various types of Windows updates, such as critical, security, driver, service packs, etc., please see the following article.

Highlights

Updates an issue that affects applications that manage files, folders, and device settings.

Improves compatibility with the Window-Eyes screen reader application.

Improvements and fixes

This update includes quality improvements. Key changes include:

Addresses an issue that may prevent the personal identification number (PIN) prompt from appearing when authenticating in Internet Explorer.

Addresses an issue with leaking Windows notification sockets that causes Windows to run out of ports.

Updates time zone information for Brazil.

Addresses an issue that displays the Power button on the Ctrl+Alt+Del screen when the "User Configuration\Administrative Templates\Start Menu and Taskbar\Remove and prevent access to the Shut Down, Restart, Sleep, and Hibernate commands" policy is enabled.

Addresses an issue that fails to bypass automatic sign in (Autologon) when you press and hold the Shift key during startup.

Addresses an issue that may prevent the Netlogon service from establishing a secure channel and reports the error, “0xC000007A – ERROR_PROC_NOT_FOUND.”

Addresses an issue that causes Windows Defender Application Control to generate too many events related to dynamic code generation.

Addresses an issue that causes applications that use windows.storage.dll to stop working and displays ExceptionCode c0000005 (Access violation) when the process closes.

Addresses an issue that causes the Storage Spaces Direct (S2D) pool to lose Pool Quorum and prevents access to the S2D volumes if you restart one of the S2D cluster nodes.

Addresses an issue in Microsoft Remote Desktop Web Access (RDWeb) that allows user passwords to be updated even if there is a "Confirm New Password" field error.

Addresses an issue that may cause a Remote Desktop Server to stop responding when someone who is using drive redirection disconnects.

Addresses an issue that may prevent some applications from running as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installing KB4493473 on the server. Applications that may exhibit this behavior use an IFRAME during non-interactive authentication requests and receive X-Frame Options set to DENY.

Addresses an issue that prevents Microsoft Application Virtualization (App-V) scripting from working if you run it when you’re not connected to a domain controller (DC). App-V scripting also fails when you run it in an environment that only contains Microsoft Azure Active Directory.

Addresses an issue with opening or using the Window-Eyes screen reader application that may result in an error and prevent some features from functioning as expected.

Addresses an issue that may cause a cluster node to lose membership in a cluster and cause all its workloads to fail over. This issue may occur when a cluster node creates a Live Dump.

If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.

Windows Update Improvements
Microsoft has released an update directly to the Windows Update client to improve reliability. Any device running Windows 10 configured to receive updates automatically from Windows Update, including Enterprise and Pro editions, will be offered the latest Windows 10 feature update based on device compatibility and Windows Update for Business deferral policy. This doesn't apply to long-term servicing editions.

Known issues in this update

Symptom Workaround For hosts managed by System Center Virtual Machine Manager (SCVMM), SCVMM cannot enumerate and manage logical switches deployed on the host after installing the update.
Additionally, if you do not follow the best practices, a stop error may occur in vfpext.sys on the hosts.

Run mofcomp on the following mof files on the affected host:

Scvmmswitchportsettings.mof

VMMDHCPSvr.mof

Follow the best practices while patching to avoid a stop error in vfpext.sys in an SDN v2 environment (NC managed hosts).

After installing KB4467684, the cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the group policy “Minimum Password Length” is configured with greater than 14 characters. Set the domain default "Minimum Password Length" policy to less than or equal to 14 characters.

Microsoft is working on a resolution and will provide an update in an upcoming release. Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Do one of the following:

Perform the operation from a process that has administrator privilege.

Perform the operation from a node that doesn’t have CSV ownership.

Microsoft is working on a resolution and will provide an update in an upcoming release. Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) or System Center Configuration Manager (SCCM) may fail to start with the error "Status: 0xc0000001, Info: A required device isn't connected or can't be accessed" after installing this update on a WDS server. For mitigation instructions, see KB4512816.

We are working on a resolution and will provide an update in an upcoming release.
How to get this update

Before installing this update

Microsoft strongly recommends you install the latest servicing stack update (SSU) for your operating system before installing the latest cumulative update (LCU). SSUs improve the reliability of the update process to mitigate potential issues while installing the LCU. For more information, see Servicing stack updates.

If you are using Windows Update, the latest SSU (KB4509091) will be offered to you automatically. To get the standalone package for the latest SSU, search for it in the Microsoft Update Catalog.

Install this update

Release Channel Available Next Step Windows Update or Microsoft Update Yes Go to Settings > Update & Security > Windows Update and select Check for updates. Microsoft Update Catalog Yes To get the standalone package for this update, go to the Microsoft Update Catalog website. Windows Server Update Services (WSUS) Yes You can import this update into WSUS manually. See the Microsoft Update Catalog for instructions.
File information

For a list of the files that are provided in this update, download the file information for cumulative update 4507459.
Click to expand...

Source: https://support.microsoft.com/en-us/help/4507459

Direct download links for KB4507459 from Microsoft Update Catalog:

*Arrow Download KB4507459 MSU for Windows 10 Version 1607 32-bit (x86) - 790.0 MB

*Arrow Download KB4507459 MSU for Windows 10 Version 1607 64-bit (x64) - 1417.0 MB

Tip Find Windows 10 Version Number

Find Windows 10 Build Number

:)

Bree · Jul 16, 2019

Cumulative Update KB4034658 Windows 10 v1607 Build 14393.1593

All went in fine. Seems a safe one. But noticed after today's updates my update history was wiped in that it now says 'no updates have been installed yet'
Click to expand...

You will still see all previous updates listed if you look in the Control Panel. @dalchina reported the same thing happening with the July 18th KB4025334...
Cumulative Update KB4025334 Windows 10 v1607 Build 14393.1532

My possible explanation then was...

Update history saying 'no updates have been installed yet' while Control Panel still shows the list of installed updates is exactly what you'd see if you Reset Windows Update in Windows 10. There's nothing obvious in the list of 'issues addressed' that says it would reset Windows Update, but it's a plausible explanation.
Click to expand...

If you didn't get KB4025334 then whatever 'fix' did this would have been installed by this Cumulative Update.

Brink · Jul 16, 2019

Cumulative Update KB4023680 Windows 10 v1607 Build 14393.1230

Installing now.

Brink · Jul 16, 2019

Cumulative Update KB4038782 Windows 10 v1607 Build 14393.1715

Update: Cumulative Update KB4038801 Windows 10 v1607 Build 14393.1737 - Windows 10 Forums

Windows 10: Cumulative Update KB4507459 Windows 10 v1607 Build 14393.3115 July 16

Cumulative Update KB4507459 Windows 10 v1607 Build 14393.3115 July 16

Cumulative Update KB4507459 Windows 10 v1607 Build 14393.3115 July 16

Cumulative Update KB4507459 Windows 10 v1607 Build 14393.3115 July 16

Cumulative Update KB4507459 Windows 10 v1607 Build 14393.3115 July 16 - Similar Threads - Cumulative Update KB4507459

Cumulative Update KB4507467 Windows 10 v1703 Build 15063.1955 July 16

Cumulative Update KB4507460 Windows 10 v1607 Build 14393.3085 - July 9

Cumulative Update KB4346877 Windows 10 v1607 Build 14393.2396 -July 30

Cumulative Update KB4345455 Windows 10 v1507 Build 10240.17918 July 16

Cumulative Update KB4345418 Windows 10 v1607 Build 14393.2368 -July 16

Cumulative Update KB4025334 Windows 10 v1607 Build 14393.1532 -July 18

Cumulative Update KB4345419 Windows 10 v1703 Build 15063.1208 -July 16

Cumulative Update KB4345420 Windows 10 v1709 Build 16299.550 - July 16

Cumulative Update KB4338814 Windows 10 v1607 Build 14393.2363 -July 10

Users found this page by searching for:

kb4507459

kb4507459 kb4507460

kb4507459 didnt appear in sccm