The Windows 10 April 2018 Update will reach end of service on November 12, 2019 for Home and Pro editions. We will begin updating devices running the Windows 10 April 2018 Update starting July 16, 2019 to help ensure that these devices remain in a serviced and secure state. For more information, see the Windows 10, version 1903 section of the release information dashboard.
Reminder: March 12 and April 9 were the last two Delta updates for Windows 10, version 1803. 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.
Starting with update KB4499183, 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 unintentionally removed Windows Hello credentials.
- Updates an issue that causes the Settings page to stop working and occasionally prevents default applications from being set properly.
- Updates an issue with downloading copyrighted digital media (music, TV shows, movies, and so on) from certain websites using Microsoft Edge and Internet Explorer.
Improvements and fixes
This non-security update includes quality improvements. Key changes include:
- Addresses an issue with downloading digital rights management (DRM) files from certain websites using Microsoft Edge and Internet Explorer.
- Addresses an issue that causes Deployment Image Servicing and Management (DISM) to intermittently stop responding while deprovisioning some preinstalled apps using the Microsoft System Center Configuration Manager (SCCM).
- Addresses an issue in which the default keyboard for the English (Cyprus) (en-CY) locale was not set properly.
- Addresses an issue that causes the Settings page to stop working and occasionally prevents default applications from being set properly.
- Addresses an issue that causes a query request of the Win32_LogonSession class for the StartTime to display the value of the epoch (for example, 1-1-1601 1:00:00) instead of the actual logon time. This occurs when a user who isn’t an administrator creates the query request.
- Addresses an issue that causes a Windows Management Instrumentation (WMI) call to connect to the Windows PE (WinPE) host fails with the error, “0x80070721.”
- Addresses an issue that prevents an App-V application from opening and displays a network failure error. This issue occurs under certain circumstances, such as when a system's battery is low or there is an unexpected power failure.
- Addresses an issue that unintentionally removed Windows Hello credentials after installing KB4489894.
- Addresses a rare issue that causes Windows Defender Advanced Threat Protection (ATP) to temporarily prevent other processes from accessing files.
- Addresses an issue that causes a workstation to stop working when you sign in using an updated user principal name (UPN) (for example, changing UserN@contoso.com to User.Name@contoso.com).
- Addresses an issue in which Windows Defender Application Control will not allow third-party binaries to be loaded from a Universal Windows Platform application. CodeIntegrity event error 3033 appears as, “Code Integrity determined that a process (<process name>) attempted to load <binary name> that did not meet the Store signing level requirements.”
- Addresses an issue that may break the domain trust when the Recycle Bin is configured on the domain that carries the trust.
- Addresses an issue that prevents some users from receiving a TTL value when they are added as members of Shadow Principals. This occurs for users who have distinguished names (DN) that contain an escape character. The TTL value is now added as expected.
- Addresses an issue that may prevent devices from starting when they start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) or System Center Configuration Manager (SCCM). The error is, "Status: 0xc0000001, Info: A required device isn't connected or can't be accessed."
- Addresses an issue that may cause the following to stop responding:
- Applications that were made using Visual Basic 6 (VB6).
- Macros that use Visual Basic for Applications (VBA).
- Scripts or apps that use Visual Basic Scripting Edition (VBScript).
You may also receive an "Invalid procedure call” error.
If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.
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:
|We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates.|| |
This issue is resolved in KB4519978.
|After installing this update, Windows Mixed Reality Portal users may intermittently receive a “15-5” error code. In some cases, Windows Mixed Reality Portal may report that the headset is sleeping and pressing “Wake up” may appear to produce no action.|| |
This issue is resolved in KB4519978.
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.|
|Windows Server Update Services (WSUS)||Yes|| |
This update will automatically synchronize with WSUS if you configure Products and Classifications as follows:
Product: Windows 10
For a list of the files that are provided in this update, download the file information for cumulative update 4512509.