Discord Update Failed or Won't Open on Windows: 6 Fixes for the Loop, JavaScript Error and Blank Screen

Discord update failed or won't open: what is actually going on

On Windows, Discord is not one program but two layers: a small launcher called Update.exe that checks for and installs updates, and the real app (Discord.exe) that lives in a versioned folder next to it. When the launcher cannot download, unpack or start the newest version, you see "Update Failed", "Starting...", "Checking for updates" forever, or a grey or white window. Almost every fix below either repairs that launcher, clears a corrupted app folder, or removes whatever is blocking its network connection.

This guide is the broad troubleshooting map for every variant of "Discord will not start on Windows". If your only symptom is the retry countdown ("Update Failed, retrying in 5 seconds"), our focused page Discord Update Failed Loop: 7 Fixes That Actually Work gives the short version. Come back here when that does not work, or when your symptom is different: Discord stuck on the splash screen, a "JavaScript error occurred in the main process" box, a blank white or grey window, or an app that simply never appears after you double-click it.

A note on how we wrote this. Discord does not publish a detailed technical description of its updater, and the internal details can change between releases. Where we describe how the launcher behaves (folder names, what a retry means), that is based on what technicians see on real Windows 10 and Windows 11 machines and on Discord's own published troubleshooting steps, and we say so when something is a typical pattern rather than a guarantee. Everything that involves Windows itself (Task Manager, Run box, Windows Security, network settings) is standard and verifiable on your own PC.

The six symptoms and what they usually mean

Use the table to jump to the right fix. If you are not sure, follow the fixes in order: they go from the least invasive (ending stuck processes) to the most thorough (a full clean reinstall), and each one is safe on its own. Your messages, servers and friends are stored by Discord's service, not on your PC, so none of these steps deletes your account or chat history.

Before you start: 5 quick checks that solve a surprising number of cases

Run these first. They take under three minutes combined and rule out problems that are not really about the app.

1. Is Discord itself down? Open discordstatus.com in a browser. During a real outage no local fix will help, and the launcher may loop simply because the update servers are not answering. If the status page shows an incident, wait and try again later. For a related server-side message, see our page on Discord error 1105.
2. Does Discord work in the browser? Open discord.com/app and log in. If the browser version works, your account, internet connection and Discord's servers are fine, and the problem is isolated to the desktop app on your PC. You can keep chatting there while you repair the app.
3. Is your Windows version supported? Discord's own support notice says that from March 15, 2024, Discord is no longer supported on Windows 7, 8 or 8.1, and you need at least Windows 10 to keep receiving updates. On those old versions an update loop is expected and cannot be fixed by cleaning folders. Check with Win + R, then winver.
4. Is the date and time right? A wrong system clock breaks secure connections (HTTPS) and makes downloads fail quietly. In Settings, Time and language, turn on automatic time and sync now.
5. Is there free disk space? The updater needs room to download and unpack the new version, and a nearly full C: drive makes that fail. A few gigabytes free is plenty for Discord, but if C: shows less than 1 GB free, free some space first.

Fix 1: End every Discord process, then relaunch

If you clicked Discord several times, or if a previous start crashed, hidden Discord processes can stay alive in the background and hold files open. A new launch then collides with the old one and appears frozen. Discord's own troubleshooting page for installer problems says the same: stray processes can hide in the system tray or in Task Manager, so double-check both.

1. Press Ctrl + Shift + Esc to open Task Manager.
2. On the Processes tab, find everything named Discord (there are often several) and also Update.exe if it is listed. Select each and click End task. If you do not see the full list, click "More details" first. Our short guide to the Task Manager shortcut covers the other ways to open it.
3. Check the system tray (the small arrow near the clock) and right-click any Discord icon, then choose Quit.
4. Optional but clean: open Command Prompt and run taskkill /f /im Discord.exe and then taskkill /f /im Update.exe. Seeing "process not found" is fine, it only means nothing was running.
5. Wait ten seconds, then start Discord once from the Start menu, and wait a full minute before clicking again.

Patience matters here. After an update, the first launch can take noticeably longer than normal because the new version unpacks and the app rebuilds some cached data. Clicking repeatedly spawns more processes and makes things worse.

Fix 2: The clean reinstall (the fix that solves most loops)

The single most effective repair is to remove both Discord folders in your user profile and install a fresh copy. This is the procedure Discord itself documents for installer failures, and it also fixes most update loops, "Starting" hangs and JavaScript errors, because all of those usually come from a damaged app folder. The key is to delete the leftovers properly. Using "Uninstall" in Settings alone often leaves the broken pieces behind, so the new install inherits the same problem.

Step by step

1. Close everything. Complete Fix 1 first so no Discord process is running.
2. Optional: uninstall in Settings. Open Settings, Apps, Installed apps, find Discord and choose Uninstall. If it is not listed, or the uninstall fails, skip this step: the folder deletion below does the real work.
3. Delete the roaming folder. Press Win + R, type %appdata% and press Enter. In the window that opens, delete the folder named Discord. This folder holds settings and cached data (Cache, Code Cache, GPUCache and similar).
4. Delete the local folder. Press Win + R again, type %localappdata% and press Enter. Delete the folder named Discord. This is where the Update.exe launcher and the versioned app folders (names like app-1.0.9xxx) live. The number differs on every PC and changes with each update.
5. If Windows says a file is in use, go back to Task Manager, end the remaining Discord tasks, and also check the Startup apps tab (Task Manager, Startup apps) so Discord does not relaunch itself. Then try again.
6. Restart Windows. This releases any file locks and clears temporary state.
7. Download a fresh installer from discord.com/download (the official site only) and run it. Wait: the installer shows a short progress window, then opens Discord by itself.

Why this works

The versioned folders under %LocalAppData%\Discord are replaced on each update. If a download is cut off (laptop sleeps, Wi-Fi drops, antivirus interrupts), the launcher can be left with a half-written version folder. On the next start it tries to reuse or repair that folder, fails, and retries forever. Deleting the whole folder removes the damaged state so the installer starts from nothing. The same logic explains the "JavaScript error occurred in the main process" box: the app's own script files are missing or truncated, so the main process throws an error before any window can open.

If the error returns right after a clean reinstall

A fresh install that fails again in the same way is a strong signal that the folder was not the real cause. The usual suspects, in order, are security software blocking the new files (Fix 3), a network or DNS problem (Fix 4) or a permissions problem on the profile (Fix 5). Do not repeat the cleanup over and over: change the variable instead. Our companion page on Discord installation failed (error 20012) covers the installer-side version of this problem if the setup file itself refuses to finish.

Installing a different build: PTB or Canary as a test

Discord publishes separate desktop builds. Stable is the normal one, Beta is called PTB (Public Test Build), and Alpha is called Canary, which is the least stable. Discord's support page about testing clients lists where to download PTB and Canary. Installing PTB next to Stable is a useful diagnostic: it lives in its own folders, so if PTB opens normally while Stable loops, the problem is isolated to the Stable install (a clean reinstall of Stable will fix it). If PTB loops in exactly the same way, the cause is almost certainly something on your PC or network, not the Discord app files. Expect more bugs in test builds, so use PTB as a test or temporary workaround, not as a long-term fix.

What about renaming Update.exe?

Some users in Discord's community forum report that renaming Update.exe in %LocalAppData%\Discord let them get past an update loop long enough to install. This is anecdotal, not an official Discord instruction, and we do not recommend it as a first step: a clean reinstall is cleaner and reversible. We mention it because it shows what the loop really is: the launcher is trying to run an update step that keeps failing, and anything that interrupts that step changes the outcome.

Fix 3: Antivirus, Windows Security and firewall blocking the launcher

Security software is the second most common cause once the folders are clean. The updater downloads files, writes them into your AppData folder, and then launches a new executable from there, which is exactly the behaviour some security products treat as suspicious, especially on a freshly created folder. When the product blocks or quarantines one of those steps, the launcher sees a failed update and retries.

What to check, in order

1. Windows Security protection history. Open Windows Security, Virus and threat protection, Protection history. Look for entries mentioning Discord or Update.exe around the time of the failure. If something was quarantined or blocked, restore it and add an exclusion for the Discord folder.
2. Controlled folder access. In Windows Security, Virus and threat protection, Ransomware protection, check whether "Controlled folder access" is on. If it is, it can stop applications from writing to protected folders. Look at "Block history", and if Discord was blocked, use "Allow an app through Controlled folder access" and add Discord.
3. Third-party antivirus. Products like Norton, McAfee, Kaspersky, ESET, Avast and Bitdefender have their own firewall and web-protection layers. Open the product's quarantine and log, restore anything from the Discord folder, and add %localappdata%\Discord as an exclusion. If you only want a test, pause real-time protection for a few minutes, run the installer, then turn protection back on right away.
4. Windows Firewall. If you or a program changed firewall rules, Discord could be blocked outbound. In Windows Security, Firewall and network protection, choose "Allow an app through firewall" and confirm Discord is allowed on Private and Public networks. If you are unsure, "Restore firewalls to default" resets Windows rules to standard.

Work and school computers

On a managed PC, Discord may be blocked on purpose: by a web filter, a firewall rule, an application-control policy or a school network. In that case the launcher cannot reach its update servers and loops forever, and nothing you do on the PC will change it. If this is a company-owned laptop, ask your IT team whether Discord is allowed. Do not try to work around a policy, you may be breaking your workplace rules. The browser version at discord.com/app may be allowed or blocked separately.

Fix 4: Network problems: VPN, proxy, DNS, IPv6 and "Checking for updates" forever

If Discord sits on "Checking for updates" or the update loop returns after a clean reinstall, the launcher is probably not reaching Discord's servers, or the connection is being altered on the way. The browser can work fine while the desktop launcher fails, because they do not necessarily share the same proxy, VPN or DNS path. Work through these in order, testing Discord after each change.

4a. Turn off the VPN (or switch its mode)

A VPN, a "secure DNS" feature in a security suite, or a browser-extension proxy can break the launcher's downloads. Some VPN servers are blocked by Discord's protection systems, and some VPN apps use split tunneling that leaves the launcher on a path that does not work. Disconnect the VPN completely, launch Discord, and let the update finish. Once Discord is on its newest version, you can usually turn the VPN back on. If you need the VPN, try another server, a different protocol, or add Discord to the VPN's split-tunnel list. For general background on when a VPN helps or hurts, see antivirus vs VPN: do you need both.

4b. Check the Windows proxy settings

Malware, old software or a former employer's configuration can leave a proxy turned on that no longer exists. Every request then goes to a dead address and times out.

1. Open Settings, Network and Internet, Proxy.
2. Under "Automatic proxy setup", try turning off "Automatically detect settings" and "Use setup script" if you do not use them.
3. Under "Manual proxy setup", make sure "Use a proxy server" is off unless you know you need it.
4. Restart Discord and test again.

If you find a proxy you did not set up and cannot explain, treat it as a possible security issue, not just a network quirk, and run a full malware scan. Our guide on free antivirus options lists reputable scanners to use.

4c. Flush DNS and reset the network stack

DNS turns names like discord.com into addresses. A corrupted DNS cache or a broken Winsock configuration can make the launcher fail on the lookup. Open Command Prompt as administrator (search cmd, right-click, Run as administrator) and run these, one per line:

ipconfig /flushdns
netsh winsock reset
netsh int ip reset

Restart the PC afterwards, because the Winsock reset only takes effect after a reboot. These commands are safe: they reset Windows networking state to defaults and do not delete files. They can, however, clear custom static IP settings on some manual configurations, so if your PC uses a fixed IP address, note your settings first.

4d. Switch to a public DNS resolver

If your internet provider's DNS is slow or filtering, a public DNS service can fix lookups. In Settings, Network and Internet, choose your connection (Wi-Fi or Ethernet), Hardware properties, DNS server assignment, Edit, Manual, turn on IPv4, and enter a preferred and alternate DNS address from a provider you trust (for example, Cloudflare's 1.1.1.1 and 1.0.0.1, or Google's 8.8.8.8 and 8.8.4.4). Save, restart Discord and test. If it fixes the problem, you can keep that DNS. If not, set it back to "Automatic (DHCP)". For symptom-level DNS errors in the browser, our DNS_PROBE_FINISHED_NXDOMAIN guide is a good companion.

4e. Test with IPv6 off

On some networks, IPv6 is advertised but broken somewhere along the path, so connections that prefer IPv6 time out before falling back to IPv4. This produces slow or failed downloads that look random. As a test, open Control Panel, Network and Sharing Center, Change adapter settings, right-click your adapter, Properties, untick "Internet Protocol Version 6 (TCP/IPv6)", click OK and test Discord. Do this as a diagnostic: if it helps, the real fix is on the router or with your provider, and you can re-enable IPv6 afterwards unless your network needs it off. If a router restart and a firmware check do not solve it, our guide on what to do when the internet is not working walks through the router side.

4f. Try another network

The quickest way to prove a network problem is to use a different network. Connect the PC to a phone hotspot and launch Discord. If the update completes on the hotspot, the issue is your home or office network (router, filter, parental controls, DNS) and not your PC or Discord. If it fails on every network, go back to security software (Fix 3) and permissions (Fix 5). If the connection itself drops often, see internet keeps disconnecting, because an unstable link interrupts downloads and leaves half-written update files.

Fix 5: Permissions, "run as administrator" and the user profile

Discord installs per user, into your own AppData folder, and normally does not need administrator rights. That is a deliberate design: a normal user can install and update it without admin approval. But there are cases where permissions get in the way, and Discord's own installer troubleshooting suggests setting the app to run as administrator as an extra step.

Run as administrator (as a test)

1. Open %localappdata%\Discord. Inside, open the newest app- folder.
2. Right-click Discord.exe, Properties, Compatibility tab.
3. Tick "Run this program as an administrator" and click OK.
4. Launch Discord from that file and see whether it opens.

Discord's support page suggests this, and also mentions trying compatibility mode for Windows 7 or 8 in installer cases. Our view: try administrator mode first as a diagnostic. Compatibility mode for older Windows versions is a last resort on Windows 10 or 11, and if it only works in compatibility mode, treat that as a sign something else is wrong. If administrator mode fixes it, find out why: it usually means folder permissions or security software, not a permanent need.

Folder permissions and profile problems

• Inheritance broken on AppData. If you ever used a cleanup tool or manual "take ownership" commands on your profile, permissions on %LocalAppData% may be wrong. Right-click the Local folder (inside AppData), Properties, Security, and make sure your user account and SYSTEM have Full control.
• Read-only attribute. If the Discord folder is marked read-only, the launcher cannot write updates. Right-click the folder, Properties, untick Read-only.
• Folder redirection or cloud-synced profile. If your Documents, Desktop or AppData are redirected to a network location or synced aggressively, the launcher's many small file writes can fail. Keep %LocalAppData% on the local drive.
• A damaged Windows profile. If other apps also fail to update or save settings, test with a brand-new local user account. If Discord works there, the old profile is the problem, which is a signal for a profile repair or migration rather than another Discord reinstall.

Corrupted system files

If several apps misbehave at once, Windows components may be damaged. In an administrator Command Prompt, run sfc /scannow and let it finish. If it reports problems it could not fix, run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow again, and restart. This is standard Microsoft guidance for system file corruption. If the machine is also slow, our application failed to start (0xc0000142) page covers a related symptom in other apps that often has the same root cause.

Fix 6: White screen, grey screen or a window that never loads

If Discord opens a window but it stays white, grey, black or blank, the app started but its interface did not render. That is a different branch from the update loop and has its own causes.

1. Clear the cache folders without a full reinstall. Close Discord completely (Fix 1), press Win + R, type %appdata%\discord, and delete the folders named Cache, Code Cache and GPUCache. Discord rebuilds them on the next start. This keeps your settings and is much lighter than the clean reinstall.
2. Update the graphics driver. Discord's interface is drawn with hardware acceleration. A buggy or very old graphics driver can produce a blank window. Install the current driver from the maker of your graphics card (NVIDIA, AMD or Intel) or from Windows Update, restart, and retest.
3. Turn hardware acceleration off. If Discord opens briefly, go to User Settings, Advanced, and switch Hardware Acceleration off. If it never stays open long enough, the settings file lives in the roaming folder and the clean reinstall in Fix 2 resets it.
4. Check for overlay and capture software. Third-party overlays and screen-capture tools that inject into other programs can break the window. Close them one by one (for example GPU control panels, game-performance overlays, screen recorders) and retest.
5. Test your connection. A white window with a spinner can also mean the app opened but cannot reach the service. Go back to Fix 4.

If the window flashes on screen and closes immediately, the app is crashing at startup. That points to damaged files (Fix 2), security software killing the process (Fix 3), or a driver or system-file problem (this fix and Fix 5).

"A JavaScript error occurred in the main process": what it means and how to fix it

This message comes from the framework Discord's desktop app is built on, which runs a JavaScript "main process" that starts the app. The error box means that process threw an error before the window could be created. The text underneath usually mentions a file path or a module that "cannot be found", which is the clue: files in the app folder are missing, corrupted or blocked.

The reliable fix is the clean reinstall from Fix 2, deleting both Discord folders. Two details improve the odds. First, close every Discord process before deleting, otherwise a locked file is left behind and the new install inherits it. Second, read the error text before dismissing it. If it names a path in a user profile folder with unusual characters or a different drive, that suggests a profile or redirection issue (Fix 5). If it names a module in the Discord folder, the clean reinstall is the right move. The same error can appear in other desktop apps built on the same framework, so a fix that cures it for Discord often cures it for them, but do not delete other apps' folders without a reason.

Other causes that keep Discord from starting

If the six fixes above did not solve it, these less common causes are worth checking. They are listed from most to least likely.

• Discord starting with Windows and colliding with itself. If "Open Discord" is on at login and the previous session did not exit cleanly, the new instance can hang. In Task Manager, Startup apps, disable Discord, restart, then launch manually once to confirm it works. Turn the startup option back on in User Settings, Windows Settings after it is stable.
• Another instance running under a different user. On a shared PC with Fast User Switching, a Discord process from another signed-in account can hold resources. Sign the other user out fully.
• Pending Windows updates or a half-finished restart. A PC that has installed updates but not rebooted can behave strangely with newly installed apps. Restart fully (use Restart, not Shut down, because Fast Startup can keep a stale session alive).
• Disk errors. A failing drive can corrupt downloads over and over. If clean reinstalls keep breaking in different ways, run chkdsk /scan and check the drive's health. A drive with real faults is a data-safety issue first and a Discord problem second.
• Old graphics or audio drivers. Outdated or damaged drivers can crash a modern Chromium-based app at startup. Update them from the manufacturer.
• Overclocking or unstable memory. Rare, but unstable RAM can corrupt unpacked files. If other programs also crash randomly, test memory with the built-in Windows Memory Diagnostic.
• Malware. Some malware targets Discord, because it stores login tokens, and some fake "Discord update" downloads are malicious. If you downloaded an installer from anywhere other than discord.com, or Discord started failing after you ran a "free Nitro" or "game crack" file, scan the PC and change your Discord password. Never download the installer from a link in a chat message.

Reinstalling the right way (and avoiding the same loop later)

A proper reinstall has four parts: clean removal, a clean download, a clean first run, and good habits afterward.

1. Clean removal. Both folders gone (%appdata%\Discord and %localappdata%\Discord), as in Fix 2, followed by a restart.
2. Clean download. Only from discord.com/download. Avoid third-party "download" sites, which often wrap the installer with unwanted software. If your browser cached a broken installer earlier, delete the old file and download again.
3. Clean first run. Run the installer normally (a plain double-click, no special flags). Let it finish. Do not launch it three times. The first start can take a minute while it unpacks.
4. Good habits. Do not kill Discord in the middle of an update, do not let the laptop sleep during the update, and keep disk space free. If you use a VPN, let Discord update before connecting to it.

If you keep a modded client or plugin on top of Discord, those can break after an official update and produce launch failures too. Remove the mod, do a clean reinstall of the official client, and confirm it works before adding anything back. Modified clients are not supported by Discord, and we cannot advise on them.

Quick notes for Mac and Linux

This article focuses on Windows, because Squirrel-style folders and the Update.exe launcher are Windows-specific. The idea of a clean reinstall applies elsewhere too, but the details differ and we only describe what is standard.

• Mac: Quit Discord fully (Command + Q, and check Activity Monitor), drag Discord out of Applications to the Trash, and download a fresh copy from discord.com/download. Discord's settings and cache on a Mac are normally stored under your user Library folder (in Application Support). Deleting that folder resets the app settings, but check the exact location on your own Mac before deleting. Installation or permission messages on macOS are often caused by the download being damaged or by macOS privacy settings, so also try downloading again in a different browser.
• Linux: Discord offers packages in several formats (deb, rpm, tar.gz and others) on its official download site, and the build you installed matters: a package from your distribution or a sandboxed package can behave differently from the official one. If it will not open, reinstall from the official package for your distribution and check you have current graphics drivers. We cannot give a one-size command for every distribution.
• Browser fallback: On any system, discord.com/app is the fastest workaround while you fix the desktop app.

Comparison: which fix to try, how long it takes, how much it risks

Printable checklist: Discord will not start on Windows

Three realistic scenarios

These are illustrative scenarios built from common patterns we see, not real client cases.

Realistic scenario 1: the gamer whose loop returned after a clean reinstall

A student on a Windows 11 gaming PC deletes the Discord folders, reinstalls, and still sees "Update Failed" within a minute. The Protection history in Windows Security shows a blocked item from the Discord folder dated minutes earlier, and a third-party antivirus (installed by the PC maker as a 30-day trial) is also active. Restoring the item and adding an exclusion for %localappdata%\Discord lets the update finish on the next try. Time: about 15 minutes. Lesson: a repeat failure after a clean install usually means something is actively blocking the files.

Realistic scenario 2: the home-office worker stuck on "Checking for updates"

A remote worker uses a paid VPN all day. Discord worked for months, then began hanging on "Checking for updates" after an app update. With the VPN disconnected, the update completes in 40 seconds. The worker adds Discord to the VPN's split-tunnel exclusions and the problem does not return. Time: 10 minutes. Lesson: update while the VPN is off or excluded.

Realistic scenario 3: the PC that fails on every network

A 6-year-old laptop shows a JavaScript error in the main process on Discord, and a clean reinstall fails twice in different ways, each time with a slightly different missing file. A phone hotspot makes no difference, sfc /scannow reports files it could not repair, and the drive's health tool shows reallocated sectors. This is not a Discord problem: the drive is failing, and the priority is to back up important files and replace the drive. Time: a few hours, plus the replacement. Lesson: random corruption across clean installs is a hardware warning.

What it costs: doing it yourself vs paying a technician

Most Discord launch problems are DIY-sized. Where a technician saves the most time is when the cause is not in Discord at all: a security product acting up, a damaged profile, or a drive that is slowly failing. If you also run a small business and Discord is used for customer chat, an hour of downtime costs more than the consultation.

When to call a professional

Call for help if any of these is true:

• You completed a clean reinstall plus the security and network checks and the failure repeats.
• Other programs also fail, crash or lose settings, which suggests Windows or the drive.
• You suspect malware, a stolen Discord login, or you installed something from a doubtful link.
• The PC is managed by an employer or school and you are not sure what is allowed.
• You do not want to delete system folders or edit network and security settings yourself.

IT Cares has provided remote and on-site IT support in Quebec and across Canada since 2014. A technician can connect to your PC, find the cause with you watching, and fix it. Call 1 (888) 711-9428 or book a remote session. Once Discord opens again, if your voice does not work in calls, our guide on fixing a Discord mic that is not working picks up where this one ends.

Official resources

When a fix involves Discord's own behaviour, trust Discord's published pages over forum posts. These are the ones we used: the [Windows] Installer Errors article (clean folder removal, run as administrator), the Discord Testing Clients article (PTB and Canary), and the system requirements and Windows 7, 8 and 8.1 support notices. The full links are in the Sources list below. If you still cannot get Discord running, Discord Support accepts requests at dis.gd/contact, as its own installer page says.

Frequently asked questions

Related guides

• Discord Update Failed Loop: the short guide
• Discord installation failed (error 20012)
• Discord error 1105 (server error)
• Discord mic not working: 13 fixes
• How to turn off Windows Defender safely
• Firewall vs VPN vs antivirus
• Internet not working: router and network fixes
• Windows error 0xc0000142

Sources and official references

Last verified: November 5, 2026

• Discord Support: [Windows] Installer Errors (opened 2026-11-05)
• Discord Support: Discord Testing Clients, Stable, PTB and Canary (opened 2026-11-05)
• Discord Support: [Known Issue] Support for Windows 7, 8, and 8.1 (opened 2026-11-05)
• Discord Support: OS/system requirements (seen in search 2026-11-05)
• Discord download page