Discord Update Failed or Installation Has Failed: Fix It on Mac, Windows and Linux

What "Update Failed" and "Installation has failed" actually mean

Both messages mean the same thing in plain language: Discord could not replace its own program files on your computer. Your account is fine, your servers are fine, and nothing you wrote has been lost. The desktop app is just a program installed on your device, and the failure is between that program, your operating system and whatever sits in between, such as security software or a network filter.

This guide covers the whole family of problems on all three desktop systems. If you are on Windows and only want the shortest path, our existing page on the Discord Update Failed loop on Windows walks through seven fixes in order of success rate. This article goes wider: what is different on Mac and Linux, what to do when the screen says Installation has failed instead of a retry timer, what the STATUS_BREAKPOINT crash is, and what to check when a clean reinstall does not help.

The three messages people confuse

People search for the same symptom with different words, and the right fix depends on the exact wording on your screen. Here is how to tell them apart.

Why the problem tends to appear right after you start the computer

Discord checks for a new version every time it launches. When a new version exists, it downloads it, then tries to switch to it before showing you anything. That is why the failure feels sudden: yesterday it worked, today it will not even open. Nothing on your side necessarily changed. The new build arrived, and something on your system stopped it from being installed.

The things that stop it fall into five groups, and every fix in this guide targets one of them:

• Damaged or leftover files in the Discord folder from an interrupted earlier update.
• Locked files because a Discord process is still running in the background.
• Permissions: your user account cannot write to the folder Discord needs.
• Security software or network filters that quarantine files or block the download.
• Disk, time and connection basics: no free space, a wrong clock, an unstable network.

Five minute checks before you touch anything

Start with the checks that cost nothing and rule out the causes you cannot fix yourself. Confirm Discord is not having an outage, make sure you can still reach your account in a browser, and check disk space, the clock and the connection. Skipping these is the most common reason people spend an hour on repairs that were never needed.

1. Check whether Discord itself is down

Open discordstatus.com on your phone or in a browser. If the page reports an incident affecting updates, downloads or the API, wait and try again later. Repairing your computer during a provider outage only wastes your time. If the status page is green, the problem is on your side and the rest of this guide applies.

2. Use the web app so you are never locked out

Open discord.com/app in Chrome, Edge, Firefox or Safari and sign in. This confirms your account works and gives you messaging while you repair the desktop app. If you have two-factor authentication, have your authenticator app or backup codes ready now, because you will have to sign in again after a reinstall. If you cannot sign in even on the web, the problem is your account or your network, not the update.

3. Check free disk space

Discord is not large, but an update downloads a package, unpacks it and keeps the old version until the switch works. Keep at least 1 GB free on the drive that holds your user profile. On Windows that is normally the C: drive. On Mac check Apple menu, System Settings, General, Storage. A drive that is nearly full is a quiet cause of many "Installation has failed" cases, and it also hurts everything else on the machine, as we explain in our guides on speeding up Windows 11 and speeding up a MacBook.

4. Check the date, time and time zone

Secure downloads depend on a correct clock. If your computer's date is off by even a day, or the time zone is wrong because a battery died or a setting was changed, HTTPS connections can fail and updates with them. On Windows right click the clock and choose Adjust date and time, then turn on automatic time and time zone. On Mac use System Settings, General, Date and Time and turn on automatic setting. On Linux run timedatectl and check that the system clock is synchronized.

5. Check the connection

Try loading a large site and run a quick speed test. A weak Wi-Fi signal, a hotel or school network with a captive portal, or a VPN can interrupt a download in the middle, which the updater reports as a failed update. If you are on Wi-Fi, move closer to the router or plug in with a cable for the duration of the repair. If you use a VPN, switch it off for now and turn it back on after Discord works. We cover VPN trouble in more depth in our page on Windows VPN connection failures.

Windows: fix Update Failed and Installation has failed (Windows 10 and 11)

On Windows, Discord installs into your own user profile under %localappdata%\Discord and updates itself with a small program called Update.exe. When that folder is damaged, locked or blocked, you get the Update Failed loop or Installation has failed. The reliable repair is to close every Discord process, remove that folder, and install a fresh copy, which takes about five minutes.

Why Windows behaves differently from Mac and Linux

Discord on Windows does not need administrator rights to install, because it lives inside your profile. The cost of that design is that the updater works with many small files in %localappdata%\Discord, with version folders named like app-1.0.xxxx. If one of those files is half written, or something holds it open, the updater cannot move to the new version and retries. That is why the same screen can come back after every reboot.

Method 1: end every Discord process, then run it again

A leftover background process is the simplest cause and the cheapest to test.

1. Press Ctrl + Shift + Esc to open Task Manager. If it opens in a compact view, click More details.
2. In the Processes tab look for Discord, Update and anything with Discord in the name. Select each one and click End task.
3. Also check the Details tab for Discord.exe and Update.exe and end them.
4. Start Discord again from the Start menu.

If the update now completes, you are done. If you see the same loop, continue.

Method 2: clean reinstall (the fix that solves most cases)

This removes the damaged files and installs a fresh copy. Your account data is untouched.

Method 3: Installation has failed on the fresh installer

If the installer itself says Installation has failed, one of three things is still in the way.

• Leftovers: the Discord folder was not fully deleted. Open %localappdata% again and check that no Discord or SquirrelTemp folder remains. Delete them.
• Permissions: right click the installer and choose Run as administrator once. This is a test, not a permanent habit. If it works, your normal account likely lacks write access to your own profile folder, which deserves attention (see Method 5).
• Security software: antivirus can quarantine files while they are unpacked. See Method 4.

Method 4: security software, firewall and download blocking

Third party antivirus suites and "internet security" bundles sometimes treat a self updating app as suspicious, especially one that downloads and replaces executables in a user folder. Open your security program's quarantine or history and look for Discord or Update.exe entries. If you find one, restore it and add the folder %localappdata%\Discord to the exclusions list. Microsoft Defender users can do this under Windows Security, Virus and threat protection, Manage settings, Exclusions. If you are shopping for protection that behaves better with everyday apps, our free antivirus comparison covers what to expect, and antivirus versus VPN explains why these tools can overlap.

Firewalls and filtering DNS can also block Discord's content servers. If you use a custom DNS service, a router with parental filtering or a corporate firewall, test on a different network, such as a phone hotspot. If the update works there, the filter is your cause. Our guide to DNS server not responding shows how to reset DNS to automatic.

Method 5: permissions on the profile folder

If administrator rights make the installer work, your own folder may have broken permissions, which can happen after a profile migration, a restore from backup, or a security tool that changed access rules. Right click the Discord folder in %localappdata% before deleting it, choose Properties, then Security, and check that your user has Full control. If you cannot edit it, a technician can reset ownership in a few minutes. Do not apply permission changes to large parts of your profile without guidance, because that can create new problems.

Method 6: repair Windows system files if multiple apps fail

If other apps also fail to install or update, the cause is likely Windows itself. Open Terminal as administrator and run sfc /scannow, wait for it to finish, then run DISM /Online /Cleanup-Image /RestoreHealth and restart. These are Microsoft tools that check and repair system components. Our guide on Windows Update stuck or failing explains them in more detail.

Windows quick reference

What the Windows logs can tell you

The Windows installer typically leaves a log file named SquirrelSetup.log in the Discord folder under %localappdata%, and the updater writes messages there as well. Open it in Notepad and scroll to the end. Look for words such as "access denied", "unable to delete", "sharing violation" or "network". An access denied line points to permissions or antivirus. A sharing violation points to a process holding a file. Network wording points to DNS, proxy or connectivity. Exact wording varies between Discord builds, so use it as a clue, not as a diagnosis.

Mac: fix Discord Update Failed and Installation has failed on macOS

On a Mac, Discord is a normal application bundle, Discord.app, that should live in your Applications folder. Update failures here usually come from running it from the wrong place, from a copy your user is not allowed to modify, or from damaged support files in your Library folder. Move a fresh copy into /Applications and clear the old support files, and the problem normally disappears.

Why the Windows loop fixes do not apply to a Mac

There is no %localappdata% on macOS, and the Windows updater behavior does not carry over. Many Windows fix lists tell Mac users to delete folders that do not exist on their computer. On macOS the program is the Discord.app bundle, usually in /Applications, and the user data lives under ~/Library. That is where we work.

Step 1: quit Discord fully

1. Click the Discord icon in the menu bar if it shows, and choose Quit Discord.
2. Press Command + Option + Escape to open Force Quit Applications, select Discord if listed and click Force Quit.
3. For a thorough check, open Activity Monitor (Applications, Utilities), search for "discord" and quit anything that remains.

Step 2: check where Discord is installed

This single point explains many Mac cases. If you opened Discord straight from the downloaded disk image, from the Downloads folder or from the Desktop, macOS may run it from a temporary read only location and the updater cannot replace itself. In Finder, open Applications (Shift + Command + A) and look for Discord. If it is not there, or if you have more than one copy, that is the problem. Drag the extra copies to the Trash, eject the disk image if one is still mounted, and keep only the copy in Applications.

Step 3: remove the old app and the support files

The Library folder is hidden by default, so use the Go menu.

Step 4: handle Gatekeeper and "damaged" warnings

If macOS reports that Discord "is damaged and can't be opened" or that the developer cannot be verified, the cause is usually an interrupted download or a quarantine flag on a bad copy. Download the installer again, over a stable connection, directly from discord.com. Avoid copies shared by chat or file hosting sites. Do not disable Gatekeeper system wide to get around the warning. If you have verified that the file came from the official page and macOS still refuses it, open System Settings, Privacy and Security, and look for an Open Anyway option near the bottom. Apple documents these startup and security features on its support site, linked in the sources below.

Step 5: permissions on the Applications folder

On a Mac with a standard (non administrator) account, the app in /Applications may be owned by an administrator, so Discord cannot overwrite itself during an update. Signs include being asked for an admin password every time Discord updates, or an update that fails only for one user on a shared Mac. The cleanest fix is to reinstall while signed in as an administrator, or to install Discord for your own user by placing it in a ~/Applications folder you create. Recent macOS versions also have an App Management privacy setting in System Settings, Privacy and Security, that can restrict apps from modifying other apps. If you use a tool that blocks this, expect update problems.

Step 6: Mac specific extras

• Low disk space: a full startup disk is the number one hidden cause on older MacBooks. Free at least 5 to 10 GB if you can.
• Security tools and profiles: work managed Macs with an endpoint tool or content filter can block downloads. Test on a personal hotspot.
• Old macOS versions: Discord stops supporting very old macOS releases over time. If your Mac cannot run the current macOS, the desktop app may refuse to update, and the web app at discord.com/app is the fallback. Discord does not publish a firm cutoff that we could confirm today, so check discord.com/download for current system requirements.
• Apple silicon and Intel: use the Mac download from the official page and let it pick the right build. Do not copy an app from another Mac.

Mac troubleshooting table

If your Mac also feels slow, freezes with a spinning wheel, or shows a kernel panic, the update error may be a symptom of a bigger issue. Our pages on the MacBook slowdown are a good next read.

Linux: fix Discord update prompts, .deb, Flatpak and snap installs

On Linux there is no single Discord updater, because the result depends on how you installed it. A .deb or tarball from discord.com usually needs a newer download when a new version is required, while Flatpak and snap update through their own tools. Identify your install type first, then use the matching steps below.

Step 1: find out how Discord was installed

Run these commands in a terminal and see which one answers.

• dpkg -l | grep -i discord lists a Debian or Ubuntu package install.
• flatpak list | grep -i discord shows a Flatpak install.
• snap list | grep -i discord shows a snap install.
• which discord shows the launcher path, which helps spot a manual tarball install under /opt or your home folder.

.deb on Debian, Ubuntu, Linux Mint and Pop!_OS

Discord publishes a .deb on its download page. When Discord requires a newer version than the one installed, the desktop app can show a screen asking you to update and it may not install the new package by itself. The dependable fix is to download the latest .deb from discord.com/download and install it over the old one:

sudo apt install ./discord-*.deb

Using apt rather than dpkg directly lets the system pull any missing dependencies. If apt reports a broken package, run sudo apt --fix-broken install, then try again. After the install, start Discord from the application menu. If the old version still launches, check that which discord points to the packaged location and not to a stale copy in your home folder.

Flatpak (Flathub)

The community maintained Flatpak is listed on Flathub. Update it with:

flatpak update com.discordapp.Discord

If the update loops or fails, quit Discord and run flatpak repair --user (or without --user for a system install), then update again. As a last resort, remove it with its data and reinstall: flatpak uninstall --delete-data com.discordapp.Discord, then flatpak install flathub com.discordapp.Discord. The delete data option removes local settings for the Flatpak only. If you are unsure, skip it and try the repair first.

snap

Run sudo snap refresh discord. If the refresh is held or fails, check snap changes for a stuck task and the error text. A snap that is being refreshed while Discord is open can fail with a busy message, so quit Discord first. The snap store entry is maintained separately from Discord, so versions can lag behind the official .deb. If you need the newest build and the snap lags, use the .deb or Flatpak instead.

Tarball or manual installs

If you unpacked the .tar.gz from the download page, update means downloading the new tarball and replacing the old folder. Back up nothing special: user data is in ~/.config/discord, separate from the program folder. Quit Discord, remove or rename the old program folder, unpack the new one in the same place and update your launcher if the path changed.

Clear damaged local data on Linux

If Discord crashes at launch or keeps failing after a reinstall, move its config out of the way instead of deleting it, so you can undo it:

mv ~/.config/discord ~/.config/discord.bak

Start Discord. If it works, your settings were corrupted, and you can delete the backup later. Flatpak keeps its data under ~/.var/app/com.discordapp.Discord.

Wayland, graphics and sandbox issues

Some Linux users see a blank window or an instant crash that looks like an update failure but is really a graphics or sandbox problem, particularly after a driver update or on a new Wayland session. Try launching from a terminal to read the output: discord. Errors that mention GPU, sandbox or GLib point to a graphics stack issue. A common experiment is to start Discord with GPU acceleration disabled, using the flag --disable-gpu, which Chromium based apps generally accept. If that fixes it, update your graphics drivers. Because flags and behavior change between versions, treat this as a test and not as a permanent configuration.

Linux summary table

The STATUS_BREAKPOINT crash: what it is and what to try

STATUS_BREAKPOINT is a Windows exception code (0x80000003) that Chromium based programs can report when their renderer hits an unexpected stop. With Discord it normally means a damaged install, a graphics driver or hardware acceleration issue, or unstable memory, and it is not a sign that your account has a problem. Because we could not confirm one official cause, the steps below go from the cheapest test to the most involved.

Where people see it

The code is most often reported in Chrome, Edge and other Chromium browsers, and some Discord users report seeing it in Discord's embedded web view or in the window that appears after a crash. It can appear right after an update fails halfway, which is why people search for it next to "Discord update failed".

What to try, in order

1. Restart the computer and open Discord again. A one-off crash often does not return.
2. Do the clean reinstall from the Windows section. A half updated folder is the most likely reason.
3. Turn off hardware acceleration if Discord opens for a moment: User Settings, Advanced, Hardware Acceleration. If it will not open, users report that a setting named "enableHardwareAcceleration" in the settings.json file under %appdata%\discord can be set to false while Discord is closed. Confirm the exact key name in your own file before editing, and make a copy first.
4. Update the graphics driver from your GPU maker or your laptop manufacturer. Outdated drivers are a classic source of renderer crashes.
5. Run a memory check if crashes also happen in other programs: search Windows Memory Diagnostic in the Start menu and restart to test. Random crashes across apps point to hardware.
6. Check for overlays: screen recorders, game overlays and RGB or monitoring tools inject into other programs and are a known source of Chromium crashes. Close them and test.
7. Try a different channel: install Discord PTB from the official download area to see whether the problem is tied to the stable install or to the system.

If STATUS_BREAKPOINT also appears in your browser on every page, the cause is likely the browser or the system rather than Discord, and the same checks (driver, memory, overlays) apply there.

When a clean reinstall does not help: network, DNS, VPN and proxy causes

If a fresh install still fails to update on any system, suspect the path between your computer and Discord: DNS, a VPN, a proxy, a router filter or a firewall. Test on a different network first, because that one test splits "my computer" from "my network" in two minutes.

The phone hotspot test

Connect the affected computer to your phone's hotspot and launch Discord. If the update completes, your usual network is blocking or breaking the download. If it still fails on the hotspot, the cause is on the computer (disk, permissions, security software, damaged system files). This test is more useful than any amount of reading about error strings.

DNS

Your computer asks a DNS server to translate names like discord.com into addresses. A slow, failing or filtering DNS makes downloads time out. Switch to automatic DNS from your router first. If you already use a public DNS service, switch back to automatic as a test. On Windows, open a terminal and run ipconfig /flushdns. On Mac, flushing DNS differs by macOS version, so a restart is the simplest equivalent. Our guide on DNS_PROBE_FINISHED_BAD_CONFIG and the page on DNS server not responding cover DNS repair in more detail.

VPN, proxy and "secure DNS" browser features

A VPN changes the route and sometimes the DNS your system uses. Some VPNs block or throttle certain content networks, and a VPN that disconnects mid download breaks the update. Turn it off, test, and if the update works, set the VPN to split tunneling for Discord or choose a different server. On Windows, check Settings, Network and internet, Proxy, and make sure no manual proxy is set unless your employer requires it. A leftover proxy from a removed program is a quiet cause of failures in many apps at once.

Work, school and shared networks

Managed networks often filter chat services. If Discord is blocked on purpose by your employer or school, an update loop is not a bug and you should not try to bypass the policy. Ask the network administrator. If you run a small business and want to decide whether staff should use Discord at all, that is a policy decision that belongs in your written IT rules.

Router level problems

Routers with built-in "family" filters, outdated firmware or an overloaded DHCP table can cause strange partial failures. Restart the router and modem by unplugging them for 30 seconds. If one device fails while others work, the router is rarely the cause, but if every device fails on updates, check the router's filter and security pages.

Advanced checks for stubborn cases

When the clean reinstall and network tests both fail, the cause is almost always something about the machine itself: a failing drive, a damaged user profile, aggressive security software or corrupted system components. These checks separate those four.

Create a new user account as a test

Create a temporary standard user on the computer, sign in to it and install Discord. If it works there, your original profile is damaged or restricted. That is useful to know: rebuilding or migrating a profile is a job for a technician because it can affect files, licenses and settings.

Check the drive

On Windows run chkdsk C: /scan from an administrator terminal, which checks the file system without scheduling a restart. On Mac open Disk Utility and run First Aid on the startup volume. On Linux use the tools your distribution recommends. Drives that report errors should be backed up immediately, because a drive that fails to write updates may soon fail to write anything. See our explanation of data recovery versus data backup if you have no recent backup.

Boot into a clean state

On Windows, a clean boot (using msconfig to hide Microsoft services and disable the rest) shows whether a startup program interferes. On Mac, Safe Mode (hold Shift at startup on Intel, or use the startup options on Apple silicon) disables third party extensions and clears some caches. If Discord updates in these modes, a third-party tool is your cause and you can re-enable items one at a time.

Try another channel

Discord PTB (Public Test Build) and Canary are separate installs with their own folders. If PTB installs and updates but the stable build does not, the problem is tied to the stable folder, which supports the clean reinstall theory. They are for testing and can have more bugs, so treat them as a temporary workaround.

Capture the evidence before you ask for help

If you reach support, whether Discord's or ours, a clear report saves hours. Collect these items:

Three realistic scenarios

The examples below are illustrative, not real client cases. They show how the same error message can have three different causes, and how the right order of checks saves time.

Realistic scenario 1: the gaming PC with an old antivirus

A student in Montreal has a Windows 11 desktop. Discord shows Update Failed every morning. He has reinstalled twice, but the loop returns after about a day. The third-party antivirus subscription has an "aggressive heuristics" setting turned on, and its quarantine log shows Update.exe from the Discord folder flagged three times. Restoring the file and adding %localappdata%\Discord to the exclusions list ends the loop. Time spent after finding the log: about 8 minutes. The two earlier reinstalls were wasted because the real cause was not the install at all.

Realistic scenario 2: the MacBook running from a disk image

A freelancer opens the Discord disk image and double clicks Discord inside it, every time, for weeks. The first update fails and from then on she sees an update message she dismisses until Discord stops opening. In Finder, Applications has no Discord. Dragging the app into Applications, ejecting the image, and trashing the old ~/Library/Application Support/discord folder fixes it. Time: about 6 minutes, including the sign in with two-factor authentication.

Realistic scenario 3: the small team with a network filter

A five person design shop in Laval uses Discord with clients. After the office router firmware update, three of five Windows PCs show Installation has failed on the new Discord version, while two work. All five are on the same Wi-Fi. A hotspot test shows the failing PCs update normally on the phone network. The router's built-in filter had a category setting changed by the update. Changing the filter back and rebooting the router restores updates. The takeaway: a problem across several machines at the same site points to the network, not to Discord.

What this costs: do it yourself versus paying for help

Fixing a Discord update failure yourself costs nothing but 10 to 30 minutes. Paying a technician only makes sense when a clean reinstall did not work, several devices are affected, or the error is a symptom of a deeper Windows, Mac or network problem. Prices below are in Canadian dollars and are rough ranges, not quotes.

A single Expert Consultation is a flat 119.99 $ CAD for up to 60 minutes, and we connect remotely so you can watch each step. For most people, the update failure is only the first visible sign. In a session we typically also look at startup programs, free disk space and security settings so the problem does not return. That said, if this guide fixes your problem, you do not need us.

How to stop Discord update failures from coming back

Prevention is mostly about keeping the install location writable, the disk healthy and the security software informed. A few habits remove the large majority of repeat failures.

• Install from discord.com only, and on Mac keep the app in Applications, not in Downloads or a disk image.
• Do not force quit Discord during an update. If you see the small updating window, let it finish.
• Keep 10 percent or more of your drive free. Updates and caches need room.
• Add the Discord folder to security exclusions if your antivirus has quarantined it once.
• Keep the operating system updated. Old systems eventually stop being supported by modern apps.
• Restart weekly. Many "locked file" problems vanish with a normal restart.
• Know your web fallback. Bookmark discord.com/app and keep your two-factor backup codes in a safe place.
• Watch discordstatus.com when something looks wrong everywhere at once.

Common mistakes to avoid

When to call a professional

Call for help when you have done a clean reinstall and the hotspot test, and Discord still fails, or when several programs misbehave at once. At that point the problem is the computer or the network, and guessing makes it worse. A remote technician can read the installer logs, check permissions, security software and disk health, and fix the cause while you watch.

Signs that you should stop troubleshooting alone:

• Other apps also fail to install or update.
• Your drive reports errors or the computer is unusually slow.
• You get permission or administrator errors you cannot explain.
• The computer is a work device with a management or security tool installed.
• Several computers at the same site have the same problem.
• You suspect that you opened a malicious file or link.

IT Cares has provided remote and on-site IT support in Quebec and across Canada since 2014. You can reach a technician at 1 (888) 711-9428 or book a remote session and we connect to your device securely. The Expert Consultation is 119.99 $ CAD for up to 60 minutes.

Your Discord update repair checklist

This is the whole process in one place. Work from top to bottom and stop as soon as Discord updates.

Summary

Discord Update Failed and Installation has failed are local installation problems, and they are fixable on Windows, Mac and Linux without losing any account data. Rule out an outage and use the web app, remove the local folders, install a fresh copy from discord.com, and then look at security software and the network if the problem returns. For the Windows retry loop in particular, keep our dedicated Discord Update Failed loop page bookmarked. If voice is your next problem, the guide on Discord mic not working is the sensible next read, and the error pages for error 1105 and error 20012 cover other Discord messages.

Frequently asked questions

Related guides

• Discord Update Failed loop: 7 Windows fixes
• Discord error 1105
• Discord error 20012
• Discord mic not working: how to fix it
• Windows DNS server not responding
• Windows VPN connection failed
• Best free antivirus in 2026
• Antivirus vs VPN: do you need both?
• How to speed up a MacBook
• How to speed up Windows 11
• Windows Update stuck or failing

Sources and official references

Last verified: October 1, 2026

• Discord Status (live service status)
• Discord download page (official installers for Windows, Mac and Linux)
• Discord on Flathub (Flatpak package page)
• Apple Support: Mac startup and system information resources