Windows 11 24H2 voice typing not working? Fix it

Win+H opens, nothing lands. You're not imagining it.

If the panel appears but no words show up, and there's no little sound-level animation while you talk, that's the signature 24H2 failure. The mic test in Settings passes. Dictation in some apps might even half-work. But Win+H specifically does nothing. Users on Microsoft's forums report this started right after the 24H2 upgrade, with the speech runtime either reset or never provisioned.

I'll say the unglamorous part out loud: I've spent an embarrassing amount of my life staring at a UI that opened correctly and then did absolutely nothing, waiting for it to confess what's wrong. It never does. With 24H2 voice typing, what moved is almost always one of three things — a toggle, a language pack, or the speech runtime itself. We'll check them in that order.

What 24H2 actually changed under the hood

24H2 is a full operating-system version, not a small patch. It re-lays system components, and a feature update that size can reset a privacy toggle, drop a microphone permission, or leave a speech language resource half-installed. The online speech recognition setting is documented: it lives at Settings > Privacy & security > Speech, and when it's off, only device-based features stay available — cloud-based recognition stops working. Voice typing leans on that cloud recognition. If the toggle came back off after the update, Win+H has nothing to talk to.

Two caveats, because I'd rather be honest than tidy. First, the toggle's existence and effect are documented; the claim that a 24H2 update can flip it back off is community-reported, not in a published Microsoft note. Second, some 24H2 machines show a deeper problem — the speech runtime was never properly provisioned, so the folder Windows keeps it in sits empty. The toggle and language-pack fixes won't touch that case. Start with the cheap checks anyway; they catch most people.

Start here: turn online speech recognition back on

Open Settings > Privacy & security > Speech. Find Online speech recognition and make sure it's set to On. With it off, Windows only offers device-based speech features, and Win+H — which uses the cloud Azure Speech path — has nowhere to send your audio. Flip it on, confirm you actually have an internet connection, put your cursor in a text box, and try Win+H again.

This is the 30-second check, and it's first for a reason: a reset toggle is the single most common way 24H2 leaves voice typing dead while everything else looks fine. While you're in there, glance at your microphone permission — feature updates have a habit of revoking app access to the mic, and a revoked permission produces the same blank-panel symptom. If the toggle was already on and the mic already had access, move on. The next step is where the 24H2-specific stuff starts.

Next, reinstall the speech language pack

Voice typing needs the speech features for your display language, and 24H2 can leave those resources missing or stranded. Reinstall them. Go to Settings > Time & language > Language & region, select the ellipsis next to your current Windows display language, and choose Language options. Under Language features you'll see Text-to-speech, Basic speech recognition, and Enhanced speech recognition. Make sure they're installed — re-download any that show as missing. Restart, then test Win+H.

One honest heads-up from Microsoft's own documentation: not all languages have speech features. If Text-to-speech and the speech recognition options simply aren't offered for your language, that language doesn't support them. That's not a 24H2 bug — that's a coverage gap. Users on Microsoft's forums also report that a 24H2 build broke dictation for at least one non-English language while English kept working; if that matches you, reinstall the language pack and then install a later cumulative update, with a roll-back to the previous build as the community's stopgap. I'm not naming a specific update as the culprit, because Microsoft hasn't confirmed one.

If the runtime itself is gone, run Microsoft's in-place repair

This is the case where the cheap fixes don't bite. The toggle's on, the language pack's reinstalled, the mic works — and Win+H still does nothing. Users on Microsoft's forums describe 24H2 machines where the speech runtime was never provisioned, so the folder it lives in sits empty and the incremental fixes just fail. People reach for DISM to rip the speech packages out and re-add them, and on 24H2 that command often dies with a 0x800f0825 error because the enhanced-speech packages are protected as Features on Demand. I'd skip that fight.

The supported route is Microsoft's official in-place repair: it reinstalls the same version of Windows already on your PC, preserves your apps, files, and settings, and repairs system files and components. Microsoft recommends exactly this when something fails because of problems with system files or components. It's the closest thing to "reset the broken parts and keep everything else." It takes a while and asks for patience, but it brings the speech runtime back without a clean install and without you learning more about DISM than you ever wanted to. Run it, restart, and Win+H should have something to talk to again.

Install the latest cumulative update before you assume it's broken

Before the in-place repair, or right after it, check for and install the latest cumulative update. Microsoft has kept patching voice typing in later 24H2 and 25H2 updates — a 2026 cumulative update, for example, improved how a dictation setting persists. The point isn't any single patch. It's that "voice typing is broken on my build" sometimes means "my build is a few updates behind the one that fixed it." Go to Settings > Windows Update, install everything pending, restart, and test again. It's the laziest fix that sometimes just works, and laziness that works is still a fix.

The basics that aren't 24H2-specific

Some of what breaks voice typing has nothing to do with 24H2. The mic isn't selected as the default input. App access to the microphone got revoked. The audio driver needs a refresh after the update. The wrong input language is active. Those are real and worth a glance — but they're the general "any Windows update" playbook, not the 24H2 story, and re-running all six here would just pad the page.

So I won't. If your dictation went sideways right after some update and you can't pin it to the 24H2 jump, the steps are the same across versions, and I wrote them up in dictation not working after a Windows update. If voice typing has never worked on this PC, start with the broader voice-to-text not working on Windows checklist instead. Two more for the specific dead-ends: the online speech recognition toggle greyed out and Windows dictation stuck on "initializing".

The dictation that survives feature updates

Heads-up: this section is about Whisper by Remskill, the dictation app we build. The fixes above stand on their own — keep them. This is the option for when you're tired of the speech runtime moving every time Windows ships a major update.

Here's my one opinion in this piece, and I'll back it: if you're done re-provisioning a speech runtime every major Windows version, try local dictation first. Whisper's local mode runs entirely on your machine and works completely offline — after a one-time model download, transcription needs no internet and contacts no server. It doesn't ride on Windows' online speech toggle. The model is a file you downloaded; it isn't a Windows OS component, so a feature update can't reprovision it or leave its folder empty. There's no "missing speech runtime" failure mode to chase.

The trigger is its own global hotkey — Ctrl+Space by default on Windows, not Win+H. Press it, talk, release, and the text lands at your cursor in whatever app you're in. Local transcription is free at signup with no card required. If you dictate in another language, the multilingual models cover 90+ languages including auto-detect, and they can translate as you speak — say something in another language, get English text out. Built-in Windows voice typing doesn't do that.

When to skip Whisper and stay on Win+H

Be honest with yourself about what you actually need. If you dictate a 40-word text once a day, the in-place repair fixed Win+H, and you're back in business — stay there. Built-in voice typing is free, already installed, and for short bursts in English it's perfectly fine. You don't need a second app for the occasional sentence. Microsoft also ships Dictate inside Word and Outlook, which sometimes keeps working when Win+H doesn't, so that's another no-cost fallback for short writing. Reach for a dedicated tool only when the failure keeps coming back, when you need it offline, or when you dictate in a language built-in voice typing won't cover. That's the line. Below it, save your download.

Voice typing is one of those things you never think about until a Tuesday update eats it, and then it's all you can think about. Work the ladder — toggle, language pack, in-place repair, update — and Win+H comes back for most people. And if you're tired of doing this dance every major version, download Whisper and let dictation live somewhere a feature update can't reach. My younger one still thinks the computer is just listening to her. Some days I'd like that back.