Forum Discussion
Web Speech API stopped working on Edge starting with v.134
- Mar 13, 2025
Hi Everyone! The fix should now be available. Please test on the latest version of Microsoft Edge 134.0.3124.68. Microsoft Edge release notes for Stable Channel | Microsoft Learn
Thanks!
-Kelly
Hi Everyone! I just left a similar reply in the other thread but just to make sure I reach everyone, replying here as well. Our developers are investigating and need some additional information. If you are able, can you provide the following?
- Navigate to edge://metrics-internals/#variations and provide the values for SpeechNetworkStack and CFRSpeechServiceProtectECS experiments. It is possible you will not have these but if you do, it will look something like this:
"SpeechNetworkStack": { "enableFeatures": [ "msSpeechRecognitionChromiumNetworkStack" ] }, "CFRSpeechServiceProtectECS": { "enableFeatures": [ "msSpeechSynthesisServiceUseCetoService", "msSpeechRecognitionServiceUseCetoService" ] }, - After you see the failure, navigate toedge://histograms and provide the information under the following sections (they will all be right next to each other)
"Microsoft.SpeechRecognition.CancellationReason"
"Microsoft.SpeechRecognition.Error"
"Microsoft.SpeechRecognition.ErrorRate"
"Microsoft.SpeechRecognition.Event"
"Microsoft.SpeechRecognition.Method2"
"Microsoft.SpeechRecognition.SdkInstall"
"Microsoft.SpeechRecognition.WasRateLimited"
If you prefer, please feel free to send me a message with this information. Thanks!
-Kelly
Here is mine but it was in the Edge Canary latest release.
]
},
"SpeechNetworkStack": {
"enableFeatures": [
"msSpeechRecognitionChromiumNetworkStack"
]
},
"CFRSpeechServiceProtectECS": {
"enableFeatures": [
"msSpeechSynthesisServiceUseCetoService",
"msSpeechRecognitionServiceUseCetoService"
Histogram: Microsoft.SpeechRecognition.Event recorded 11 samples, mean = 0.8 (flags = 0x41) [edge://histograms/#Microsoft.SpeechRecognition.Event]
0 -----O (5 = 45.5%) 1 -----O (5 = 45.5%) {45.5%} 2 ... 4 -O (1 = 9.1%) {90.9%} 5 ...
Histogram: Microsoft.SpeechRecognition.Method2 recorded 11 samples, mean = 1.5 (flags = 0x41) [edge://histograms/#Microsoft.SpeechRecognition.Method2]
0 -----O (5 = 45.5%) 1 -O (1 = 9.1%) {45.5%} 2 O (0 = 0.0%) {54.5%} 3 -----O (5 = 45.5%) {54.5%} 4 O (0 = 0.0%) {100.0%}
Histogram: Microsoft.SpeechRecognition.SavedAudioLength recorded 5 samples, mean = 0.0 (flags = 0x41) [edge://histograms/#Microsoft.SpeechRecognition.SavedAudioLength]
0 -----O (5 = 100.0%) 1 ...
Histogram: Microsoft.SpeechRecognition.WasRateLimited recorded 5 samples, mean = 0.0 (flags = 0x41) [edge://histograms/#Microsoft.SpeechRecognition.WasRateLimited]
0 -----O (5 = 100.0%) 1 ...
Not sure if this helps at all but this is all I could find.
- Kelly_YMay 20, 2026
Microsoft
Thanks, mlmason75! I'll pass this along!
As just a quick update, our developer has been able to reproduce the issue and is continuing to investigate.
- mlmason75May 28, 2026Brass Contributor
Hello,
Any update on when the fix for this will make it into Edge?
Thanks
- Kelly_YMay 28, 2026
Microsoft
Hi mlmason75 - I just talked to our developer and the team is still investigating, so no ETA yet but will keep you posted. Thanks!
-Kelly