IMPORTANT We have been evaluating the public health situation and understand the impact this is having on many of our customers. To help ease some of the burdens customers are facing, we are going to delay the scheduled end of service date for the Home, Pro, Pro Education, Pro for Workstations, and IoT Core editions of Windows 10, version 1809 to November 10, 2020. This means devices will receive monthly security updates only from May to November. The final security update for these editions of Windows 10, version 1809 will be released on November 10, 2020 instead of May 12, 2020.
- Updates an issue with pasting mixed content of images and text from Microsoft Word into Internet Explorer.
- Updates an issue that causes a text box that contains multiple lines of text to stop responding in certain scenarios.
- Updates an issue that fails to print content that is outside of the margins of a document.
Improvements and fixes
This non-security update includes quality improvements. Key changes include:
- Addresses an issue that occurs when a third-party application loads hidden tabs into Internet Options.
- Addresses an issue with pasting mixed content of images and text from Microsoft Word into Internet Explorer.
- Addresses an issue that causes a box that contains multiple lines of text to stop responding in certain scenarios.
- Addresses an issue that prevents the first key stroke from being recognized correctly in the DataGridView cell.
- Addresses an issue that causes an application that uses msctf.dll to stop working, and the 0xc0000005 (Access violation) exception appears.
- Addresses an issue that prevents the correct lock screen from appearing when all of the following are true:
- The Group Policy Object (GPO) policy "Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Interactive Logon: Do not require Ctrl+Alt+Del Computer" is disabled.
- The GPO policy “Computer Configuration\Administrative Templates\System\Logon\Turn off app notifications on the lock screen” is enabled.
- The registry key HKLM\SOFTWARE\Policies\Microsoft\Windows\System\DisableLogonBackgroundImage is set to 1.
- Addresses a reliability issue in WDF01000.sys.
- Addresses an issue that causes a KERNEL_SECURITY_CHECK_FAILURE (139) stop error when Windows resumes from Sleep and turns on certain Bluetooth headsets.
- Addresses an issue that causes the Event Viewer Microsoft Management Console (MMC) to stop working when the secondary monitor is above the primary monitor. An out of bounds exception appears.
- Addresses an issue that causes an error in logman.exe. The error is, "A user account is required in order to commit the current Data collector Set properties."
- Addresses an issue that prevents users from setting the REG_EXPAND_SZ keys in some automated scenarios.
- Addresses an issue that causes a memory leak in the LsaIso.exe process when the server is under a heavy authentication load and Credential Guard is enabled.
- Addresses an issue that prevents hash signing using the Microsoft Platform Crypto Provider for TPMs from working correctly. This issue might also affect networking software, such as VPN applications.
- Addresses an issue with merging Windows Defender Application Control policies that sometimes generates a duplicate rule ID error and causes the Merge-CIPolicy PowerShell command to fail.
- Addresses an issue that prevents a user’s PIN from being changed after connecting the device to Microsoft Workplace Join.
- Addresses an issue that prevents applications running in an Azure Active Directory environment from receiving account change notifications. This occurs when using the Web Account Manager (WAM) and the WebAccountMonitor API.
- Addresses an issue that fails to print content that is outside of the margins of a document.
- Addresses an issue that prevents Microsoft Internet Information Services (IIS) management tools, such as IIS Manager, from managing an ASP.NET application that has configured SameSite cookie settings in web.config.
- Addresses an issue that causes high CPU usage on Active Directory (AD) domain controllers when migrating to Windows Server 2019. This increases latency in Microsoft Exchange operations, causes Managed Store contention, and severely impacts index creation in Active Directory and the Global Catalog’s performance.
- Addresses an issue that logs incorrect Internet Protocol (IP) addresses in the audit logs because of missing or old data for active requests coming from "windowstransport/usernamemixed/certificatemixed" endpoints.
- Addresses an issue that causes devices that are provisioned for Windows Hello for Business (WHfB) to fail. Registration occasionally fails, which leads to a delay in WHfB enrollment and, in some instances, creates Conflicting Objects (CNF) in the Active Directory “Registered Device” container.
- Addresses an issue that might cause a deadlock in the Remote Desktop Gateway service.
- Addresses an issue that might cause the Remote Desktop Gateway service to stop working.
- Addresses an issue that causes systems to stop working with a 0x3B stop code when running a binary that is signed by a revoked certificate.
- Addresses an issue that prevents the Notification State registries from being deleted for certain apps even after the user profile is deleted.
- Addresses an issue that causes stop error 0x18 (REFERENCE_BY_POINTER) when Remote Desktop sessions redirect devices that are not input devices.
- Addresses an issue that displays a black screen to Windows Virtual Desktop users when they attempt to sign in.
- Addresses an issue that prevents you from enabling the Japanese Input Method Editor (IME) in applications that do not have terminal server awareness when they connect to a computer using the Remote Desktop Service.
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
|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.
|After installing KB4550969 or later, when using Microsoft Edge Legacy, you might receive the error,”0x80704006. Hmmmm…can’t reach this page” when attempting to reach websites on non-standard ports. Any website that uses a port listed in the Fetch Standard specification under bad ports or port blocking might cause this issue.|| |
This issue is resolved in KB4577069.
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 general information about SSUs, see Servicing stack updates and Servicing Stack Updates (SSU): Frequently Asked Questions.
Install this update
|Release Channel||Available||Next Step|
|Windows Update or Microsoft Update||Yes||Go to Settings > Update & Security > Windows Update. In the Optional updates available area, you’ll find the link to download and install the update.|
|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 4550969.
Note Some files erroneously have “Not applicable” in the “File version” column of the CSV file. This might lead to false positives or false negatives when using some third-party scan detection tools to validate the build.