KB5018482
詳細情報
KB番号 | KB5018482 Preview |
---|---|
リリース日 | 2022/10/25 |
Windowsバージョン | Windows 10 21H2 / Windows 10 21H1 / Windows 10 20H2 |
ビルド番号 | 19044.2193 / 19043.2193 / 19042.2193 |
URL(英語) | https://support.microsoft.com/en-us/help/5018482 |
URL(日本語) | https://support.microsoft.com/ja-jp/help/5018482 |
ダウンロード | Microsoft Update Catalog |
ハイライト
It addresses an issue that causes an OS upgrade to stop responding, and then it fails.
It addresses an issue that affects the font of three Chinese characters. When you format these characters as bold, the width size is wrong.
It addresses an issue that affects Microsoft Direct3D 9 games. The graphics hardware stops working if the hardware does not have a native Direct3D 9 driver.
It addresses graphical issues in games that use Microsoft D3D9 on some platforms.
It addresses an issue that affects Microsoft Edge when it is in IE Mode. The titles of pop-up windows and tabs are wrong.
It addresses an issue that affects the lasso tool in a graphics editing program.
It stops the start of daylight saving time in Jordan at the end of October 2022. The Jordan time zone will permanently shift to the UTC + 3 time zone.
改良点
It addresses an issue that affects Distributed Component Object Model (DCOM) authentication hardening. It automatically raises the authentication level for all non-anonymous activation requests from DCOM clients to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY. This occurs if the authentication level is below Packet Integrity.
It addresses a DCOM issue that affects the Remote Procedure Call Service (rpcss.exe). It raises the authentication level to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY instead of RPC_C_AUTHN_LEVEL_CONNECT if RPC_C_AUTHN_LEVEL_NONE is specified.
It addresses an issue that causes an OS upgrade to stop responding, and then it fails.
It addresses an issue that affects the Microsoft Azure Active Directory (AAD) Application Proxy connector. It cannot retrieve a Kerberos ticket on behalf of the user. The error message is, “The handle specified is invalid (0x80090301).”
It addresses an issue that affects the font of three Chinese characters. When you format these characters as bold, the width size is wrong.
It addresses an issue that affects Microsoft Direct3D 9 games. The graphics hardware stops working if the hardware does not have a native Direct3D 9 driver.
It addresses graphical issues in games that use Microsoft D3D9 on some platforms.
It addresses an issue that affects Microsoft Edge when it is in IE Mode. The titles of pop-up windows and tabs are wrong.
It addresses an issue that affects Microsoft Edge IE mode. It stops you from opening webpages. This occurs when you enable Windows Defender Application Guard (WDAG) and you do not configure Network Isolation policies.
It addresses an issue that might cause an application to stop responding. This might occur when the input queue overflows.
It addresses an issue that affects input method editors (IME) from Microsoft and third parties. They stop working when you close the IME window. This occurs if the IME uses Windows Text Services Framework (TSF) 1.0.
It addresses an issue that affects the lasso tool in a graphics editing program.
It addresses an issue that affects Miracast advertisements. This issue occurs on Surface Hub devices under certain conditions.
It addresses an issue that affects some drivers. They use more power when you play hardware-protected digital rights management (DRM) content.
It addresses an issue that affects .msi files. Windows Defender Application Control (WDAC) will ignore them when you disable script enforcement.
It addresses an issue that affects a remote desktop virtual desktop infrastructure (VDI) scenario. The session might use the wrong time zone.
It updates the Windows kernel vulnerable driver blocklist that is in the DriverSiPolicy.p7b file. This update also ensures that the blocklist is the same across Windows 10 and Windows 11. For more information, see KB5020779.
It makes Microsoft compliant with US Government (USG) version 6 revision 1 (USGv6-r1).
It stops the start of daylight saving time in Jordan at the end of October 2022. The Jordan time zone will permanently shift to the UTC + 3 time zone.
既知の不具合
Symptoms | Workaround |
---|---|
Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone servicing stack update (SSU) released March 29, 2021 or later. Note Devices that connect directly to Windows Update to receive updates are not affected. This includes devices using Windows Update for Business. Any device connecting to Windows Update should always receive the latest versions of the SSU and latest cumulative update (LCU) without any extra steps. | To avoid this issue, be sure to first slipstream the SSU released March 29, 2021 or later into the custom offline media or ISO image before slipstreaming the LCU. To do this with the combined SSU and LCU packages now used for Windows 10, version 20H2 and Windows 10, version 2004, you will need to extract the SSU from the combined package. Use the following steps to extract the SSU:
If you have already encountered this issue by installing the OS using affected custom media, you can mitigate it by directly installing the new Microsoft Edge. If you need to broadly deploy the new Microsoft Edge for business, see Download and deploy Microsoft Edge for business. |
After installing this update, Microsoft OneDrive might unexpectedly close, and you might receive an error when attempting to do the following:
Note These issues might affect both OneDrive and OneDrive for Business. | We are working on a resolution and estimate a solution will be available in the coming week. |
After you install this or later updates, you might be unable to reconnect to Direct Access after temporarily losing network connectivity or transitioning between Wi-Fi networks or access points. Note This issue should not affect other remote access solutions such as VPN (sometimes called Remote Access Server or RAS) and Always On VPN (AOVPN). Windows devices used at home by consumers or devices in organizations which are not using Direct Access to remotely access the organization's network resources are not affected. | This issue is addressed in updates released December 13, 2022 (KB5021233) and later. We recommend you install the latest security update for your device. It contains important improvements and issue resolutions, including this one. If you install an update released December 13, 2022 (KB5021233) or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to address this issue. If you are using an update released before December 13, 2022, and have this issue, you can address it by installing and configuring the special Group Policy listed below. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> <Group Policy name listed below>. For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback. Group Policy downloads with Group Policy name:
Important You must install and configure the Group Policy for your version of Windows to resolve this issue. |