Microsoftは8月18日(現地時間)、Windows 10 Version 1809をはじめとした古いWindows 10の各バージョンに対し累積アップデートを公開しました(gHacks)。
今回公開された累積アップデートは以下の通りです。
- Windows 10 Version 1809: KB4512534
- Windows 10 Version 1709: KB4512494
- Windows 10 Version 1703: KB4512474
- Windows 10 Version 1607: KB4512495
- Windows 10 Version 1507: KB4517276
更新プログラムはシステムの品質を改善するもので新たな機能は追加されていません。オプション扱いの更新プログラムで、Windows Updateで手動で更新プログラムのチェックを実行するか、Microsoft Update Catalogからファイルをダウンロードしてインストールすることができます。
それぞれの累積アップデートでは、VBに関連した不具合を含め、さまざまな問題が修正されています。
目次
KB4512534 (OS Build 17763.720)
Version 1809要の累積アップデートKB4512534では、デバイスを再起動した後、Windows Helloの顔認識が機能しなくなる問題の修正や、Microsoft Edgeで横向きと縦向きのページを含むPDFドキュメントを正しく印刷できない不具合の修正、Microsoft EdgeとInternet Explorerを使用して、特定のWebサイトから著作権で保護されたデジタルメディア（音楽、テレビ番組、映画など）をダウンロードする際の問題の修正、VB関連の不具合の修正などが行われています。
ハイライト:
- Updates an issue that prevents Windows Hello face recognition from working after you restart a device.
- Allows Microsoft Edge to print PDF documents that contain landscape and portrait-oriented pages together correctly.
- Allows Microsoft Edge to open PDFs that are configured to be opened only once correctly.
- Updates an issue with downloading copyrighted digital media (music, TV shows, movies, and so on) from certain websites using Microsoft Edge and Internet Explorer.
改良と修正:
- Improves the reliability of push notifications about app deployments to Microsoft HoloLens 1 devices.
- Addresses an issue that prevents Windows Hello Face Authentication from working after a restart.
- Addresses an issue with downloading digital rights management (DRM) files from certain websites using Microsoft Edge and Internet Explorer.
- Addresses an issue that prevents the Universal C Runtime Library from returning the proper value for time zone global variables in certain conditions.
- 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 to enable Microsoft Edge to print PDF documents that contain landscape and portrait-oriented pages correctly.
- Addresses an issue with PDFs that are configured to be opened only once in Microsoft Edge.
- Addresses performance issues for the Win32 subsystem and Desktop Window Manager (DWM).
- Addresses an issue with the input and display of special characters that occurs when an app uses imm32.dll.
- Addresses a composition handle leak in Universal Windows Platform (UWP) apps.
- Addresses a memory leak in dwm.exe that may lead to a loss of functionality and cause a device to stop working.
- Addresses an issue that fails to bypass automatic sign in (Autologon) when you press and hold the Shift key during startup.
- Addresses an issue that causes the Windows Management Instrumentation (WMI) class Win32_PhysicalMemory to report that 32 GB memory chips have a missing Capacity value.
- 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 with User Experience Virtualization (UE-V) that may sometimes prevent exclusion paths from working.
- 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 prevents some Trusted Platform Module (TPM) devices from being used for Next Generation Credentials.
- Addresses an issue that causes applications on a container host to intermittently lose connectivity because of a port conflict with applications running on a container.
- 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 with the disabled attribute of the input element, which doesn’t allow a scope to be passed to the authorization endpoint.
- Addresses an issue with leaks in Windows notification sockets that causes Windows to run out of ports.
- Addresses an issue that prevents server editions from activating with a Multiple Activation Key (MAK) in the graphical user interface (GUI). The error is, “0x80070490”.
- Addresses an issue that may break the domain trust when the Recycle Bin is configured on the domain that carries the trust.
- Increases the number of supported interrupts per device to 512 on systems that have x2APIC enabled.
- 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).
更新プログラムには以下の4件の既知の不具合が存在します。
- 特定の操作をクラスター共有ボリューム上のファイルやフォルダーに対して実行すると「STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)」が発生する
- 特定のアジアの言語パックがインストールされているデバイスで「0x800f0982 - PSFX_E_MATCHING_COMPONENT _NOT_FOUND」というエラーが表示されることがある
- 更新インストール後の最初のログオン画面でブラックスクリーンが表示される場合がある
- NetQueryDisplayInformation API(または同等のWinNT provider)を呼び出すアプリケーションとスクリプトがデータの最初のページの後に結果を返さない場合がある
更新プログラムはWindows Updateの他、Microsoft Update Catalogや、Windows Server Update Services(WSUS)を利用してインストールすることができます。
