[SHOWTOGROUPS=4,20,22]
Today is the second Tuesday of the month, making it Patch Tuesday. And that means that all supported versions of Windows are getting updates.
For Windows 10, that still means all versions except for one, version 1511.
For those that are on the latest version of Windows 10, version 2004, and also for Insiders on 20H2, you'll get
Для просмотра ссылки Войди или Зарегистрируйся, bringing the build number to 19041.508 and 19042.508, respectively. You can
Для просмотра ссылки Войди или Зарегистрируйся, 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 Microsoft Office products.
Here's the full list of fixes:
- Addresses an issue with a possible elevation of privilege in windowmanagement.dll.
- Addresses a security vulnerability issue with user proxies and HTTP-based intranet servers. After installing this update, HTTP-based intranet servers cannot leverage a user proxy by default to detect updates. Scans using these servers will fail if the clients do not have a configured system proxy. If you must leverage a user proxy, you must configure the behavior using the Windows Update policy “Allow user proxy to be used as a fallback if detection using system proxy fails.” This change does not affect customers who secure their Windows Server Update Services (WSUS) servers with the Transport Layer Security (TLS) or Secure Sockets Layer (SSL) protocols. For more information, see Ensuring clients stay secure, changes to scans against Windows Server Update Service (WSUS) servers.
- Security updates to Windows App Platform and Frameworks, Microsoft Graphics Component, Windows Input and Composition, Windows Media, Windows Shell, Windows Cloud Infrastructure, Windows Fundamentals, Windows Management, Windows Kernel, Windows Virtualization, Windows Storage and Filesystems, the Microsoft Scripting Engine, and the Microsoft JET Database Engine.
There's also one known issue to be aware of:
| Symptom | Workaround |
|---|
| Users of the Microsoft Input Method Editor (IME) for Japanese or Chinese languages might experience issues when attempting various tasks. You might have issues with input, receive unexpected results, or might not be able to enter text. | For more information about the issues, workaround steps, and the currently resolved issues, please see KB4564002 |
Those on Windows 10 versions 1909 and 1903 will get
Для просмотра ссылки Войди или Зарегистрируйся, bringing the build number to 18363.1082 and 18362.1082, respectively. You can
Для просмотра ссылки Войди или Зарегистрируйся, and these are the highlights:
- 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 to improve security when using Microsoft Office products.
Here's the full list of fixes:
- Addresses a security vulnerability issue with user proxies and HTTP-based intranet servers. After installing this update, HTTP-based intranet servers cannot leverage a user proxy by default to detect updates. Scans using these servers will fail if the clients do not have a configured system proxy. If you must leverage a user proxy, you must configure the behavior using the Windows Update policy “Allow user proxy to be used as a fallback if detection using system proxy fails.” This change does not affect customers who secure their Windows Server Update Services (WSUS) servers with the Transport Layer Security (TLS) or Secure Sockets Layer (SSL) protocols. For more information, see Ensuring clients stay secure, changes to scans against Windows Server Update Service (WSUS) servers.
- Security updates to Windows App Platform and Frameworks, Microsoft Graphics Component, Windows Input and Composition, Windows Media, Windows Shell, Windows Cloud Infrastructure, Windows Fundamentals, Windows Management, Windows Kernel, Windows Virtualization, the Microsoft Scripting Engine, and the Microsoft JET Database Engine.
For those that are on Windows 10 version 1809, you'll get
Для просмотра ссылки Войди или Зарегистрируйся, bringing the build number to 17763.1457. You can
Для просмотра ссылки Войди или Зарегистрируйся, and these are the highlights:
- Updates to improve security when using Microsoft Office products.
- 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.
Here's the full list of fixes:
- Addresses a security vulnerability issue with user proxies and HTTP-based intranet servers. After installing this update, HTTP-based intranet servers cannot leverage a user proxy by default to detect updates. Scans using these servers will fail if the clients do not have a configured system proxy. If you must leverage a user proxy, you must configure the behavior using the Windows Update policy “Allow user proxy to be used as a fallback if detection using system proxy fails.” This change does not affect customers who secure their Windows Server Update Services (WSUS) servers with the Transport Layer Security (TLS) or Secure Sockets Layer (SSL) protocols. For more information, see Ensuring clients stay secure, changes to scans against Windows Server Update Service (WSUS) servers.
- Security updates to Windows App Platform and Frameworks, Microsoft Graphics Component, Windows Input and Composition, Windows Media, Windows Shell, Windows Cloud Infrastructure, Windows Fundamentals, Windows Management, Windows Kernel, Windows Virtualization, Windows Storage and Filesystems, the Microsoft Scripting Engine, and the Microsoft JET Database Engine.
There are two known issues in this update:
| 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 will provide an update in an upcoming release. |
While versions 1809 and above are still supported for all SKUs, older versions are only supported for certain SKUs.
As usual, you can grab the update that corresponds to your version of Windows 10 manually, you can push it to install through Windows Update, or you can wait for it to be installed automatically.
[/SHOWTOGROUPS]
