The short answer
On the same PC and connection, check whether the same account’s conversations open in the browser. If the browser works, fully quit and reopen the app before preserving Cache. If both fail, check incidents and connectivity first. Screen color alone does not identify the cause.
Different symptom or still not fixed? Find the next check →Key facts
- Compare actual conversations
- A login screen or landing page alone is not enough
- Only the app fails
- Fully quit, restart, then compare preserved Cache if needed
- Both fail
- Check incidents and the same PC on another permitted connection
Find your symptom
Start with your symptom. Skip steps that do not apply to your setup.
| What you see | What to check | Go to |
|---|---|---|
| Logo stalls; browser conversations work | Does a complete app quit resolve it? | Step 2 |
| Gray screen; browser conversations work | Compare after a full quit, regardless of screen color. | Step 2 |
| Only the app still stalls after restart | Preserve Cache before comparing. | Step 4 |
| Neither app nor browser opens conversations | Check incidents, other sites and another connection. | Step 3 |
| App works; browser stalls | Compare a private window or another browser. | Step 1 |
| Update Failed or installation-corruption message | Record the exact message and use its specific guide. | Step 5 |
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｜Compare the same account in the browser
This tests a usable Discord session from the same connection, not the underlying reason for an app-only stall.
Time: Compare one change before continuing
- On the affected PC, open https://discord.com/app and, where possible, sign in to the same account as the desktop app. Verify the domain first.
- Check that the server/chat list loads and an existing conversation opens. A sign-in screen alone does not complete the comparison.
- If the browser works and only the app stalls, continue to Step 2. If both stall, continue to Step 3.
- If only the browser fails, compare a private window or another browser before inspecting extensions and stored site data. Keep sign-in access available before clearing anything.
If authentication prevents reaching conversations, mark the comparison unconfirmed. A gray screen or logo does not identify a particular cause.
Results that did not fix the problem help the next reader too.
Step 2｜If the browser works, fully quit the app
Remaining background processes can survive a closed window.
Time: Compare one change before continuing
- In the Windows notification area, expand hidden icons if needed and quit Discord from its icon. This disconnects any call or stream.
- Open Task Manager with Ctrl+Shift+Esc and end remaining identified Discord processes.
- Reopen once and check the chat list. If normal loading returns, stop making changes.
- If it still stalls, save work and restart Windows. If only the app remains affected afterward, continue to Step 4.
Results that did not fix the problem help the next reader too.
Step 3｜If both fail, check the service and connection
Resetting app Cache does not isolate a failure shared by the browser.
Time: Compare one change before continuing
- Check https://discordstatus.com/ for a relevant incident and wait for recovery if one matches. No posted incident does not rule out an unreported or local connection issue.
- Open another website in the same browser. If other sites fail, inspect the PC’s Wi-Fi/router/connection first.
- If available and permitted, compare the same PC on another connection such as your own hotspot. Consider data costs, then return to the original network. Success only elsewhere points toward the original connection or restrictions.
- If other sites work but Discord does not, check Windows Settings → Time & language → Date & time for automatic time, and inspect VPN/proxy/firewall restrictions affecting Discord. Record existing settings and avoid changing multiple variables.
Do not bypass company/school restrictions or leave protection disabled. Ask the administrator about managed settings and restore any unhelpful personally controlled comparison.
Results that did not fix the problem help the next reader too.
Step 4｜If only the app stalls, preserve Cache
Use this after a full app quit and Windows restart have failed to help the app-only symptom.
Time: Compare one change before continuing
- Fully quit Discord as in Step 2 and confirm its processes are gone. Keep email/password and two-factor authentication available in case another sign-in is needed.
- Open Windows+R and enter %APPDATA%/discord. Record this path and the intended backup name.
- Rename only Cache to an unused name such as Cache_before_loading_fix. If it is absent, do not create it or delete a different folder.
- Reopen and inspect conversations. To undo an unhelpful result, quit again, keep the newly generated Cache separately and restore the old folder’s exact name without mixing or overwriting contents.
This does not reset every file outside Cache. Keep the original private until testing is complete and distinguish it from the entire Discord settings folder.
Results that did not fix the problem help the next reader too.
Step 5｜Follow explicit update or corruption errors
A named update/installation error needs its own comparison path.
Time: Compare one change before continuing
- Record the exact displayed error and time it appeared.
- For Update Failed, use the linked update-loop guide to compare update connectivity and processes.
- If installation corruption is explicitly reported, review Discord’s corrupt-installation instructions and the installer guide before reinstalling. Removing whole app-data folders is a different, wider operation than preserving Cache and requires sign-in preparation.
Results that did not fix the problem help the next reader too.
Avoid
- Do not infer a cause from screen color or a working login page.
- Do not delete the entire Discord folder as the first Cache test or disable network protection to bypass a restriction.
Important cautions
- If both clients still fail on another connection, retain the incident/login observations for support.
- If only the app fails, include Windows version, exact error and full-quit/Cache results. Mark unavailable comparisons as unconfirmed.
- Redact personal details in screenshots and keep preserved app data private.
FAQ
Do a logo screen and a gray screen need different fixes?
Their colors do not identify the cause. First compare actual browser conversations on the same PC. A browser-only success leads to app checks; failure in both leads to incident/connection checks.
Does the browser login screen prove the desktop app is broken?
No. Reach the server/chat list and a conversation before treating it as a successful session. If sign-in fails, record the authentication error and leave the comparison unconfirmed.
Will preserving Cache remove servers or messages?
This targets the Windows app’s Cache folder, not account or server/message deletion. Keep the preserved folder until testing finishes, and do not confuse it with the complete app-data directory.
Sources
English adaptation of the Japanese guide, retaining its comparison sequence, restoration and stopping conditions. Official Discord documentation was reviewed; the comparisons and log-reading examples are editorial guidance, not a claim of a reproduced fault or a guaranteed repair. These Windows instructions concern the standard desktop client.
Discord: general troubleshooting and Cache locationDiscord: stuck on the connecting screenDiscord: corrupt Windows installationDiscord Status: official service incidentsDiscordJapanese version of this page