logo logo

The next-generation blog, news, and magazine theme for you to start sharing your stories today!

The Blogzine

Save on Premium Membership

Get the insights report trusted by experts around the globe. Become a Member Today!

View pricing plans

New York, USA (HQ)

750 Sing Sing Rd, Horseheads, NY, 14845

Call: 469-537-2410 (Toll-free)

hello@blogzine.com

Microsoft confirms speech recognition issues in Windows 11 22H2

avatar
Louis Ferguson

An editor at Blogzine


  • šŸ•‘ 1 minute read
  • 2 Views
Microsoft confirms speech recognition issues in Windows 11 22H2
A red Windows logo next to a dead emoji indicating a security flaw in the operating system

Microsoft has updated its Windows Health Dashboard documentation with details about a newly discovered bug. According to the company, Windows 11 version 22H2 users might experience problems with speech recognition, expressive input, and handwriting after installing KB5022913 (and subsequent releases). Affected systems fail to recognize words or detect input in various applications.

Microsoft says the problem appears on PCs running client Windows 11 version 22H2 edition with Chinese and Japanese languages and apps using Windows.Media.SpeechRecognition API. Other speech recognition implementations, APIs, and Windows versions are unaffected.

The company is working on resolving the issue in future updates. Meanwhile, customers can mitigate the problem by doing the following after every device restart:

  1. Close the app which is having issues with speech recognition or other affected input types.
  2. Open Task Manager by selecting the Start button and type ā€œtask managerā€and select it.
  3. Select the ā€œProcessesā€tab on the left and then select the ā€œNameā€column so that the list of processes is sorted by their names.
  4. Find ctfrmon.exe and select it.
  5. Select the ā€œEnd Taskā€button.
  6. Confirm a new instance of ctfmon.exe is started automatically.
  7. You should now be able to open the affected app and use speech recognition and other input types.

You can learn more information about the bug in the documentation.



Leave a Reply

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