Microsoft releases Windows 10 builds 19041.450, 18363.1016 - here's what's new

Today is Patch Tuesday, and you know what that means. Every supported version of Windows is getting an update today, and for Windows 10, that still includes every version except for version 1511. Of course, the only versions that are supported for consumers are versions 1809 to present.

If you're on Windows 10 version 2004, or if you're an Insider on Windows 10 20H2, you're going to get KB4566782, bringing the build number to 19041.450 or 19042.450, respectively. You can manually download it here, and these are the highlights:

Updates to improve security when using input devices (such as a mouse, keyboard, or pen).

Updates to improve security when Windows performs basic operations.

Updates for storing and managing files.

Updates to improve security when using Internet Explorer and Microsoft Edge Legacy.

Updates to improve security when using Microsoft Office products.

Updates for verifying usernames and passwords.

Here's the list of fixes:

Addresses an issue in Universal Windows Platform (UWP) apps that allows single sign-on authentication when an app does not have the Enterprise Authentication capability. With the release of CVE-2020-1509, UWP applications might begin prompting the user for credentials.

Security updates to the Microsoft Scripting Engine, Internet Explorer, Windows Graphics, Microsoft Graphics Component, Windows Kernel, Windows Input and Composition, Windows Media, Windows Shell, the Windows Wallet Service, Microsoft Edge Legacy, Windows Cloud Infrastructure, Windows Authentication, the Windows AI Platform, Windows Fundamentals, Windows Storage and Filesystems, Windows Update Stack, Windows File Server and Clustering, Windows Hybrid Storage Services, Windows App Platform and Frameworks, Microsoft JET Database Engine, and Windows SQL components.

There's also one known issue to be aware of:

Symptom	Workaround
When using some apps, such as Microsoft Excel, users of the Microsoft Input Method Editor (IME) for Chinese and Japanese might receive an error, or the app might stop responding or close when attempting to drag using the mouse.	For more information and workaround steps, please see KB4564002.

For those on Windows 10 version 1909 or 1903, you'll get KB4565351, bringing the version number to 18363.1016 or 16362.1016, respectively. You can manually download it here, and these are the highlights:

Updates to improve security when using Internet Explorer and Microsoft Edge Legacy.

Updates to improve security when using input devices (such as a mouse, keyboard, or pen).

Updates to improve security when Windows performs basic operations.

Updates for verifying usernames and passwords.

Here's the full list of fixes:

Addresses an issue in Universal Windows Platform (UWP) apps that allows single sign-on authentication when an app does not have the Enterprise Authentication capability. With the release of CVE-2020-1509, UWP applications might begin prompting the user for credentials.

Security updates to the Microsoft Scripting Engine, Internet Explorer, Windows Graphics, Windows Input and Composition, Windows Media, Windows Shell, the Windows Wallet Service, Microsoft Edge Legacy, Windows Cloud Infrastructure, Windows Authentication, Windows AI Platform, Windows Fundamentals, Windows Kernel, Windows Update Stack, Windows File Server and Clustering, Windows Hybrid Storage Services, Windows App Platform and Frameworks, and the Microsoft JET Database Engine.

If you're still on Windows 10 version 1809, you'll get KB4565349, bringing the build number to 17763.1397. You can manually download it here, and these are the highlights:

Updates to improve security when using Internet Explorer and Microsoft Edge Legacy.

Updates to improve security when Windows performs basic operations.

Updates to improve security when using input devices (such as a mouse, keyboard, or pen).

Updates for verifying usernames and passwords.

Updates for storing and managing files.

Here's the full list of fixes:

Addresses an issue in Universal Windows Platform (UWP) apps that allows single sign-on authentication when an app does not have the Enterprise Authentication capability. With the release of CVE-2020-1509, UWP applications might begin prompting the user for credentials.

Provides the ability for a Windows Embedded Compact 2013 OS instance and applications to operate on top of Windows 10 IoT Core using Windows CE App Container.

Security updates the Microsoft Scripting Engine, Internet Explorer, Windows Graphics, Windows Input and Composition, Windows Media, Windows Shell, the Windows Wallet Service, Microsoft Edge Legacy, Windows Cloud Infrastructure, Windows Authentication, the Windows AI Platform, Windows Fundamentals, Windows Kernel, Windows Storage and Filesystems, Windows Update Stack, Windows File Server and Clustering, Windows Hybrid Storage Services, Windows App Platform and Frameworks, the Microsoft JET Database Engine, and Windows Remote Desktop.

There are two known issues to be aware of:

Symptom	Workaround
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."	Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. 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.	To mitigate this issue, you can do one of the following: Update to the new, Chromium-based Microsoft Edge and configure it to allow the port used for the affected site. See the note below. Use Internet Explorer 11 to access the website. Update Windows 10 to a newer version. Configure the website to use a standard port on the server side. Don’t use a port that is listed in the Fetch Standard specification under bad ports or port blocking. Note The new, Chromium-based Microsoft Edge will also fail to connect to websites on non-standard ports by default. This is an expected behavior. However, you can allow sites on the affected non-standard port by using the parameter --explicitly-allowed-ports=####, where #### is the port you require. For example, when you need to access a website on port 6667, type c:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe--explicitly-allowed-ports=6667 We are working on a resolution and

Symptom

Workaround

After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."

Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10.
Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10.

Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows:

Go to the Settings app > Recovery.
Select Get Started under the Reset this PC recovery option.
Select Keep my Files.

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.

To mitigate this issue, you can do one of the following:

Update to the new, Chromium-based Microsoft Edge and configure it to allow the port used for the affected site. See the note below.
Use Internet Explorer 11 to access the website.
Update Windows 10 to a newer version.
Configure the website to use a standard port on the server side. Don’t use a port that is listed in the Fetch Standard specification under bad ports or port blocking.

Note The new, Chromium-based Microsoft Edge will also fail to connect to websites on non-standard ports by default. This is an expected behavior. However, you can allow sites on the affected non-standard port by using the parameter --explicitly-allowed-ports=####, where #### is the port you require. For example, when you need to access a website on port 6667, type c:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe--explicitly-allowed-ports=6667

We are working on a resolution and

Finally, there are a bunch of updates that are for versions that are only supported for specific SKUs.

Version	KB	Build	Download	Support
1803	KB4571709	17134.1667	Update Catalog	Enterprise and Education SKUs
1709	KB4571741	16299.2045	Update Catalog	Enterprise and Education SKUs
1703	KB4571689	15063.2467	Update Catalog	Surface Hub only
1607	KB4571694	14393.3866	Update Catalog	Long-Term Servicing Branch
1507	KB4571692	10240.18666	Update Catalog	Long-Term Servicing Branch