Starting with update KB4497934, we are introducing functionality that allows you to decide when to install a feature update. You control when you get a feature update while simultaneously keeping your devices up to date. Feature updates that are available for eligible devices will appear in a separate module on the Windows Update page (Settings > Update & Security > Windows Update). If you would like to get an available update right away, select Download and install now. To find out more about this feature, please go to this blog.
When Windows 10 devices are at, or within several months of reaching, end of service, Windows Update will begin to automatically initiate a feature update. This keeps those devices supported and receiving the monthly updates that are critical to device security and ecosystem health.
- Updates an issue that may cause Internet Explorer to stop working when you drag a tab to create a new window.
- Updates an issue that prevents newly installed or updated applications from appearing in Windows search results.
- Updates an issue that prevents a device from recognizing a Microsoft account until you sign out and sign in again.
- Updates an issue that affects applications that manage files, folders, and device settings.
- Improves compatibility with the Window-Eyes screen reader application.
- Updates an issue to keep your App permissions settings when resetting your device.
- Improves reliability when upgrading from Windows 10, version 1703.
Improvements and fixes
This update includes quality improvements. Key changes include:
- Addresses a performance issue that may occur on some websites that use WebAssembly.
- Addresses an issue that may cause Internet Explorer to stop working when you move a tab to create a new window.
- Addresses an issue that may prevent the personal identification number (PIN) prompt from appearing when authenticating in Internet Explorer.
- Updates time zone information for Brazil.
- Addresses an issue that may cause Windows notifications to display nonsense characters instead of a single quote (‘).
- Addresses an issue that prevents newly installed or updated applications from appearing in Windows search results.
- Address an issue that prevents SharedPC policies from migrating properly during an upgrade.
- Addresses an issue that prevents a Hardware Support application (HSA) from installing in a timely manner.
- Addresses an issue that prevents the Windows Event Log service from processing notifications that the log is full. This causes issues with some Event Log behaviors such as archiving the log when it reaches a maximum file size and you’ve configured the "Archive the log when full, do not overwrite events" setting. Additionally, the Local Security Authority (LSA) cannot handle CrashOnAuditFail scenarios when the Security Log is full, and events cannot be written.
- Addresses an issue that prevents a system from recognizing a Microsoft account or Azure Active Directory account until the user signs out and signs in again.
- 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 may cause authentication to fail when using Windows Hello for Business on a server running Windows Server 2016 with the Server Core option installed.
- Addresses an issue that doesn't update the personal identification number (PIN) policy (minimum length, required digits, special characters, and so on) for Windows Hello for Business when a PIN already exists on the machine.
- Addresses an issue that causes some processes running inside Windows Server containers and Hyper-V containers to have empty names.
- Addresses an issue that causes input and output to fail when Multipath I/O (MPIO) failover occurs.
- Addresses an issue that causes applications that use windows.storage.dll to stop working and displays ExceptionCode c0000005 (Access violation) when the process closes.
- Reinforces the Certificate Revocation List (CRL) on Internet Key Exchange version 2 (IKEv2) machines for certificate-based virtual private network (VPN) connections, such as Device Tunnel, in an Always On VPN deployment.
- Addresses an issue that intermittently prevents connections to a corporate network when using Always On VPN with the IKEv2 protocol. Connections are not always automatically established, and manual connections sometimes fail. In this scenario, when you call the RasDial function from the command line for the target VPN connection, you receive the error, “ERROR_PORT_NOT_AVAILABLE(633)”.
- Addresses an issue that changes the status for Work Folders in File Explorer to 0x80C802A0 (ECS_E_SYNC_UPLOAD_PLACEHOLDER_FAILURE) after selecting Free up space.
- 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 causes an error when using certain data persistence memory technologies.
- 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 that damages the Microsoft Message Queuing (MSMQ) feature and prevents it from starting or installing again. This issue may occur after installing Windows updates or upgrading from Windows 10, versions 1607, 1703, and 1709 to Windows 10, version 1809.
- 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 fail to keep App permissions settings when you select Keep my files after selecting Reset this PC.
- Addresses an issue with system reliability in certain scenarios when upgrading from Windows 10, version 1703.
- Addresses an issue with enrolling a device in the Windows enterprise commercial data pipeline.
- Addresses an issue that causes Windows Server 2019 to receive a D1 Stop error code when eight volumes are configured with Fiber Channel Multipath I/O (MPIO).
- 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 that exhausts User Datagram Protocol (UDP) ports on several hundred machines in a forest when there is very high Domain Controller Locator traffic. As a result, servers stop responding.
Addresses an issue that causes a Windows device to incorrectly register host A records for two network interface controllers (NIC) after establishing a virtual private network (VPN) connection to the corporate domain. This occurs when the device is configured with two NICs and one of them is a VPN. To implement this solution, make the following registry changes and then restart your device:
Value: A value of 1 means that only the host A records for the VPN interface will register on an active VPN connection. A value of 0 (default) means host A records will also be registered for other local interfaces.
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
|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:
|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.
|We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates.|| |
To mitigate this issue, press Ctrl+Alt+Delete, then select the Power button in the lower right corner of the screen and select Restart. Your device should now restart normally.
We are 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.|| |
This issue is resolved in KB4512534.
Devices connected to a domain that is configured to use MIT Kerberos realms may not start up or may continue to restart after installation of this update. Devices that are domain controllers or domain members are both affected.
If you are not sure if your device is affected, contact your administrator. Advanced users can check if this registry key exists HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\MitRealms or for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos.
|This issue is resolved in KB4511553.|
|Applications and scripts that call the NetQueryDisplayInformation API or the WinNT provider equivalent may fail to return results after the first page of data, often 50 or 100 entries. When requesting additional pages you may receive the error, “1359: an internal error occurred.” This issue occurs in this update and in all the updates before June 18, 2019.||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.
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)||No|| |
You can import this update into WSUS manually. See the Microsoft Update Catalog for instructions.
For a list of the files that are provided in this update, download the file information for cumulative update 4505658.