Separate input failure from a game service problem
Closed Beta 02’s official announcement lists VOIP among systems being tested at scale. That means a silent channel may be a test issue, but it does not establish that every microphone problem is server-side.
Start by testing the microphone outside the game. If Windows cannot capture it, check the device connection, hardware mute, and selected input before changing WARDOGS settings. If the device works normally elsewhere, focus on permissions and the game’s audio configuration.
Check Windows access deliberately
Microsoft’s instructions for Windows 11 point to Settings, Privacy & security, and Microphone. Confirm microphone access, app access, and permission for desktop applications. Windows 10 places the equivalent controls under Privacy. You need access for the game, not every unrelated app on the computer.
Return to WARDOGS and verify which input is selected, which channel you are attempting to use, and the binding currently shown. Ask one teammate to confirm a short test instead of assuming a visible speaking icon proves delivery.
Capture a useful report
If the issue remains, note whether it affects one channel or all communication, whether it follows you between servers, and whether the same device still works outside the game. Include the approximate time and test build if displayed. Avoid registry edits, security bypasses, or unofficial voice patches: these checks are diagnostic steps, not a claimed universal fix.