Need help fixing a Discord fatal Javascript error

General
1

I keep getting a “Discord Fatal Javascript Error” every time I try to open the desktop app on Windows. I’ve already tried reinstalling Discord, clearing AppData, and disabling my antivirus, but the error still pops up and the app won’t launch. Can someone explain what usually causes this and walk me through any reliable steps or advanced fixes to resolve it for good

2

I had this same fatal Javascript error loop a few months ago. Reinstall alone did nothing. What fixed it for me was nuking every Discord and Discord-related process and file, then fixing corrupted stuff on Windows.

Try this step by step:

  1. Kill everything Discord

    • Press Ctrl + Shift + Esc.
    • Go to Processes.
    • End task on any Discord.exe, Update.exe, Squirrel, or anything that looks related.

  2. Remove all Discord folders

    • Press Win + R, type:
      %AppData%
    • Delete the Discord folder.
    • Press Win + R again, type:
      %LocalAppData%
    • Delete any Discord folder there too.
    • Also delete:
      C:\Users\YourUser\AppData\Roaming\discord
      C:\Users\YourUser\AppData\Local\Discord
    • Empty Recycle Bin.

  3. Delete the Discord updater and Squirrel leftovers

    • Go to:
      C:\Users\YourUser\AppData\Local\SquirrelTemp
    • Delete everything in there.
    • If you see “DiscordSetup” in Downloads or Temp, delete those too.

  4. Check for corrupted files on Windows

    • Press Start, type cmd.
    • Right click Command Prompt, run as Administrator.
    • Run:
      sfc /scannow
    • Wait for it to finish.
    • Then run:
      DISM /Online /Cleanup-Image /RestoreHealth
    • Restart your PC after both.

  5. Install Discord fresh

    • Go to discord.com in a browser.
    • Download the latest stable Windows app.
    • Right click the installer, choose “Run as administrator”.

  6. If the error pops up again

    • Press Win + R, type:
      %LocalAppData%\Discord
    • Open the folder with a version number, like app-1.0.9030.
    • Right click Discord.exe, choose “Run as administrator”.
    • If that works, the shortcut might point to a broken install. Recreate the shortcut from this exe.

  7. Check for conflicting stuff

    • Some overlay or hook tools break Discord.
    • Temporarily disable:
      • Overwolf
      • Razer Synapse overlay
      • MSI Afterburner overlay
      • Nahimic or Sonic Studio sound tools
    • Restart Discord after each change.

  8. Check the log to see what is blowing up

    • Go to:
      %AppData%\discord\logs
    • Open the latest .log file with Notepad.
    • Look for lines with “Error” around the time you launched it.
    • Post the exact error message and stack trace on the thread if you want more targeted help.

If none of that works, easiest workaround is to use Discord PTB or Canary since they install in a separate path.

Links you might need:
Official download:

PTB:

Canary:

3

Couple more angles you can try that don’t repeat what @kakeru already laid out:

  1. Figure out what’s actually crashing (the real error text)

    • When the “Discord Fatal Javascript Error” pops, there’s usually more detail like:
      • EPERM: operation not permitted
      • ENOENT: no such file or directory
      • Cannot find module '...’
    • Screenshot or copy that exact message. Different text = different cause. For example:
      • EPERM often = permissions / AV / something locking files.
      • ENOENT often = missing / half‑deleted resources.
      • “Cannot find module” = broken or outdated Discord files.

  2. Check if it is your user profile, not Discord

    • Create a new local Windows user account:
      • Settings → Accounts → Family & other users → Add someone else.
    • Log in with that new user, download Discord, install and run.
    • If it runs fine there, the corruption is inside your main Windows profile (registry entries, path issues, or leftover perms), not the global install.
    • In that case:
      • Check your main profile’s %AppData%\discord and %LocalAppData%\Discord security permissions:
        • Right click folder → Properties → Security.
        • Make sure your user has Full control.
      • If permissions look broken, reset using:
        • icacls '%AppData%\discord' /reset /T in an elevated CMD.
        • Same for %LocalAppData%\Discord.

  3. Verify your .NET / Visual C++ stack

    • Discord is Electron and uses a bunch of system libs. Corrupted runtimes can trigger what looks like a Javascript error.
    • Go to “Apps & Features”:
      • Find all Microsoft Visual C++ Redistributable entries.
      • Repair them (don’t just uninstall).
    • Install latest supported Visual C++ from Microsoft’s site (x86 and x64).
    • Also make sure Windows Update is actually up to date, not stuck on a failed patch.

  4. Disable weird filesystem stuff

    • If you’re using:
      • OneDrive “Files on Demand”
      • Cloud backup that hooks into AppData
      • Third party anti-ransomware controlling folders
    • Temporarily:
      • Pause OneDrive / backup client.
      • Turn off “controlled folder access”:
        • Windows Security → Virus & threat protection → Ransomware protection → Controlled folder access → Off (for testing).
    • Then try launching Discord again. A lot of those “Fatal Javascript Error” dialogs end up being JS code complaining that it cannot read or write to a file the OS just blocked.

  5. Try a completely offline install run

    • Disconnect from internet (pull cable / disable Wi‑Fi).
    • Start DiscordSetup.exe as admin.
    • Let it finish, then launch Discord once.
    • Sometimes the installer is updating itself mid‑install and if your connection or DNS is flaky, you get a half‑baked build that JS chokes on.

  6. Nuke Discord’s GPU usage

    • Discord uses hardware acceleration by default, and if your GPU drivers are crusty, JS error can be a side effect of the renderer failing.
    • You can force disable hardware acceleration via a shortcut flag:
      • Create a shortcut to Discord.exe in %LocalAppData%\Discord\<version>\.
      • Right click → Properties → Target, append:
        • --disable-gpu
      • Run Discord using that shortcut.
    • Also worth updating GPU drivers from NVIDIA / AMD / Intel directly.

  7. Check the Event Viewer for what Windows thinks

    • Win + R → eventvwr.msc.
    • Windows Logs → Application.
    • Filter by “Error” and look for entries with Discord.exe or Squirrel.
    • If you see something like .NET Runtime or SideBySide errors around the same time, that points more to system libs rather than Discord itself.

  8. If you’re on some weird drive / path

    • Don’t install Discord on a network drive, SD card, or some funky junction point.
    • Let it install to the default %LocalAppData%\Discord on your system drive.
    • If you previously tried to “portable-ify” it by copying folders around, delete that and stick with the default.

Personally, I’d do this order next:

  1. Note the exact error text in the JS popup.
  2. Test with a brand‑new Windows user account.
  3. Repair Visual C++ and update Windows & GPU drivers.
  4. Run Discord with --disable-gpu.
  5. Check Event Viewer + Discord logs for EPERM / ENOENT / module errors.

If you post the specific error line from the fatal JS dialog and maybe a line or two from %AppData%\discord\logs, people can usually pinpoint the cause instead of just saying “reinstall Discord” for the 19th time.

4

Couple of angles that haven’t been covered yet, focusing less on “nuke & reinstall” and more on environment conflicts.

1. Check for Electron-level conflicts

Discord is just an Electron app. If you have issues with other Electron apps (VS Code, Slack, Teams, etc.) crashing or giving similar JS errors, that points to a shared dependency problem rather than Discord itself.

  • Try launching another Electron-based app.
  • If it also misbehaves, suspect:
    • System-wide environment variables
    • Security software hooks
    • Third party “optimizer” tools

Temporarily disable any “PC cleaner,” “game booster,” or OS skinning tools that hook into processes.

2. Strip down your startup environment

Instead of only killing Discord processes like @mikeappsreviewer and @kakeru suggested, try a clean boot of Windows:

  1. Press Win + R → type msconfig.
  2. Go to Services tab.
  3. Check “Hide all Microsoft services.”
  4. Click “Disable all.”
  5. Go to Startup tab → open Task Manager.
  6. Disable everything non-essential (RGB, game launchers, overlays).
  7. Reboot and test Discord.

If it works in this minimal state, re-enable things in batches until you find the culprit.

3. Look at system-wide environment variables

Corrupted or weird %TEMP% / %TMP% or custom PATH entries can break installers and Electron apps in subtle ways.

  1. Right click Start → System → Advanced system settings.
  2. Click “Environment Variables.”
  3. Check:
    • User and System TEMP / TMP point to valid folders (usually C:\Users\<you>\AppData\Local\Temp).
    • Those folders exist and are writable.
  4. Clear them out:
    • Go to each Temp folder and delete contents you can (skip locked files).
  5. Try Discord again.

If the JS error mentions temp paths, this is a strong candidate.

4. Check for file system / profile path weirdness

If your Windows username has non‑ASCII characters or you moved your profile to a different drive using junctions or registry hacks, Discord sometimes chokes.

  • Confirm your profile path is the default: C:\Users\<username>
  • If it is redirected using symlinks or network paths, try:
    • Creating a new user with a simple ASCII name.
    • Test Discord there (this extends what @kakeru said, but focus on the name/path specifically).

If it only fails on the complex-username profile, the fatal Javascript error might be due to path parsing.

5. Group policy / corporate lockdown scenarios

If this is a work or school machine:

  • IT policies can block:
    • Running from %LocalAppData%
    • Squirrel-based updaters
    • Writing to AppData
  • That can manifest as “fatal Javascript error” instead of a clean “blocked by policy” message.

Open gpedit.msc (if available) and check under:

  • Computer Configuration → Administrative Templates → Windows Components → Attach your attention to any policy related to installers, software restriction, or AppData.

If you are under strict policy and cannot change it, the web version is the safest route.

6. Disk / storage subtle issues

Even short of obvious disk failures, bad sectors or flaky SSD firmware can corrupt small files that Discord relies on.

  • Run chkdsk on the system drive:
    1. Open CMD as admin.
    2. chkdsk C: /f
    3. Accept reboot.
  • If your Discord folders live on a different drive or partition, run chkdsk there too.

If Event Viewer shows disk-related warnings around Discord crashes, this becomes more likely than a pure JS problem.

7. Competing Electron runtimes or “portable” remnants

If you previously tried a portable Discord or manually copied app folders:

  • That can leave broken shortcuts or partial runtimes.
  • Search your whole system drive for:
    • Discord.exe
    • Squirrel.exe
  • Delete any stray “portable” or manually copied Discord directories that are not under the standard AppData locations mentioned by @mikeappsreviewer.

8. About the “product” angle and pros/cons

Using the regular desktop Discord app instead of only web has its own pros and cons, which matter here since you are deciding whether to keep fighting this error:

Pros:

  • Better performance than browser in long sessions.
  • System-level features like push-to-talk and global keybinds.
  • Screen share and hardware acceleration features that can be smoother than browser.

Cons:

  • More fragile install due to Squirrel and Electron, which is exactly what you are hitting.
  • Sensitive to system-level changes, overlays, and weird security tools.
  • Needs periodic cleanup if updates or caches get corrupted.

If the desktop version keeps throwing fatal Javascript error even after trying the heavier steps from @mikeappsreviewer and @kakeru plus the environment checks above, it is completely reasonable to:

  • Park the desktop app for now.
  • Use the browser version long term.
  • Revisit the installer only after:
    • A major Windows update,
    • Driver refresh,
    • Or if you rebuild / reset Windows.

At this point, the next debugging move would be: screenshot the exact JS error text and cross-check it with Discord’s logs and Event Viewer. That specific message usually narrows it from “something is wrong” to “this file / permission / path is wrong,” which is the point where further troubleshooting becomes targeted instead of more reinstall cycles.