But that’s not the only error that now appears in the documentation of known problems after the recent Windows updates. However, the second confirmed bug only affects input with multibyte character sets such as those used in Japanese, Korean and Chinese. However, end users are also affected by this.
We have translated the error descriptions for you. You will find the most important information about this at the end of this article.
No solution in sight
In both cases, users of the latest Windows version 22H2 (2022) are affected. Details can be found in the Windows Release Health Documentation. There, the Windows team explains that they are currently investigating the cause and that there is still no temporary solution. The Windows team is working on the fix and will provide an update as soon as possible. In some cases it could already help if you switch from an earlier version to newer patches.
Text conversion error description
When typing in languages that use multibyte character sets – such as Japanese, Korean, and Chinese – character conversion operations may not work correctly. Text conversion occurs when a series of characters is converted into different characters by a user selection. This usually results in additional windows for prediction and conversion candidates appearing near the cursor position as you type.
Symptoms observed may include:
- Wrong character range is automatically selected for conversion, resulting in unexpected options being displayed in the conversion candidates window.
- The cursor may move to an unexpected position, resulting in an incorrect string being selected for conversion. This can lead to Symptom 1.
Next steps: We are working on a solution and will provide an update in one of the next versions.
Affected platforms:
- client: Windows 11 version 22H2
- Server: None
Issues with deployment packages
When using provisioning packages on Windows 11, version 22H2, not all expected applications may be installed. The affected applications require elevated privileges to install (must be installed as Administrator) and may not have sufficient privileges to install during deployment. The provisioning packages are .PPKG files used to configure new devices for use on corporate or school networks. Deploying Windows devices with Windows Autopilot is not affected by this issue.
bypass: Any required applications that have not been installed can be installed after the deployment is complete.
Next steps: We are working on a solution and will provide an update in one of the next versions.
Important: If you are using deployment packages, we recommend installing updates released on November 29, 2022 or later before deploying devices to avoid the issue where Windows may be partially configured and the out-of-box Experience using deployment packages may not be completed.
Affected platforms:
- Client: Windows 11, version 22H2
- Servers: None
Windows 11 FAQ Instructions, tips and tricks
