[Windows10] WindowsUpdate February 2022 February Bug Information -Security Update KB5010342 [Update 5]

▼ Highlights of updates ・ Corrected vulnerabilities and problems

Windows 10 versions 21H2 / 21H1 / 20H2 / 2004 If you use a new Japanese IME installed, the Roman letters / Kana input mode may not be automatically switched in the application.

Developer information: If the application uses the ImmsetConversionStatus function or the VK_KANA key, it is affected by this problem.

Please consider how to deal with one of the following.

manually change the input mode.

Use the previous version of IME.Enter "Settings" in "Settings" → "Setting Japanese IME" and open "Japanese IME settings" → "General" → "Use the previous version of Microsoft IME" at the bottom.You can avoid this bug by changing to on.

Some half -width katakana and full -width katakana characters with a cloudy point or semi -cloudy point are not interpreted as the same character.When comparing the norm_ignoreWidth flag by specifying the comparestringex () function, these characters are evaluated as different sort rules.This bug affects all updates on Windows 10 versions 21H2 / 21H1 / 20H2 / 2004 after June 10, 2020.

Open the command prompt (administrator) and enter and execute the following command.

The above command is a command to rewrite the registry data.If you restart your PC, the sort rules will return to 1909 and no problems.

However, this workaround must be performed only in an environment where KB4586853 or later, which is released on December 1, 2020, is applied.If KB4586853 is done in an environment where it is not applied, the PC may not start.

Also, be aware that Microsoft does not guide you to the original back.

According to this environment, the original data was "00060305" for both 21H1 / 20H2 / 2004, so if you execute the following, you should return to the original.

The data may vary depending on the environment, so open "HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ nls \ Sorting \ Sorting \ Versions" in the registry editor to confirm the data before "(default)".We recommend that you keep it.

If you are not sure about the above contents, or if you are not in trouble with this problem, we do not recommend implementing this workaround.We recommend that you wait for it to be fixed.

In an environment where Windows10 is installed from custom offline media or custom ISO images, even if Microsoft Edge Legacy is deleted by this update, it may not be automatically replaced with a new Microsoft Edge.

This bug is that the custom -off media or ISO image slips the update of this update in the image without first installing a standalone service stack update (SSU) released after March 29, 2021.It occurs only when created.

The device that connects directly to WindowsUpdate and receives an update is not affected.This includes the device that uses Windows Update for Business.

To avoid this bug, the Custom -O -off Media or ISO of the standalone service stack update (SSU) released after March 29, 2021, before slipstream the latest cumulative update (LCU).Slip stream to the image.

1.Extract CAB from MSU with the following command.(Example at KB5000842)

2.Extract SSU from Cab with the following command.

3.This is the SSU CAB "SSU-19041.903-X64.CAB is created.Slip stream of this file first and then put the LCU.

If this bug occurs when you install the OS using a custom media, you can deal with this problem by directly downloading and manually installing a new Microsoft Edge.If you need to expand the new Microsoft Edge for Business widespread, see Download and deploy Microsoft Edge for Business.

July 7 (KB5004945) in some environments in which the Windows 10 version 21H1 / 20H2 / 2004 preview release KB5003214 released on May 26, 2021 and the preview release KB5003690 released on June 22, 2021Subsequent updates may not be installed.At that time, an error message "psfx_e_matching_biny_missing" is displayed.

According to Microsoft, even if left alone, the "Windows Update Medic Service" (WaasmedicsVC) service will be automatically repaired by an in -place upgrade.

If you want to solve the problem earlier, follow the steps below.

With this, an in -place upgrade is performed within up to 48 hours, and the latest security update programs are also applied at the same time.

In the ARM environment, KB5005932 is required separately.Please see here for the detail.

Installing the preview release KB5005611 or later on October 1, 2021 may fail the connection with a smart card authentication when connecting to an unreliable domain PC with a remote desktop.

At that time, "Your qualification information did not work. The qualification information used to connect to [Device name] did not work. Please enter a new qualification information."

Microsoft states that this bug is to fix using Known Issue Rollback (KIR / function that allows you to roll back only the problem without uninstalling the updated program), and is a general PC environment, companies and companies.In the case of a PC environment that is not managed by the organization, it is automatically corrected within up to 24 hours even if left alone.If you restart your PC, it may be corrected quickly.

PCs managed by companies and organizations can be solved by installing and setting the following special group policies:

・ For Windows10 21H2 / 21H1 / 20H2 / 2004 ・ For Windows Server 2022

For more information, see "How to deploy a known problem rollback using a group policy".After setting the group policy, you need to restart your PC.

"Settings" → "Update and Security" → "Recovery" → "Return this PC to the initial state" → Press "Start" to open the "Reset this PC" window, and select "Delete all".The file may not be deleted.

To avoid this bug, sign out from oneDrive or remove the link before returning Windows to the initial state.For a detailed procedure, see the page "Turn off or disable or uninstall ONEDRIVE".

In the environment that has already been returned to the initial state, Windows.Deleting the OLD folder can also reduce this effect.Please see this page (English page. Japanese page is incorrect with machine translation).

Microsoft is working on a problem solving and plans to revise future updates.

[NEW]

In some environments paired with Bluetooth devices, blue screen errors may occur.This bug occurs only when a specific configuration service provider (CONFIGURATION Service Provider (CSP)) is set up.Such a policy may be used by companies and organizations, but it is unlikely that individual users and personal PCs will be affected.

This bug occurs in one of the following scenarios.

This bug occurs in an environment where the preview release KB5009596 or later released on January 26, 2022 is installed.

This bug can be avoided in one of the following ways.

▼ How to deal with the registry method You can avoid problems by editing the following registry before installing the update.

If you have already installed an update program and a blue screen error occurs during the device restart, open Windows in Safeos mode and add a registry entry.

▼ How to deal with KIR This bug is modified using Known Issu Rollback (a function that can roll back only the part of the problem without uninstalling the KIR / updated program).However, KIR is not expanded (distributed) automatically.

If your environment is affected, install a manually special group policy and do the following steps:

For more information, see "How to deploy a known problem rollback using a group policy" (Japanese pages are unknown in machine translation. Click here for English pages).

In some environments, it has been reported that after installing the KB5010342, the phenomenon that the program does not start no matter what you click.

Restart in safe mode and uninstall KB5010342.This will start up normally.

After that, if you disable "sysMain" from the service and install KB5010342 again, you can apply without any problems.