[BUG]

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Title: Voice input fails with NotReadableError on RDP-redirected microphone (Windows desktop app)

Environment:

• Claude Desktop for Windows 1.26832.0 (MSIX), Windows 11 Pro 26200
• Machine accessed via RDP with audio recording redirection enabled

("Record from this computer"); the session exposes the standard
"Remote Audio" capture endpoint.

Symptom:

• Pressing the microphone button: in Home tab the mic icon turns red and

shakes; in Code tab it flashes red briefly. Voice input never starts.

• claude.ai-web.log shows on every attempt:

[VOICE_MODE] [VoiceSession] Failed to start:
{"errorCode":"device_error","technicalMessage":"Could not start audio
source","nativeErrorName":"DOMException","selectedMicId":"2122165793",
"error":{"name":"NotReadableError","message":"Could not start audio source"}}

Evidence it is app-specific, not environmental:

• Windows Sound Recorder records fine from the same "Remote Audio" device.
• Opera (Chromium) on the same machine in the same RDP session captures the

same device fine (getUserMedia works, waveform visible on mictests.com).

• Windows mic privacy permissions are granted for Claude.
• IMMDeviceEnumerator inside the session shows exactly one active capture

endpoint: "Remote Audio" {3.0.1.00000002}.{...} — so no device-selection
ambiguity; Claude simply fails to open the only device that exists.

Workarounds tried without success:

• Launching with --disable-features=AudioServiceSandbox
• Launching with --disable-features=AudioServiceOutOfProcess,AudioServiceSandbox
• VB-Audio Virtual Cable routing (dead end by design: RDP sessions expose

only the session-scoped Remote Audio endpoints to applications, so a
virtual device cannot be selected at all).

Expected: voice capture from an RDP-redirected microphone, matching the
behavior of other Chromium-based apps on the same machine.

Happy to provide full logs on request.

What Should Happen?

Voice input should start and capture audio from the RDP-redirected microphone ("Remote Audio"), the same way other Chromium-based apps (e.g. Opera) capture it on the same machine in the same RDP session.

Error Messages/Logs

[VOICE_MODE] [VoiceSession] Failed to start: {"errorCode":"device_error","technicalMessage":"Could not start audio source","nativeErrorName":"DOMException","selectedMicId":"2122165793","error":{"name":"NotReadableError","message":"Could not start audio source"}}

Steps to Reproduce

1. Connect to a Windows 11 machine over RDP with microphone redirection enabled ("Record from this computer"). The session exposes the standard "Remote Audio" capture device; Windows Sound Recorder records from it fine.
2. Launch the Claude desktop app inside the RDP session.
3. Open the Home tab and press the voice input (microphone) button.
4. The mic icon turns red and shakes; the voice session never starts. The log shows NotReadableError "Could not start audio source" (see Error Messages/Logs).
5. Same result in the Code tab: the mic button flashes red briefly and nothing happens.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.222 (Claude Code), Claude Desktop 1.26832.0

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_