Speech to text is not working

Question

Speech to text is not working

Mahesh Pratap Singh alias Yogi M. P. Singh 0

Subject: Azure Speech-to-Text (Speech Service) not working / recognition failing

Service affected: Azure AI Speech (Speech-to-Text / Speech SDK)

Issue summary: Speech-to-text transcription is not working as expected. [Choose the one that applies and delete the others:]

No transcription output is returned at all (empty/null result)
Requests fail with an error (see error details below)
Audio is submitted but recognition never completes / times out
Recognized text is inaccurate or garbled
Service was working previously and stopped working on [date]

Environment details:

Azure region: [e.g., East US, West Europe]
Speech resource name: [your resource name]
SDK / API used: [Speech SDK (language: C#/Python/JS/Java), REST API, or Speech Studio]
SDK version: [version number]
Platform: [Windows/Linux/macOS/mobile/web], OS version: [version]
Audio input source: [microphone, .wav file, streaming, phone call, etc.]
Audio format: [sample rate, channels, bit depth, e.g., 16kHz, mono, PCM WAV]
Language/locale configured: [e.g., en-US]Subject: Azure Speech-to-Text (Speech Service) not working / recognition failing Service affected: Azure AI Speech (Speech-to-Text / Speech SDK) Issue summary:
Speech-to-text transcription is not working as expected. [Choose the one that applies and delete the others:]
- No transcription output is returned at all (empty/null result)
- Requests fail with an error (see error details below)
- Audio is submitted but recognition never completes / times out
- Recognized text is inaccurate or garbled
- Service was working previously and stopped working on [date]
Environment details:
- Azure region: [e.g., East US, West Europe]
- Speech resource name: [your resource name]
- SDK / API used: [Speech SDK (language: C#/Python/JS/Java), REST API, or Speech Studio]
- SDK version: [version number]
- Platform: [Windows/Linux/macOS/mobile/web], OS version: [version]
- Audio input source: [microphone, .wav file, streaming, phone call, etc.]
- Audio format: [sample rate, channels, bit depth, e.g., 16kHz, mono, PCM WAV]
- Language/locale configured: [e.g., en-US]

0 comments

2 answers

Your answer

Answer 1

Amanda Zhu 160

You haven't filled out the entire troubleshooting template, so there isn’t enough information to identify a Speech service failure yet.

To narrow down your issue, I would make 2 checks:

Run the same input through the documented speech-to-text quickstart using the same Speech resource, region, and locale. This separates an application/audio-pipeline issue from resource configuration.
If the result is Canceled or recognition stalls, capture the cancellation details and enable Speech SDK logging. Include the SDK version, platform, audio format, region, and the exact ErrorCode/ErrorDetails in the question.

If this is long-running or streaming audio, also verify that the app is using continuous recognition rather than RecognizeOnceAsync, which is intended for a single utterance.

kiro_nox 0 Reputation points

2026-08-26T20:06:25.4533333+00:00
Hi Amanda,

I am not a developer, and I don't really understand the technical templates or SDK settings mentioned above. I am just a regular Windows user. I hadn't used the built-in Windows Voice Typing feature (wind+h) in quite a while, but today I needed it and realized it isn't working at all. After looking for answers online, I found this post because I am experiencing the exact same issue: my computer listens to my voice, but the text never appears, and it eventually times out. Even though the original post is from August 18th, and I highly doubt a service like this would stay down for that long, the fact is that it is definitely broken today.

To see if something was wrong with my internet, I did some basic checks, and I strongly believe the issue might actually be on Microsoft's end:

My SpeechRuntime.exe gets completely stuck trying to connect to the Microsoft network IP 150.171.29.10 (port: 443) .

When I try to open that server link in my web browser to check if it's online, your gateway blocks the connection with a "Service Unavailable" error page.

The page literally says: "Our services aren't available right now. We're working to restore all services as soon as possible. Please check back soon."

I am attaching a screenshot of this error screen.

I am sharing this simply to contribute and help the community out. I don't really need a reply back, as I just wanted to report the bug so your team is aware of it. Thanks!

Best regards.

Answer 2

Hi ˇMahesh Pratap Singh alias Yogi M. P. Singh ,

Thank you for sharing the additional details and your observations.

From your description, this appears to be different from an application-level Speech SDK issue. You mentioned that Windows Voice Typing (Win + H) is listening but never returns transcribed text, eventually timing out, and that you are seeing a service availability message when attempting related connectivity checks.

However, the information provided in this thread is not sufficient to confirm a service-side outage. To help determine whether the issue is related to the client device, network connectivity, or a backend service problem, could you please provide:

Your Windows version and build.
Whether the issue occurs on multiple networks (for example, home network vs. mobile hotspot).
Whether other cloud-powered Windows features are working normally.
A screenshot of the exact "Our services aren't available right now" message you referenced.

For developers using Azure Speech, a useful validation step is to run the official Speech-to-Text quickstart against the same Speech resource to determine whether the issue is specific to the application or affects the service more broadly.

If recognition requests are being cancelled or timing out, enabling Speech SDK logging and capturing the cancellation details can provide additional diagnostic information.

Thanks again for reporting what you're seeing. Additional details will help determine whether this is a local voice typing issue or a broader service connectivity problem.