Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Microsoft TTS provider is not registered at runtime on Windows 2026.4.5. /tts provider only shows OpenAI, and /tts status reports microsoft as not configured even though messages.tts.providers.microsoft is present in openclaw.json.

Steps to reproduce

1. Install or update OpenClaw to 2026.4.5 on Windows.
2. Set Microsoft as the TTS provider in openclaw.json under messages.tts and restart the gateway.
3. Run /tts status.
4. Run /tts provider.
5. Send an inbound voice message and let OpenClaw reply with TTS.

Expected behavior

Microsoft should appear as an available TTS provider in /tts provider, /tts status should show microsoft as configured, and replies should use the configured Microsoft voice such as zh-CN-XiaoxiaoNeural.

Actual behavior

/tts status shows: Provider: microsoft (not configured).
The last attempt shows microsoft: skipped(no_provider_registered).
/tts provider only lists OpenAI as available and does not list Microsoft at all.
As a result, TTS falls back to OpenAI voice instead of using the configured Microsoft voice.

OpenClaw version

2026.4.5

Operating system

Windows 11

Install method

No response

Model

ChatGPT-4.5

Provider / routing chain

Discord direct chat -> OpenClaw gateway (local) -> TTS runtime

Additional provider/model setup details

• openclaw doctor reports no plugin errors
• Plugins are loaded/imported successfully
• local install contains node-edge-tts
• openclaw.json contains only the microsoft TTS provider under messages.tts.providers
• restarting the gateway does not change the result

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response