KB4561608

詳細情報

KB番号 KB4561608
リリース日 2020/06/09
Windowsバージョン Windows 10 1809
ビルド番号 17763.1282
URL https://support.microsoft.com/en-us/help/4561608
ダウンロード Microsoft Update Catalog

ハイライト

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

  • Updates to improve security when Windows performs basic operations.

  • Updates to improve security when using Microsoft Office products.

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

  • Improves security in Microsoft Xbox and the Microsoft Store.

  • Updates for verifying usernames and passwords.

  • Updates for storing and managing files.

改良点

  • Addresses an issue that prevents users from updating .msi files from a network folder.

  • Addresses an issue that causes the promotion of a server to a domain controller to fail. This occurs when the Local Security Authority Subsystem Service (LSASS) process is set as Protected Process Light (PPL).

  • Security updates to the Microsoft Scripting Engine, Microsoft Edge, Internet Explorer, Windows App Platform and Frameworks, Windows Media, Windows Kernel, Microsoft Graphics Component, Windows Input and Composition, Windows Shell, Microsoft Xbox, the Microsoft Store, Windows Cloud Infrastructure, Windows Fundamentals, Windows Management, Windows Authentication, Windows Cryptography, Microsoft HoloLens, Windows Virtualization, Windows Storage and Filesystems, Windows File Server and Clustering, Windows Hybrid Storage Services, the Microsoft JET Database Engine, and the Windows Update Stack.

既知の不具合

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

This issue is addressed by updates released June 11, 2019 and later. We recommend you install the latest security updates for your device. Customers installing Windows Server 2019 using media should install the latest Servicing Stack Update (SSU) before installing the language pack or other optional components. If using the Volume Licensing Service Center (VLSC), acquire the latest Windows Server 2019 media available. The proper order of installation is as follows:

  1. Install the latest prerequisite SSU, currently KB5005112

  2. Install optional components or language packs

  3. Install latest cumulative update

Note Updating your device will prevent this issue, but will have no effect on devices already affected by this issue. If this issue is present in your device, you will need to use the workaround steps to repair it.

Workaround:

  1. Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10.

  2. Click Check for Updates and install the April 2019 Cumulative Update or later. For instructions, see Update Windows 10.

Note If reinstalling the language pack does not mitigate the issue, use the In-Place-Upgrade feature. For guidance, see How to do an in-place upgrade on Windows, and Perform an in-place upgrade of Windows Server.

After installing this update, certain printers might fail to print. The print spooler might throw an error or close unexpectedly when attempting to print, and no output will come from the affected printer.

You might also encounter issues with the apps you are attempting to print from. You might receive an error from the app or the app might close unexpectedly.

Note This issue might also affect software-based printers, for example printing to PDF.

This issue is resolved in KB4567513.

The Local Security Authority Subsystem Service (LSASS) file (lsass.exe) might fail on some devices with the error message, “A critical system process, C:\WINDOWS\system32\lsass.exe, failed with status code c0000008. The machine must now be restarted."

This issue is resolved in KB4558998.

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.