Troubleshooting
Win+H not working on Windows 11
Windows voice typing leans on a cloud speech service, a microphone permission, and the right input language. When one of those is off, Win+H does nothing or errors out. Here is the fix, in order, plus an offline route that skips the whole handshake.
Last updated: June 2026

Win+H usually fails because Windows voice typing needs three things at once: an internet connection, microphone permission, and a supported input language. Turn on online speech recognition, allow microphone access, and confirm the language, then retry. A dedicated offline dictation tool sidesteps the whole cloud handshake by never depending on those toggles.
Win+H is supposed to be the easy one. You put your cursor in a text box, press the Windows key and H together, and a little voice typing bar drops in so you can talk instead of type. Most days it works. Then one morning you press it, nothing happens, and you start wondering whether you imagined the whole feature. You did not. It is still there. Something underneath it just went quiet.
The frustrating part is that Win+H failing silently tells you almost nothing. No error half the time, just a shortcut that does nothing. So people reinstall Windows, poke at the registry, or assume their PC is broken. None of that is usually needed. Voice typing depends on a short list of things being switched on, and when the shortcut dies, one of them slipped. Below is that list, checked in the order that fixes the most people fastest.
Here is the part Microsoft's own help page states plainly and most blog posts skip. To use voice typing you need three things at the same time: an internet connection, a working microphone, and your cursor in a text box. Win+H is not a local dictation engine. It is a button that hands your audio to a Microsoft cloud speech service and waits for text back.
So when Win+H does nothing, you are really debugging that chain — is the cloud service allowed to run, can it hear your mic, does it know your language, and is the cursor somewhere it can type. I'll walk the fast fix that solves it for most people, then the deeper repair, then an offline tool that doesn't need the chain at all. Pick whichever matches how often you actually dictate.
Why Win+H stops working

Win+H is Windows voice typing, and it is a cloud feature wearing a local costume. Press the shortcut and Windows captures your microphone, ships the audio to Microsoft's online speech service, and pastes back the transcript. That design is why it fails in more ways than a button should. There are roughly six causes, and they cover almost every case.
The common ones, in rough order of how often they bite: online speech recognition is switched off in Privacy settings, so the service Win+H calls isn't allowed to run. Microphone permission is denied, system-wide or for the app you're typing into. The input language is set to one voice typing doesn't support in your region. There's no internet, and Win+H needs the cloud to function at all. Another app has grabbed the Win+H shortcut for itself. Or the text input process that draws the voice typing bar has gotten into a bad state and needs a restart.
Two of those deserve a flag. The internet requirement surprises people — you'd assume dictation runs on your own machine, and it doesn't. And the hijacked-shortcut one is sneaky, because some clipboard managers, macro tools, and even a few work apps bind Win+H without telling you. If a tool you installed last week is the moment Win+H died, that tool is the suspect. The rest of this guide fixes each cause, then shows the route that has none of them.
The fast fix that clears most Win+H failures
Most dead-Win+H cases come down to three switches, and checking them takes about two minutes. Do them in this order, retrying Win+H after each, and stop when it comes back. These paths are Microsoft's own, taken from the Windows voice typing help page.
Walk it in sequence:
- Turn on online speech recognition. Open Settings, go to Privacy & security, then Speech, and switch online speech recognition on. Win+H routes through this service, so if it's off the shortcut has nothing to talk to.
- Allow microphone access. Settings, Privacy & security, Microphone. Make sure microphone access is on, and that desktop apps are allowed to use it. A denied mic is the second most common silent failure.
- Pick the right microphone. Settings, System, Sound, Input, and choose the mic you actually speak into. If you just plugged in a headset, Windows may still be listening to a dead built-in mic.
- Confirm the language and your connection. Press Windows key + Spacebar to check the input language matches a voice typing language, and make sure you're online — Win+H won't work offline.
Run those four and Win+H is back for most people. The reason a separate tool can feel more reliable is that none of these toggles are in its path. The overlay above belongs to Whisper, which records locally and pastes at your cursor without an online speech setting to forget, a privacy switch to flip, or an internet requirement to satisfy. Same gesture — press, talk, release — minus the four-step checklist when it breaks.
The permanent fix: dictation that never needs Win+H
If you'd rather stop re-checking Windows toggles every few months, the durable answer is a dictation tool that doesn't depend on them. You need a Windows 10-or-newer PC, a working microphone, and a free account. The whole local pipeline runs on your machine with no payment method asked for at sign-up. Here's the sequence.
Step 1 — Install Whisper and sign in.
Download from the download page, install, and create a free account. No card. The local transcription pipeline opens right away, with no online speech service to enable first.
You'll know it worked when the app's tray icon appears and the setup wizard offers to pick a model.
Step 2 — Pick a transcription path.
The app doesn't choose for you. You get three: Cloud (OpenAI, bring your own key), Local Parakeet, or Local Whisper. To avoid the cloud dependency that breaks Win+H, start local — more on which one two sections down.
You'll know it worked when a model finishes downloading and shows as ready.
Step 3 — Confirm your hotkey.
Windows defaults to Ctrl+Space, held as push-to-talk. It's a dedicated hotkey, not Win+H, so nothing that hijacked Win+H can touch it. If it clashes with something you use, change it in Settings.
You'll know it worked when a test recording pastes into any text field.
Step 4 — Put your cursor anywhere and talk.
Click into any text box — email, document, search bar — hold the hotkey, say a sentence, release. The transcript appears at the cursor, no internet required for local mode.
You'll know it worked when your spoken sentence is sitting in the text field as text.
The slow part is the one-time model download, not the setup. Once it's running, dictation stops being a thing that depends on a cloud service staying reachable and a shortcut staying unclaimed. It's a key you hold and words that appear. If you've ever fought voice to text not working on Windows, this is the version of dictation with fewer moving parts to fail.
If you'd rather repair the built-in one
Maybe you want Win+H itself fixed, not replaced. Fair. If the fast fix didn't do it, here's the deeper pass, still from Microsoft's documented steps so you're not editing anything you shouldn't. Start with the microphone, because a mic that's allowed in Privacy settings can still be muted, mis-leveled, or the wrong default device. Run the audio input troubleshooter from Windows settings, and test the mic in Sound settings to confirm the level meter moves when you talk. No movement there means voice typing has nothing to hear regardless of every other setting.
Next, the language. Win+H only works in languages it supports, and the supported set varies by region. Press Windows key + Spacebar to see your installed input languages and switch to a supported one; if the language you want isn't there, add its language pack from Settings under Time & language, then Language & region. After adding a pack, give Windows a minute to finish downloading the speech components before retrying. A half-installed language pack is a classic reason Win+H opens but never types.
If the toggles, mic, and language all check out and Win+H still does nothing, two things are left that don't require touching the registry. First, suspect a shortcut conflict: if a recently installed app — a clipboard manager, a macro or hotkey utility, a meeting tool — bound Win+H, quit or uninstall it and test again. Second, the Text Input Application — the background process that draws the voice typing bar — can get into a bad state. The safest reset is to sign out of Windows and back in, or just restart the PC, which restarts that process cleanly without you hunting for it in Task Manager. I'd stop there. A reinstall or a registry edit is almost never what fixes Win+H, and it's a lot of risk for a dictation shortcut.
Local or cloud: which mode to pick
If you go the dedicated-tool route to dodge the Win+H cloud dependency, lean local. The whole reason Win+H frustrated you is that it needs an online service to be reachable and switched on. Local modes don't — they run on your own machine, online or off. If your PC is from the last few years, local handles everyday dictation fine, and cloud becomes an option rather than a requirement. Here's how the three paths the app makes you choose between differ, because picking well matters.
The three paths, plainly:
- Local Parakeet — NVIDIA's TDT engine, around 600 MB, and the fastest local option — 5 to 10 times faster than Whisper on CPU. Covers English plus 24 other European languages, 25 in total. No translate-to-English. If you dictate in English or another European language, this is the quick, fully offline pick that never phones home.
- Local Whisper — slower than Parakeet on the same machine, but the multilingual builds cover 99 languages and can translate to English. The English-only builds are English-only, not 99. Pick this for Chinese, Japanese, Korean, or any translation work, which Parakeet can't do. Default English model is around 480 MB. Still fully offline.
- Cloud (OpenAI, BYOK) — best accuracy and web access, using your own OpenAI key billed straight by OpenAI. Transcription runs on gpt-4o-mini-transcribe by default. Needs internet, like Win+H does — so if cloud dependence is exactly what you're escaping, this isn't the path. The Cloud surface is part of Whisper Pro.
The boring truth is that for the text most people dictate — emails, notes, messages — local is plenty, and it's the path that actually solves the problem you came here with. Both local engines run entirely on your machine with nothing sent to a server. Cloud earns its place when you want top-tier accuracy on a hard recording or need the model to pull a fact off the web mid-sentence. Otherwise, start local and keep the cloud out of the loop.
Cleaner text once dictation works
Whichever route gets your dictation working, raw speech comes out as a run-on. You say "okay so reply to the landlord about the leak and tell him I'm free thursday," and that's the unpunctuated wall any speech engine hands you. What you do with that wall is where the tools differ.
Windows voice typing adds basic punctuation as you speak, which is fine for short bursts. For heavier cleanup — stripping the "ums," fixing the run-ons, turning a spoken paragraph into something you'd actually send — Whisper can run an AI pass. Say the activation phrase "Hey whisper" and the text gets enhanced before it lands. On a local model that runs through Ollama; in cloud mode it's gpt-5-mini by default.
okay so reply to the landlord about the leak and tell him im free thursday afternoon um any time after two
Okay, so reply to the landlord about the leak and tell him I'm free Thursday afternoon, any time after two.
Don't oversell what an AI pass does, though. It cleans filler and punctuation; it does not read your mind or invent structure you didn't say. Anyone promising dictation that formats your whole document on command is showing you a demo, not a Tuesday. Get the words down fast by voice, let the cleanup pass tidy them, and do the shaping you'd do anyway. The point is that you spoke instead of typed, and the gap between the two is where the time goes. This same speak-then-clean flow is how you type faster with voice in any app, not just when fixing a broken shortcut.
When the built-in one is enough

Sometimes Win+H was a one-off glitch, and once the fast fix brings it back, you don't need anything else. If you only dictate the occasional short message — a quick reply, a two-line note — Windows voice typing is free, built in, and does the job. I'm not going to tell you to install an app for a sentence you send twice a week.
Stick with Win+H when it works for you and you're fine with its terms: you're online when you dictate, your text is short, and you don't mind that the audio goes to Microsoft's servers to be transcribed. For a lot of people that's a perfectly good deal. If you've fixed it and it's behaving, there's a fuller walkthrough of getting the most out of voice to text on Windows and the general speech to text on Windows 11 setup.
Reach for a dedicated, offline tool when Win+H stops being convenient: long dictation, working without internet, privacy on sensitive text, or simply being done re-checking three toggles every time it breaks. That's the line. Below it, use what's free; above it, stop fighting the cloud handshake and run a hotkey that doesn't have one.
Win+H isn't broken so much as it's fragile — it depends on a cloud service, a permission, a language, and a shortcut nobody else claimed, and any one of those can quietly tip over. The fast fix brings it back most of the time. If you're tired of it tipping over, a local hotkey skips the whole chain. I dictated most of this guide with one, offline, on a train with no signal — which is roughly the situation that would have left Win+H staring back at me doing nothing.
Dictate without the Win+H checklist
Hold one hotkey, talk, release. The transcript lands at your cursor in any app — offline, with no cloud service to switch on first.
Free local mode for any signed-in account. No card required to start.



