Discord Not Opening? Check Support, Status and These Fixes (2026)

By LK Wood IV · Published 2026-09-12 · Updated 2026-10-23 · St. Louis County, MO

What happens after you click Discord? Pick the matching symptom below. Check support and incident timing before deleting local state; those checks can change which repair is appropriate.

The Windows commands and paths in my test account were run or read on 2026-09-12. I did not reproduce a Starting or Connecting hang. The test details separate what happened on that install from the repair suggestions drawn from Discord’s guides and other people’s reports.

Which symptom you have

If Discord opens when you click it but no longer starts with Windows, check Windows Settings > Apps > Startup and Discord’s own startup choice under User Settings. That is a different symptom from a manual launch failure. On my machine it was absent from both the Settings list and the Windows startup-command list when I checked on 2026-09-12.

Check OS, client and feature support first

Support sources checked October 23, 2026. Check eligibility first. These published floors help choose the next branch; they cannot diagnose a failure or guarantee that the app will work.

Why Mac guides disagree. The general troubleshooting guide, updated June 11, 2025, still says macOS 11. The July 2026 requirements table says 12. The later, specific macOS 12 notice controls the continued-support question and the newer-client launch warning. An older installed client may retain basic function without guaranteed stability; the notice’s fallback does not update. Its exact build is unknown here. So is its current call eligibility.

macOS 11 support ended June 15, 2026. The earlier macOS 10.15 cutoff was January 21, 2025. Those later-edited pages still point toward 12; use the September notice for the newer target.

On Windows, 7/8/8.1 support ended March 15, 2024, while 32-bit OS support ended June 15, 2024. Possible old-client operation is separate from receiving supported updates.

Collect only the facts needed for your case:

• Windows: OS version/build and installed OS bitness from About. If you use ARM64, record that too; an ARM64 download link alone does not settle an unknown Windows release/client combination.
• Mac: Apple menu > About This Mac; click the version for the build. Do not copy the Windows folder paths below.
• Linux: read ID and VERSION_ID in /etc/os-release. Use /usr/lib/os-release only if the first file is absent, and do not merge them. VERSION_ID is optional; leave it unknown if absent. ID_LIKE is not proof of Discord support. These rules come from the os-release specification.
• Discord: record Stable, PTB or Canary and the version. If it opens, User Settings has client info at the bottom left. If it cannot open, write version unknown / cannot open; a browser version is not the installed desktop version.

A browser fallback has two requirements

Check both Discord’s browser floor and the browser vendor’s supported OS. Discord lists Chrome 108+, Firefox 142+, Opera 72+, Edge 86+ and Safari 15.4+. Its requirements page excludes mobile browsers and beta operating systems. Discord also excludes developer/alpha/nightly browser bugs from its standard reports. These support limits do not establish why a particular session failed.

For example, current Chrome requirements say macOS 13+. The captured Firefox 158.0.1 requirements say macOS 10.15+, making it a documented candidate for macOS 12 as of October 23. No Discord session or call was tested here. On Linux, Chrome’s Fedora floor is 39, even though Discord lists Fedora 32.

Do not install an obsolete browser to satisfy only Discord’s version number.

Use an existing browser observation, or check discord.com/app in an eligible browser. Record exactly what loaded. Include the browser version/channel and the time.

Reading an existing message establishes that narrow result in that session; it cannot certify the entire account, connection or service. Failure in both browser and desktop also leaves several explanations open. You do not need to send a message or place a call to fill out the case record.

Opening, text and calling are different results

Since March 2, 2026, Discord’s voice/video and Go Live requirements list desktop minima of Windows 1.0.9164, macOS 0.0.320 and Linux 0.0.69 for end-to-end encryption support. A client that opens and displays text can still fail this feature requirement.

A legacy Mac fallback with an unknown version has unknown call eligibility.

The voice page’s Chrome 86 minimum does not replace the general Chrome 108 floor. Underlying browser APIs and OS compatibility also matter. Passing the version check does not test a call. Keep those questions separate before using a voice incident to explain a launch problem.

The fixes, in the order I would run them

1. Kill every Discord process, then relaunch

This is the fix behind the most-upvoted answer in a 2017 r/discordapp thread titled “Discord Won’t Open,” which had 270 comments when I read it on 2026-09-12.

The top reply, at 116 points, is: “Press the windows key + r and type in cmd.exe, then type in taskkill /F /IM discord.exe and try to launch discord again.” My September 2026 process list below confirms multiple Discord.exe processes on that install; it does not measure how often this fixes a hang.

Here is what a running client looked like on my machine on 2026-09-12. With Discord 1.0.9257 open, Task Manager shows six separate Discord.exe processes and two DiscordSystemHelper.exe processes. When you close the window, the tray process stays.

The threads describe a process remaining without a usable window. Try closing it on a supported Windows install. A tray icon alone cannot establish the cause.

Open a command prompt and run this:

taskkill /F /IM Discord.exe

On my machine that printed six SUCCESS lines, one per process. Then launch Discord from the Start menu. It came back in about fifteen seconds and the process count returned to six.

Check whether the window appears. If a Discord.exe remains, read the command’s result rather than assuming it succeeded. An access-denied result is a reason to check permissions; the separate administrator-once branch explains the limited elevation step.

2. Read the status page before you touch anything else

Discord’s own status page lists each component, API through Client, with its state and a dated incident log. I read it on 2026-09-12 and it showed All Systems Operational, but the log underneath is the point.

As of that day its incident history listed four incidents in twelve days, each with its own page: Some servers and other services (voice calls, activities) not available for some users on August 31, Some Servers Unavailable on September 3, Issue with establishing voice calls on September 10, and Media Proxy Latency High on September 11.

That history does not show that every failure on those dates was an outage. In the January 2026 thread “Help discord stuck at starting,” the poster had “tried everything on yt” and reinstalled; the replies I read were other people reporting the same failure that day and asking whether Discord was down. Check the official timeline against your own observations. Same-day reports cannot establish your cause.

For your own case, open the incident for the feature and time you actually observed. The official API documentation distinguishes current/unresolved incidents from the 50 most recent incidents returned by its history endpoint. Neither a successful current request nor an empty unresolved list establishes a complete history for your time. If your failure falls outside the dates or components you reviewed, leave the result unknown.

Use this matching rule:

1. Name the failed feature. Starting, reading messages, joining voice and screen sharing are different observations. Read the incident narrative and affected component/region; do not assign a voice region from a general title.
2. Keep date, time and numeric UTC offset. Compare both sides in UTC, including a date rollover. Use the offset at the event, not your computer’s offset today. If either offset is unknown, the time comparison is unknown.
3. Check what the timestamps mean. Keep first/last observations separate from a continuously observed failure interval. An incident’s published, started, updated and resolved timestamps are not interchangeable measurements of physical outage onset/recovery. An ongoing report is known only through the time you checked it; an impossible or unexplained time sequence needs clarification.
4. Keep the result narrow. Relevant scope plus overlapping, understood intervals gives a possible incident explanation. A reviewed non-overlap means no matching published record in that reviewed scope. Missing history, component, region or usable time means unknown. None of those labels proves a PC fault, and a planned maintenance window is not evidence that disruption occurred.

For a real example of incomplete scope, the September 16 voice-connection incident and September 17 call incident had empty component lists and no affected-component detail in their captured updates. Their narratives remain leads; those empty fields cannot identify or exclude a specific voice region. The October 1 API incident, by contrast, named API and Media Proxy and displayed an investigating update at 12:48 PDT and resolution at 13:52 PDT. Those communication times do not measure the duration of impact on every user. Statuspage describes itself as a communication tool and permits backfilled incidents.

Worked timing examples

These are authored synthetic examples. They teach the comparison; they do not import Discord records or diagnose your failure. Unless a row gives another date/offset, all times are October 20, 2026 at UTC−05:00. The first two assume reviewed voice scope and history, a noon all-clear, and a reported voice interval of 09:00–10:00. Each exact example includes its interval start and excludes its end.

A repeated 01:30 needs the event’s offset. On November 1, 2026, 01:30 at UTC−05:00 is 06:30 UTC; at UTC−06:00 it is 07:30 UTC. Keep a missing offset unknown. One failure timestamp does not establish a duration. A rounded resolution minute touching that timestamp is also too imprecise for an exact boundary decision. The first and last failed attempts do not prove failure continued between them.

If you found an applicable active incident, follow its updates before deleting local state. If you did not, retain any missing scope and proceed to the applicable local branch cautiously. A relevant candidate can coexist with incomplete history; do not discard the unknowns just because one record matches.

Save a local case record

Copy this into a text editor, or download the plain-text case record.

Fill it from existing observations and public records. Leave unknowns visible; no new call, message, purchase, install or reset is needed. If you later share it, remove account details and private log content first.

DISCORD LAUNCH CASE RECORD
Checked: 2026-10-23
Blank template, not a result.
Unknown is a valid entry.

OS name/version/build:
  unknown
Installed OS bitness:
  unknown / not applicable
CPU architecture:
  unknown
Desktop client/channel:
  unknown
Desktop version:
  unknown / cannot open
Exact symptom or feature:
  unknown
Exact error text:
  none recorded
Steps tried and their result:
  not recorded
Existing logs kept elsewhere:
  none / unavailable

Failure date and time:
  unknown
UTC offset at that event:
  unknown
Observation precision:
  unknown
Single time or interval?
  unknown
Other observed attempts:
  not recorded
Continuous failure observed?
  unknown

Browser name/version/channel:
  not checked
Browser OS eligibility:
  unknown
Feature/result/time/offset:
  not checked

Official incident URL:
  not checked
History checked at + offset:
  not checked
Dates/components reviewed:
  not checked
History gaps/fetch failure:
  unknown
Relevant component/region:
  unknown
Incident or planned work?
  unknown
Published start/end + offset:
  unknown
Timestamp labels/precision:
  unknown
Ongoing: observed through:
  unknown
Source relevance/limits:
  unknown

UTC comparison:
  unknown
Result and unresolved gaps:
  unknown
Next applicable branch:
  collect missing facts

Overlap is not cause proof.
No match does not prove
PC fault.
Keep planned work separate.
Remove private data to share.

3. Run it as administrator, once

Discord’s troubleshooting guide lists this second for loading-screen freezes, and the Microsoft Q&A answer to a May 2025 “update failed” report gives the reason: “This helps if Discord needs extra permissions to finish updating.” Right-click the Discord shortcut, choose Run as administrator, let it finish starting, then quit it from the tray and open it normally.

Once is enough. You do not want to leave it running elevated; the point is to let one update or one settings write complete.

The proof: it opens, and it keeps opening afterwards without the elevated launch.

4. Delete the three cache folders

Keep this cache-only step narrow. Close Discord first, and leave the other client files alone. Deleting the whole roaming discord folder is a broader reset that can require signing in again; read the consequences before choosing it.

Discord’s troubleshooting guide specifically names %appdata%/discord/Cache. My September test covered Cache, Code Cache and GPUCache. Press Win+R, type %appdata%\discord and press Enter to look for those three folders. On my install they hold 58 MB, 1.2 MB and 548 KB.

If those three folders are present, quit Discord fully (Fix 1), delete them, and launch again. Leave missing or differently named folders alone. I did exactly that at 22:34 on 2026-09-12: all three folders were back twenty seconds after the launch, with Cache already at 21 MB, and the client opened signed in.

The 2023 thread “Discord stuck at Starting,” at 492 comments when I read it, was started by someone deleting the broader folders every day: “I have to delete the folders in %appdata% and then launch it again to get it to work, which is rather annoying because I have to log back in again.” That is the poster’s experience. My narrower cache test did not reproduce or diagnose a hang.

Check whether your splash passes and the window opens. Cache regeneration alone cannot establish that the original failure is fixed, and my signed-in result is not a guarantee for another install.

5. Break the update loop

On the Windows install I inspected, Update.exe was the Squirrel launcher handing off to a versioned app folder under %localappdata%\Discord. Read the updater error before deciding this branch fits. The Starting label alone cannot identify a cause on every client or platform.

On my machine, the moment I launched the client on 2026-09-12 the updater log recorded “About to launch: app-1.0.9256\Discord.exe”, the client pulled an update in the background, and the next launch nineteen seconds later recorded app-1.0.9257 instead. The registry version string changed from 1.0.9256 to 1.0.9257 and the old folder was gone. A leftover app-1.0.9059 folder, dated June 9 on my machine, is still sitting beside it.

For update problems, Discord’s general guide says: “Force quit Discord from Task Manager/Activity Monitor” and “Delete Discord AppData folder (Windows) or Application Support folder (macOS)”, and under Windows Installation Errors: “Clear temporary files and previous installation remnants.” The guide does not say which AppData folder.

The May 2025 Microsoft Q&A answer points to %localappdata% and the Discord folder there, which is also where the registry’s InstallLocation string for Discord points on my machine. That was the basis for the installation-only attempt in the original article. The separate official installer-error and corrupt-installation guides specify both Discord subfolders. That broader procedure is in the full-reset section.

Before the optional installation-only attempt: check OS eligibility and save the observed updater error/version. Keep any relevant existing updater log outside the folder you remove. Removing %localappdata%\Discord removes that installation’s files. This narrower attempt leaves %appdata%\discord outside its deletion scope; it does not guarantee preservation of every effective preference. If you choose it, close the Discord processes, remove only the Discord subfolder under %localappdata%, and use the official installer for your supported platform.

The Q&A answer suggests deleting a folder named Update inside it first; on my install there is no such folder, only Update.exe, the app folders and a packages folder.

Do not substitute a guessed path when your layout differs.

Messages are stored by Discord; they do not live solely in a Windows AppData folder. This computer also has local client state. Discord’s account-data description includes account settings, and theme synchronization can span clients when enabled. Do not treat every preference as purely local.

On the September install, SquirrelSetup.log recorded the app folder launched. If the same log is present on yours, retain the relevant error or hand-off line and its time, then check whether the window opens. A missing log stays missing. Repeating a reset does not establish a diagnosis; use the support record and log guidance if installation still fails.

6. Stuck on “Connecting”: the network list

The list below comes from Discord’s “Stuck on the Main Connecting Screen” article as I read it on 2026-09-12. Check that your date and time are set automatically. Scan with Malwarebytes and restart. Make sure your firewall allows Discord. Then, in its words: “Windows: Control Panel -> Network and Internet -> Internet Options -> Connections -> Lan Settings - Uncheck ‘Use a Proxy’”. If none of that moves it, press Ctrl+Shift+I in the client and read the console for errors.

One number about that article changes how you should use it. As of 2026-09-12, 994 of 11,983 readers marked it helpful. That is about eight percent. Helpfulness votes cannot measure repair success or how common a cause is. Check processes and the applicable incident first, then use this branch for a Connecting symptom.

The proof: the client passes Connecting and loads your server list.

7. Grey or black window: hardware acceleration

If the window opens but never paints, Discord’s guide lists a third step for loading-screen freezes: “Disable hardware acceleration in User Settings > Advance.” That is quoted as written. The catch is that you need a working window to reach the setting, and I have no tested route to it without one.

If the window becomes usable, try the documented toggle. If it never does, that UI route is unavailable. My dated settings.json had no hardware-acceleration key. Deleting it or reinstalling does not establish that every effective setting returns to defaults, especially where account preferences can synchronize.

The proof: the window paints and stays painted after a relaunch.

8. It passes “Starting” and then closes itself (September 2026)

Compare your version and log with this dated case. The build and outcome below belong to that September report. On September 11, 2026 an r/discordapp thread titled “Discord crashes on launch (no error in Event Viewer) - only on one user profile, works fine on another” described Stable 1.0.9257 on Windows 11 getting past the loading screen and closing before the home page, with a full reinstall, cleared AppData folders, a renamed settings.json and a clean boot all failing.

Run from a command prompt, the client’s own log ended with “Initializing voice engine with audio subsystem: experimental” and then a renderer crash with exit code -1073740791. Two other posters on 1.0.9257, one of them on Windows 11 build 26200, reported the identical log lines within a day, and two of the three had a second Windows account on the same PC where Discord worked.

A Discord staff member replied in the thread asking for minidumps from the Crashpad folder under %appdata% and then pointed everyone at the PTB build: “Can you try our PTB build it might have a fix already for this.” The original poster’s follow-up: “PTB fixed it!” One of the posters had PTB running normally on the same PC beside the broken Stable install.

Discord’s testing-client guide identifies Stable as standard, PTB as beta and Canary as alpha. That historical report does not promise today’s PTB will fix the same symptom or bypass OS requirements.

The installer link the staff member gave is discord.com/api/downloads/distributions/app/installers/latest?channel=ptb&platform=win&arch=x64, which redirected to a DiscordPTBSetup installer when I checked it on 2026-09-12.

For what it is worth, my own install went to 1.0.9257 during this page’s testing, its settings.json also selects the experimental audio subsystem, and it opened normally.

The differing Windows-profile results remain a lead. They do not prove the cause. Preserve the version and channel alongside the exact error before considering a supported test client or contacting Discord. The September installer-link check did not verify a current binary or a Mac/Linux delivery channel; use the maintained official testing-client guide for those choices.

For the Windows install layout described here, run Discord.exe from a command prompt inside its app folder under %localappdata% if you need to compare the launch output. Record the exact error and version; do not presume the September code must appear. The staff request above concerned Crashpad minidumps, which should go through the official support route if requested. Keep private logs out of public pastes. Discord lists simultaneous Stable/PTB/Canary instances as an unsupported bug-report topic; that reporting limit does not erase the historical coexistence observation.

Keep useful errors before another reset

If the installer still fails, Discord’s installer-error guide sends the case to Support. Keep the exact installer/error text and what you already tried. The case record adds the OS/channel and relevant incident comparison without requiring a full private system report.

Discord’s current bug-report guide documents Windows debug logs at C:\Users\<username>\AppData\Roaming\discord\logs. If the folder or relevant log is missing, record that. Before deleting its roaming discord parent folder, keep any relevant existing logs separately; otherwise the cleanup would remove them too.

This debug-log path is separate from the dated Squirrel updater and Crashpad observations above. No current universal collection path for those two was verified here.

If the client opens, the same guide describes User Settings > Voice & Video > Debugging. Enabling Debug Logging and reproducing an issue is a separate, optional support step; Upload sends logs to Discord Support. A client that cannot open cannot use that UI. You can prepare the local record first and decide what to submit through Support later.

The nuclear option and what it costs

Before deleting either folder, be ready to sign in again. Confirm access to the account’s existing sign-in and required verification methods; Discord’s MFA recovery guidance describes recovery limits. You do not need to change MFA. Check OS support and incident timing first. Keep the error details and any relevant existing logs separately before removing local data.

Discord’s general guide recommends backing up settings and data before installation fixes. Keep any local backup separate.

If the app opens, record preferences that matter through their settings pages; custom keybinds are under User Settings > Keybinds on desktop. The reviewed guides do not provide a settings.json restoration procedure. Do not automatically overwrite the new file with the old one; that can reintroduce the state you are trying to isolate. Reapply needed preferences through the supported UI when possible.

For an eligible Windows install, the two-folder cleanup procedure is:

1. Quit Discord and close its processes. Uninstall it from Settings > Apps > Installed apps, the same list the Windows 11 debloat page walks through.
2. Remove the Discord subfolder in %localappdata% and the discord subfolder in %appdata%. Do not delete either AppData parent folder. Read the full paths before confirming.
3. Restart Windows, then install from discord.com/download, subject to the support check above. If it still fails, retain the new error and use Support.

A clean reinstall may help a damaged installation. It cannot promise a cure for every local-file problem.

You lose the client’s local settings file, which on my install holds the window position and size, the audio subsystem choice and a handful of startup flags.

The three cache folders held about 60 MB on my install before I cleared them and were back to 21 MB twenty seconds after a relaunch. That is the observed rebuild; the later size and timing were not measured. The persistence of every keybind, overlay preference or device choice was not established by that test.

This procedure targets local client folders. Discord separately holds messages and account/server information, as described in its data-package guide. An AppData copy is not an account backup, and a local reset cannot promise later access to every message, membership or role. Account access and the availability of those items remain separate questions.

What I ran on my own machine

Windows 11 Home, build 26200.9445, on 2026-09-12 between 22:27 and 22:35 Central. Discord was installed but not running; its registry version string read 1.0.9256. I launched it through Update.exe, the way the Start menu shortcut does. Fifteen seconds later Task Manager listed six Discord.exe processes and two DiscordSystemHelper.exe processes. taskkill /F /IM Discord.exe returned six SUCCESS lines and the process count went to zero.

A second launch brought all six back, and the updater log showed it had switched to app-1.0.9257 during the first run; the registry string now reads 1.0.9257. I then quit it again so the machine was back where it started.

The cache folders under %appdata%\discord measured 58 MB (Cache), 1.2 MB (Code Cache) and 548 KB (GPUCache). I then deleted the three cache folders with the client closed and launched it again; twenty seconds later all three existed again and the client was open and signed in.

The settings.json file there is 508 bytes and has no hardware-acceleration key. Windows’ startup command list has no Discord entry on this machine. I did not reproduce a Starting hang or a Connecting hang; the ordering above comes from Discord’s own guide and the threads cited rather than from a hang I measured.

Sources

• Discord Support, Discord Troubleshooting Guide (read 2026-09-12; loading screen freezes, update problems, Windows installation errors)
• Discord Support, Stuck on the Main Connecting Screen (994 of 11,983 found helpful as of 2026-09-12)
• Discord Status, incident history read 2026-09-12
• Discord download page
• Reddit r/discordapp, Discord Won’t Open (July 30, 2017; the 116-point taskkill reply)
• Reddit r/discordapp, Discord stuck at Starting (March 2, 2023; 492 comments)
• Reddit r/discordapp, Help discord stuck at starting (January 29, 2026; 58 comments)
• Reddit r/discordapp, Discord crashes on launch, only on one user profile (September 11, 2026; Discord staff replies and the PTB build)
• Microsoft Q&A, Discord won’t start! (May 15, 2025)

The October 23 update also uses the linked official OS retirement notices, browser-vendor requirements, feature/channel documentation and Statuspage records. Those sources update the support and timing decisions; they do not add a new installed-client test. The worked timing examples are synthetic. Current storage/reset guidance comes from Discord’s installer, account-data, appearance, recovery and bug-report pages linked beside each relevant step.