Discord Not Opening? The Fix Order That Works (2026)

By LK Wood IV · Published 2026-09-12 · Updated 2026-09-12 · ~8 min read · St. Louis County, MO

Discord failing to open has three shapes, and each one has a different first move. Most guides hand you a long list. You work through it blind. I would rather you identify the shape in ten seconds, run the one fix that matches, and check the proof before moving on. Every command and path below was run or read on my own Windows 11 install on 2026-09-12; the details of that are at the bottom.

Which symptom you have

One test sorts the first four rows fast. Open discord.com/app in a browser. If it loads and you can read messages, your account and connection are fine and the desktop client is the fault. If it does not load either, skip straight to the status page.

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.” It still applies in 2026 because the client is still a set of Discord.exe processes, which is what my own process list shows.

Here is what a running client looks like on my machine. 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 standard explanation in the threads below, and it fits the process list, is that a startup failure can leave one of those processes alive with no window, so every later click on the icon hands off to it and shows you nothing.

Open a command prompt and run this:

taskkill /F /IM Discord.exe

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

The proof it worked: the window appears. If Task Manager still lists a Discord.exe after the taskkill, the usual reason is that the prompt lacked the rights; right-click Command Prompt and choose Run as administrator, then run it again.

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 is an incident every three days. If your client failed on one of those days, no amount of cache-clearing would have helped, and the January 2026 r/discordapp thread “Help discord stuck at starting” shows the pattern: the poster had “tried everything on yt” and reinstalled, and the replies I read were other people reporting the same failure that day and asking whether Discord was down.

The proof: the component your problem lives in says Operational, and there is no open incident. If there is one, stop here. Wait for it to say Resolved.

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

Discord’s guide says “Clear Discord’s cache and temporary files” for loading-screen freezes. The folders it means live under the roaming profile. Press Win+R, type %appdata%\discord and press Enter. Inside are folders named Cache, Code Cache and GPUCache. On my install they hold 58 MB, 1.2 MB and 548 KB. Quit Discord fully (Fix 1), delete those three, and launch again. 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.

Do not delete the whole discord folder unless you are ready to sign in again. The 2023 thread “Discord stuck at Starting,” at 492 comments when I read it, was started by someone doing exactly that 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.” The three cache folders are the part that goes stale. The rest of that folder is your session and settings. Leave it alone.

The proof: the splash passes and the folders reappear with fresh timestamps, still signed in.

5. Break the update loop

The “Starting” splash is not Discord itself. It is Update.exe, the Squirrel launcher, checking for a new build before it starts the real client. The install lives at %localappdata%\Discord, and inside it each version is its own folder. 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.

When that hand-off breaks, you get a splash that never ends or an “Update failed” message that repeats. Discord’s guide gives the fix under Update Problems: “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 Microsoft Q&A answer does: it sends you to %localappdata% and the Discord folder there, which is also where the registry’s InstallLocation string for Discord points on my machine. So my reading is: kill the processes (Fix 1), delete the entire Discord folder under %localappdata%, and run a fresh installer from discord.com/download. 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, so I would go straight to removing the whole thing.

Your messages and settings are not in that folder. They live under %appdata%. This step leaves that alone.

The proof: the SquirrelSetup.log inside the new Discord folder ends with an “About to launch” line naming the new app folder, and the window appears.

6. Stuck on “Connecting”: the network list

Discord’s article “Stuck on the Main Connecting Screen” is short, and I quote its list because people paraphrase it badly. 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, and it is why this page does not start with the network list. My read of that number is that the list does not match most readers’ actual cause. An incident (Fix 2) or a stale process (Fix 1) is cheaper to rule out, so run the network list after those.

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 paints for even a few seconds, use them for that toggle. If it never does, the full reinstall below removes settings.json, the file where the client keeps its local flags, and starts the client with defaults.

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

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

This one is new and it is not in any of the listicles yet. 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!” PTB is Discord’s test channel and installs as a separate app; one of the posters had it running normally on the same PC beside the broken Stable install. 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 thread’s evidence says the crash is tied to something in the affected Windows profile, so if you hit it, try PTB before you rebuild your account.

The proof: run Discord.exe from a command prompt inside the app folder under %localappdata%; if the log no longer ends in the render-process crash line and the home screen loads, you are past it.

The nuclear option and what it costs

A full reinstall is: quit Discord (Fix 1), uninstall it from Settings, Apps, Installed apps (the same list the Windows 11 debloat page walks through, label by label), delete both the Discord folder under %localappdata% and the discord folder under %appdata%, restart Windows, and install fresh from discord.com/download.

It fixes anything a local file can cause. Here is what it costs, from the folders I read on my own machine. You sign in again, and any two-factor prompt comes with it. 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, so expect the cache to rebuild over the first days of use. Keybinds, overlay preferences and device choices that live locally are reset. Discord’s guide says it plainly: “Before attempting any installation fixes, back up your Discord settings and data.” Copy the discord folder under %appdata% somewhere first, and you can put settings.json back afterward.

Nothing server-side is touched. Your servers, friends, messages and roles live on Discord’s end and come back when you sign in.

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): https://support.discord.com/hc/en-us/articles/31623498041623-Discord-Troubleshooting-Guide
• Discord Support, Stuck on the Main Connecting Screen (994 of 11,983 found helpful as of 2026-09-12): https://support.discord.com/hc/en-us/articles/115001130052-Stuck-on-the-Main-Connecting-Screen
• Discord Status, incident history read 2026-09-12: https://discordstatus.com/
• Discord download page: https://discord.com/download
• Reddit r/discordapp, Discord Won’t Open (July 30, 2017; the 116-point taskkill reply): https://www.reddit.com/r/discordapp/comments/6qj97u/discord_wont_open/dkxu8lu/
• Reddit r/discordapp, Discord stuck at Starting (March 2, 2023; 492 comments): https://www.reddit.com/r/discordapp/comments/11g8wry/discord_stuck_at_starting/
• Reddit r/discordapp, Help discord stuck at starting (January 29, 2026; 58 comments): https://www.reddit.com/r/discordapp/comments/1qqdym5/help_discord_stuck_at_starting/
• Reddit r/discordapp, Discord crashes on launch, only on one user profile (September 11, 2026; Discord staff replies and the PTB build): https://www.reddit.com/r/discordapp/comments/1wd2rvt/discord_crashes_on_launch_no_error_in_event/
• Microsoft Q&A, Discord won’t start! (May 15, 2025): https://learn.microsoft.com/en-us/answers/questions/3860914/discord-wont-start