The short answer
Since March 2, 2026, Discord requires encryption-capable clients for voice/video conversations. Record the full version display, fully quit, update and check it again. If updating fails, compare the same call in a current supported browser and choose the next check from the actual error and call result.
Different symptom or still not fixed? Find the next check →Key facts
- Record the entire version
- Compare the same app and same settings field before/after
- Minimum is not current
- Use available current releases, not old installers at the minimum number
- Test a real conversation
- Loading text chat does not verify voice compatibility
Find your symptom
Start with your symptom. Skip steps that do not apply to your setup.
| What you see | What to check | Go to |
|---|---|---|
| Old-version warning or Windows client below 1.0.9164 | Record the version and fully quit/update. | Step 1 |
| The version seems unchanged after restart | Compare the full field, app variant and supported minimum. | Step 2 |
| Update Failed, a loop or Installation has failed | Try browser voice and follow the guide for that exact error. | Step 2 |
| App fails; updated browser voice works | Prioritize app updates, launch target and installation. | Step 4 |
| App voice works; browser fails | Inspect browser update/restart, site permission and exact error. | Step 3 |
| Both clients are supported but calls fail | Inspect incidents, RTC/No Route or channel permissions. | Step 4 |
| Call connects without audio, or only a bot fails | Separate audio devices from the bot provider’s compatibility. | Step 4 |
Fixes, in order
Continue this issue
Private notes stay in this browser. Nothing is sent automatically. Back up important notes on My Page. PC settings are never changed by this site.
Step 1｜Record the version, quit and update
The voice minimum lists Windows 1.0.9164, Firefox 142 and Chrome/Edge 86. These are voice compatibility floors, not current-release recommendations or every product’s full requirements.
Time: Compare one change at a time
- Open User Settings and scroll to the bottom of its panel. Record the entire version display, including multiple numbers rather than selecting an arbitrary part.
- Right-click Discord in Windows’ notification area and quit. If necessary, use Ctrl+Shift+Esc to check whether identified Discord processes remain.
- Open the intended Discord from Start and allow updates to finish. If Update Failed or another error appears, record it and use Step 2.
- Reopen the same settings field and record the new display. Join the same call and record any old-version warning, connection result and whether both people can hear each other.
DAVE is Discord’s audio/video encryption system. The recovery path is a supported client, not disabling encryption to retain an obsolete version.
Results that did not fix the problem help the next reader too.
Step 2｜For unchanged versions, inspect the app and update result
An unchanged number can already be current. A version below the requirement or a persistent warning is not a successful update.
Time: Compare one change at a time
- Compare the same app and field. If Stable, PTB or Canary coexist, record which one you updated and which one you launched.
- Select the intended Discord from Start instead of an old taskbar/desktop shortcut. Check the warning and version again after a PC restart.
- For Update Failed or a loop, use that guide’s app/browser/network comparisons. Do not begin by deleting AppData.
- If a fresh installer is needed, obtain Windows Discord from its official download page. Before reinstalling, preserve login/MFA access and record voice settings.
- For Installation has failed, use its dedicated guide. For unsupported OS or organization restrictions, inspect the stated condition and use a supported device or ask its administrator.
A current supported browser can be a temporary comparison, but it also needs a compatible OS. It is not a guaranteed workaround for unsupported hardware/software.
Results that did not fix the problem help the next reader too.
Step 3｜Update and restart the browser itself
Reloading Discord’s page does not update the browser.
Time: Compare one change at a time
- In Chrome, open More → Help → About Google Chrome. Record update/version state, relaunch if requested, then verify the same page again.
- For Firefox downloaded from Mozilla, use Help → About Firefox and finish the restart. A Microsoft Store installation updates through the Store. Check the resulting version, including the voice minimum of 142, and any error.
- In Edge, use Help and feedback → About Microsoft Edge, inspect update state and complete a required restart. If managed settings prevent this, ask the administrator.
- Leave the app call before opening https://discord.com/app in the browser. Join the same account/destination and inspect microphone permission for discord.com.
- Record cannot join, joins but no voice, or two-way conversation works. For browser-only silence, inspect site microphone permission and Discord input/output devices.
Example: an app old-version warning with a working browser call prioritizes app updating; both stuck on RTC Connecting prioritizes connection checks. These are decision examples, not device-test results.
Results that did not fix the problem help the next reader too.
Step 4｜Route the result to update, connection, audio or bot checks
A supported version does not make every remaining symptom an encryption problem.
Time: Compare one change at a time
- If browser voice alone works, use it temporarily and inspect the app’s update/launch errors in Step 2. This result does not rule out every possible network influence.
- If app voice alone works, revisit browser updating, restart and site permission. For a persistent unsupported-version warning, inspect OS compatibility too.
- If both show RTC Connecting or No Route, inspect Discord Status and the matching connection guide. For one channel only, ask its administrator to inspect Connect and Speak permissions.
- If connected but silent, inspect mute/deafen and Voice & Video input/output devices. Use the output guide when only incoming voices are missing.
- If people can talk and only a music bot fails, inspect the provider’s DAVE support and incidents. Reinstalling a user’s app cannot implement missing support in the bot.
Results that did not fix the problem help the next reader too.
Avoid
- Do not disable encryption, use unofficial clients or downgrade to a minimum-version installer.
- Do not delete app data or bypass managed update restrictions before identifying the stopping point.
Important cautions
- For support, record Windows version, full Discord version before/after, Stable/PTB variant, browser/version, same-call results and exact warning/time.
- The listed voice minima are distinct from broader system/browser requirements. Keep the device and browser current through their official update channels.
FAQ
Does an unchanged number prove the update failed?
No. It may already be current or you may be comparing different fields/variants. Compare the entire display with errors and actual call results.
Does opening chat prove the client supports calls?
No. Text and voice/video requirements differ. Confirm joining and two-way audio in the same call.
Should I install exactly the minimum version?
No. Use the current release available for a supported device. A compatibility floor is not a recommendation to install old software.
Can I call while the app update is broken?
Try official browser Discord on a supported, updated browser/OS. If it works, use it temporarily while fixing the app; otherwise follow the actual connection/permission error.
Sources
English adaptation preserving the Japanese article’s steps, diagnostic branches, precautions and official references. Numerical comparisons are illustrative, not measured results or universal thresholds. Record original settings and restore unhelpful changes.
Discord: minimum voice-client versions and DAVE requirementDiscord: general troubleshootingDiscord: official downloadsGoogle: updating ChromeMozilla: updating FirefoxMicrosoft: Edge update settingsDiscord Status: service incidentsDiscordJapanese version of this page