Windows 10: Update KB5014666 causes issues with Input Indicator and Language Bar

Windows[German]With the preview update released at the end of June 2022 for Windows 10 20H2 to 21H2, there is an issue that the input indicator and language bar may no longer be displayed in the status area of the taskbar. Microsoft has confirmed the bug and is rolling back the fixes via Known Issues Rollback (KIR).


Advertising

Issues with input display and language bar

As of June 28, 2022, Microsoft released preview update KB5014666 for Windows 10 20H2 bis 21H2 (see Windows 10 Preview Update KB5014666 (June 28, 2022)), and also rolled out these fixes in the July 2022 cumulative update KB5015807 (see Patchday: Windows 10-Updates (July 12 2022)). After these updates an issue with the input display and the language bar in the notification area of the taskbar has occurred.

Microsoft has confirmed these issues in the Status Health Dashboard from Windows 10 21H2 (and earlier versions up to 20H2) and published the postInput Indicator and Language Bar might not appear in the notification area as of August 2, 2022. In addition, the support articles KB5014666 and KB5015807 were expanded in the English version in the Know Issues by an entry. The Windows status area states:

After installing updates released on June 28, 2022 (KB5014666) or later updates, the Input Indicator and Language Bar might not appear in the notification area. The notification area is normally located on the right end of the taskbar. Affected devices have more than one language installed. The Input Indicator and Language Bar is used to switch between input or keyboard languages on Windows devices and is used especially with languages that use Input Method Editors (IME).

The following operating systems may be affected:

  • Client: Windows 10 version 21H2; Windows 10 version 21H1; Windows 10 version 20H2.
  • Server: Windows Server Version 20H2

The input display is mainly relevant for Asian languages – the language bar is needed to switch between multiple languages (DE, EN).

Fix via Known Issues Rollback (KIR) back

Microsoft has fixed this issue with Known Issue Rollback (KIR), which means that the affected fixes are rolled back. On unmanaged end-user systems, this rollback is automatic, but can take up to 24 hours. Since the whole thing was triggered on August 2, 2022, the process should be complete. Restarting Windows can speed up the rollback a bit if necessary.


Advertising

For managed systems in enterprise environments where updates have caused the problems, administrator intervention is required. The following special group policy from Microsoft must be downloaded, installed and configured.

Download for Windows 10, version 21H2; Windows10, version 21H1; Windows 10, version 20H2KB5014666 220706_033027 Known Issue Rollback

The special Group Policy can be found under Computer Configuration -> Administrative Templates -> KIR Solution Name (here for KB5014666 220706_033027). For information about deploying and configuring this Group Policy, see How to use Group Policy to deploy a Known Issue Rollback. (via)

Similar articles
Windows 10 Preview Update KB5014666 (June 28, 2022)
Patchday: Windows 10-Updates (July 12 2022)
Patchday: Windows 11/Server 2022-Updates (July 12, 2022)
Microsoft July 2022 Patchday issues (Windows, Office)
Windows: Printer issues after July 2022 patchday and fixes
Windows print and scan error due to smart card authentication change


Advertising

This entry was posted in issue, Update, Windows and tagged , , . Bookmark the permalink.

One Response to Windows 10: Update KB5014666 causes issues with Input Indicator and Language Bar

  1. EP says:

    Microsoft now says this about the Input Indicator and Language Bar problem:

    "Resolution: This issue was resolved in updates released August 9, 2022 ( KB5016616) and later."

Leave a Reply

Your email address will not be published. Required fields are marked *

Note: Please note the rules for commenting on the blog (first comments and linked posts end up in moderation, I release them every few hours, I rigorously delete SEO posts/SPAM).