Windows Dictation stuck on Initializing: the fix

Windows voice typing opens, says Initializing, and stays there. The microphone never goes live and nothing you say arrives.

A reboot clears it. So does ending one background process, which takes about ten seconds:

1. Open Task Manager with Ctrl + Shift + Esc.
2. On the Processes tab, find Microsoft Text Input Application. On the Details tab it is TextInputHost.exe.
3. Right-click it and choose End task.
4. Press Win + H again.

Windows restarts the process on its own the moment you ask for voice typing again, so there is nothing to put back and nothing to reinstall.

That fixes the common case, which is a wedged helper process. It does nothing for the second case, and the two look identical from the outside.

What Initializing is actually waiting for

This is the part worth knowing, and it is not obvious from anything on screen: Windows voice typing does not run on your computer. Microsoft's own requirements are that you "be connected to the internet, have a working microphone, and have your cursor in a text box" — because the recognition happens on their servers. It is online speech recognition wearing a local interface.

So "Initializing" is the word it shows while it is trying to reach a Microsoft service. It will sit there indefinitely if:

• the connection is down, or captive-portal'd at a hotel or an airport;
• a VPN or a corporate proxy is blocking the endpoint;
• online speech recognition is switched off, under Settings, Privacy & security, Speech. Off is a perfectly reasonable privacy choice and it disables voice typing entirely;
• Microsoft's service is having a bad afternoon, which is rare and does happen.

Ending the task cannot help with any of those. If Win+H hangs on a machine that has just come off wifi, that is the answer, and the ten-second fix above is the wrong tree.

The quick way to tell them apart

End the task once. If it works, it was the process. If it hangs again immediately, stop repeating it and check the connection and the Speech setting instead — a wedged process does not usually wedge twice in a row, and a missing service always will.

The other things that produce the same symptom

• Another application is holding the microphone. A conference call still running in the background will do it. Close it and try again.
• Microphone permission is off. Settings, Privacy & security, Microphone, and check that desktop apps are allowed.
• The cursor is not in a text box. Voice typing only opens against an editable field, so pressing Win+H on the desktop or in a menu gives you a panel with nowhere to type.
• The wrong input device is selected. Voice typing follows the system default, so a disconnected headset can leave it listening to nothing while still appearing to work.

Dictation or voice typing?

The same feature, renamed. Windows 10 calls it Dictation; Windows 11 calls it voice typing. Win+H opens it on both, and everything above applies to either. If you are following an older guide that says "Dictation" and your Settings app says "voice typing", you are in the right place.

Microsoft's community thread on this has a longer list of things to try if none of the above lands: dictation stops working and gets stuck on initializing.

This article was originally dictated rather than typed, with a broken wrist, which is how the fix came to be worth writing down: when typing is the thing you are avoiding, "just reboot" is an expensive answer.

One request for Microsoft, while I have the floor: a keyboard shortcut to toggle the microphone back on would save reaching for the mouse, which is the one thing voice typing is supposed to spare you.