Skip to content

Microsoft Online Voices seem to have become unresponsive again #123

Open

Description

@thislittlepiggie

Hi!
Thanks for the speed of release for the most recent update. That fixed the problems with the Ms Online Voices, but they seem to be back!

In the log file:
[error] Speak: (websocketpp.processor:20) Invalid HTTP status.
This only started this evening. They'd been running fine since the last update.

I know v.10 added the 2.0 authentication. Has something else changed with the server, perhaps?

Activity

  1. amirsol81 commented on Oct 24, 2026

    @amirsol81

    I can duplicate this. Online Edge voices no longer work with the latest update.

  2. 50rg0j commented on Oct 24, 2026

    @50rg0j

    Same here.

  3. HeraldCoupe commented on Oct 24, 2026

    @HeraldCoupe

    Same here unfortunately

  4. RM27199 commented on Oct 24, 2026

    @RM27199

    Same here

  5. mdonadel83 commented on Oct 24, 2026

    @mdonadel83

    same here

  6. pinned this issue on Oct 24, 2026
  7. gexgd0419 commented on Oct 24, 2026

    @gexgd0419
    Owner

    This issue has been reproduced.

    I didn't actually use the Sec-MS-GEC v2 algorithm in v0.2.10. I just changed the WSS URL, but now it seems to stop working.

    Time to work on actually implementing Sec-MS-GEC v2, I guess.

  8. Cavaliereeee commented on Oct 24, 2026

    @Cavaliereeee

    I'm using NaturalVoiceSAPIAdapter v0.2.10 with Balabolka on Windows 10.

    All online voices appear in Balabolka but produce no sound. Exporting speech also creates an empty audio file.

    The adapter log repeatedly shows:

    Speak: (websocketpp.processor:20) Invalid HTTP status.

    I've confirmed that:

    • Windows offline voices work normally.
    • Microsoft Edge Read Aloud works with Arabic online voices.
    • Microsoft's online voice-list endpoint returns JSON successfully.
    • The problem persists on both home internet and a mobile hotspot.
    • Microsoft Edge version: 155.0.4283.62 (64-bit).

    Is there a workaround or updated adapter configuration that restores online speech synthesis?

  9. mrendor12 commented on Oct 24, 2026

    @mrendor12

    For some reason everything works fine for me, even though I have the exact same setup as the person who posted above.

    Well, not exactly "everything works fine". As described in #118 , I too have glitches and clicks in the audio.

    Does anyone else have this problem? It doesn't seem to be related to my connection or system. Or are you using different voices? Not Ava or Emma, where it’s pretty noticeable.

    Although those electrical clicks seem to be in all the voices. It’s incredibly annoying, so it’s become impossible for me to use online voices.

  10. thislittlepiggie commented on Oct 24, 2026

    @thislittlepiggie
    Author

    Well, with the previous set of problems, there was a roll-out schedule across the world, so people in some locations didn't have the voices while others did. For me, I experienced the really-confusing situation of sometimes-they-work, sometimes-they-don't.
    I haven't been able to get the local voices working as a fall-back for the interim. But that's a different issue.

    gexgd0419 has identified the source of the most recent problems. Thanks for getting on to it, much appreciated.

  11. Myshor commented on Oct 24, 2026

    @Myshor

    Hey everyone! If you're stuck waiting for an official release, here is a quick workaround based on the community fork/PR:

    1. Grab the ZIP containing the unofficial replacement DLLs (for both x64 and x86 architectures) from the release page: dengxibo Releases.
    2. Close any running speech applications, back up your original .dll files, and simply replace them in the matching folders of your existing installation (reinstallation is normally unnecessary if already registered from the same folders).
    3. For more context, check out the fix implementation in PR Fix Edge online speech with Sec-MS-GEC v2 #121: Fix Edge online speech with Sec-MS-GEC v2 (#121).

    Works like a charm now! Hope this helps others while we wait for an official merged release. 🚀

  12. 50rg0j commented on Oct 24, 2026

    @50rg0j

    The fix worked, thanks!

  13. thislittlepiggie commented on Oct 24, 2026

    @thislittlepiggie
    Author

    Worked for me too! Many thanks!

  14. Cavaliereeee commented on Oct 25, 2026

    @Cavaliereeee

    Worked for me as well. Thanks a million!!!

  15. KiraKozo commented on Oct 26, 2026

    @KiraKozo

    @Myshor's solution worked for me, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions