How to Fix Discord Fatal JavaScript Error

You double-click Discord and instead of your servers you get a small, ominous dialog box: a fatal JavaScript error occurred. Discord never opens, clicking OK just closes the dialog, and trying again gives you the same box. No chat, no voice, no way in. This guide explains what the fatal JavaScript error means in plain English, the handful of things that usually cause it, and the fixes that get Discord opening again, in the order you should try them.

The most important thing to know up front is that this is a local app problem, not an account problem and not a Discord server outage. Your account, servers, and messages are safe on Discord's servers. Something on your own PC — usually a corrupted cached file — is stopping the Discord app from starting, which means the fix is in your hands and in most cases takes less than ten minutes.

What does the fatal JavaScript error actually mean?

In plain English, the fatal JavaScript error means Discord tried to start and one of its own program files failed to load. Discord's desktop app is built on web technology, so a large part of it runs as JavaScript code. When Discord starts up, it loads that code from files stored on your PC. If one of those files is corrupted, blocked by your antivirus, or unreadable because of a permission problem, the startup process crashes immediately and Discord shows you this dialog instead of the app window.

The word fatal sounds dramatic, but it only means the error was serious enough that Discord could not continue starting — it does not mean your computer is damaged or your account is in trouble. The same error dialog can appear for several different underlying causes, which is why the fixes below are ordered from the most common cause to the least. Start at the top and stop as soon as Discord opens normally.

What causes the fatal JavaScript error?

The causes, in rough order of likelihood:

• Corrupted app data — the most common cause by far. Discord stores cached files in its AppData folders, and if an update is interrupted or a file gets damaged, the next startup crashes on the bad file.
• A half-running Discord session — a Discord process left over from a previous session can lock files the new launch needs, producing the same startup crash every time.
• Antivirus blocking a Discord file — security software sometimes flags a Discord component after an update and quarantines or blocks it, so Discord cannot load it at startup.
• Permission problems — if Discord cannot read or write its own folders, startup fails. This often appears after moving user folders, changing Windows accounts, or tightening folder permissions.
• Leftover files after an update or reinstall — a normal reinstall does not remove the AppData folders, so corrupted files survive the reinstall and the error comes straight back.
• Conflicting software — overlays, VPN clients, and some system utilities can interfere with how Discord loads at startup, though this is less common than corrupted cache.

1End every Discord process in Task Manager

Press Ctrl + Shift + Esc to open Task Manager and look for Discord in the Processes tab. Discord often keeps background processes running even after its window closes, and a stuck process from a previous session can lock the files a fresh launch needs. End every Discord entry you find, including any Discord helper processes, then wait a few seconds and launch Discord again. If the error persists, restart your PC — which clears every stuck process at once — and launch Discord before opening anything else.

2Delete the Discord app data folders

This is the fix that resolves the fatal JavaScript error most often, so do it carefully. First, make sure Discord is fully closed, including from the system tray. Then press Windows + R, type %appdata%, and press Enter. Find the Discord folder in the window that opens and delete it. Next, press Windows + R again, type %localappdata%, press Enter, and delete the Discord folder there too. Now launch Discord: it will rebuild both folders with fresh, clean files and ask you to log in again. Your servers, messages, and friends are stored on Discord's servers, so nothing is lost — only local cached files are removed.

3Run Discord as administrator

Right-click the Discord shortcut and choose Run as administrator, then see whether the app opens. Permission problems can stop Discord from reading or writing its own files at startup, especially after a Windows update, a move of your user folders, or a change of Windows account. If Discord opens as administrator but not normally, the problem is permissions: you can set the shortcut to always run elevated from its Compatibility tab, or check that your Windows user account has full control over the Discord folders in AppData.

4Check your antivirus quarantine

Open your antivirus and look at its quarantine, blocked applications, and recent detections for anything Discord-related. Security software sometimes flags a Discord component after an update, and a quarantined file produces exactly this kind of startup crash. Restore anything Discord-related from quarantine, add Discord and its AppData folders to your antivirus exceptions list, and then try launching Discord again. As a test only, you can briefly disable real-time protection and try launching — if Discord starts, you have found the culprit, and you should re-enable protection immediately and use the exceptions list instead of leaving it off.

5Uninstall Discord completely, including leftover folders

If the AppData cleanup alone did not work, do a proper clean removal. Go to Windows Settings, then Apps, find Discord, and uninstall it. Then delete any remaining Discord folders manually: the Discord folder in %appdata%, the Discord folder in %localappdata%, and any Discord folder left in Program Files. This step matters because a standard uninstall leaves those folders behind, and a fresh install that picks up the same corrupted files will show the same error. Only after every leftover folder is gone is the removal truly clean.

6Reinstall Discord from the official site

Download the latest installer from the official Discord site — not from a third-party download mirror — and install it fresh. A clean install replaces every app file, including the JavaScript components that were failing to load. After installation, launch Discord and log in. If you performed the full cleanup in fix 5 first, this fresh install starts from genuinely clean files, which is why the combination of fix 5 and fix 6 succeeds where a quick reinstall over the old install fails.

7Use the Discord web app while you troubleshoot

If the desktop app still will not open after every fix above, you do not have to wait in silence: open Discord in your browser and log in there. The web app gives you full access to your servers, direct messages, and voice channels, and it is unaffected by whatever is breaking the desktop app, because it runs entirely in the browser. Use it to stay in touch while you try the desktop fixes again, and if the desktop app never recovers, contact Discord Support with a screenshot of the exact error dialog and the steps you have already tried.

Quick checklist

• ☐ End every Discord process in Task Manager (or restart your PC)
• ☐ Delete the Discord folders in %appdata% and %localappdata%
• ☐ Run Discord as administrator and try launching again
• ☐ Check antivirus quarantine and add Discord to exceptions
• ☐ Uninstall Discord and delete all leftover folders manually
• ☐ Reinstall from the official Discord site
• ☐ Use the Discord web app as a workaround if the desktop app still fails

Frequently asked questions

If the fatal JavaScript error is gone, Discord should open to your servers on the next launch. If it is still there after working through every fix above, note whether the error started after a Discord update, a Windows update, or an antivirus alert — those three details tell Discord Support whether you are dealing with a corrupted install, a permission problem, or a blocked file, and they are worth including in any ticket you open.