Discord stuck checking for updates? Check status first

Start with live status and the browser client

Checking for Updates is a desktop splash state, not a root-cause message. The same screen can appear during a Discord incident, on an unsupported operating system, with a stuck desktop process, when the updater path is blocked, or after Discord-only local data is damaged.

Open Discord Status from a browser. Check the Desktop, Web, API, Gateway, and related components. When this guide was checked on September 17, the page listed a call-connection incident as resolved. That incident is not evidence of an updater-loop cause. Status changes, so use the live page rather than this article's snapshot.

Next, try Discord in a supported browser without changing desktop files. Compare the result:

• Status reports an incident and browser or mobile also fails. Wait and monitor. Local cleanup is unlikely to repair a service incident.
• The browser works but the desktop app loops. Focus on operating-system support, desktop processes, local Discord state, and the updater path.
• Discord's website and browser client fail only on one network. Record the network comparison. Do not jump straight to DNS, VPN, proxy, router, or firewall changes.
• Only one account fails after the app opens. That is an account or sign-in branch, not the pre-launch updater loop.

Record the exact state before cleanup

Write down the wording and how it changes. Does the window remain on Checking for Updates, move to Starting, open blank, close and reopen, or fail only when the installer runs? Record how long it stays there and whether a full quit changes the next launch.

Save the operating system version, processor architecture, Discord build if visible, recent app or OS changes, browser result, status result, and whether another network changed the behavior. A nearby update is a clue, not proof that the update caused the loop.

Take a screenshot before removing local state. If you save logs, redact tokens, email addresses, usernames, server names, private messages, machine names, home-folder paths, and network identifiers. Do not publish raw logs.

Check the current operating-system boundary

On Windows, Discord's current requirements list Windows 10 or later for the desktop client. On Mac, the dedicated support notice now requires macOS 13 or later for updates and support.

If the Mac still runs macOS 12, do not treat repeated update checks as ordinary cache damage. Check whether that Mac supports a newer macOS release and back up before upgrading. If it cannot upgrade, use Discord's browser client when the browser meets Discord's requirements.

Do not install an old, patched, or mirrored Discord build to hold an unsupported system in place. Do not use compatibility settings to make a current client look supported. Unsupported software stops receiving normal updates and makes later troubleshooting less reliable.

Fully quit Discord and preserve what matters

Close Discord from its tray or menu, then confirm no Discord process remains in Task Manager on Windows or Activity Monitor on macOS. A window that disappears can leave the updater or another Discord process running.

Wait 30 seconds, then launch Discord once. If it opens, stop changing files. Record that a full process exit changed the result. That supports a stale-process branch, but it does not prove the local files were corrupt.

If the loop returns, keep the screenshot, exact state, OS version, browser result, status result, and any redacted logs you plan to send to Discord Support. Close every Discord process again before touching Discord-owned folders.

Follow Discord's clean-install steps

Discord documents a clean-install path for installation and update problems. On Windows, it names the Discord folders under %AppData% and %LocalAppData%. On macOS, it names the Discord folder under ~/Library/Application Support.

Remove only the Discord-owned folders named by Discord. Do not delete broad AppData, LocalAppData, Library, browser, profile, certificate, registry, or network folders. On a managed computer, stop and ask the administrator before removing application data.

Restart the computer after the documented cleanup. Download a fresh installer only from Discord's official download page. Install it once, then record whether the updater advances, the app opens, or the same loop returns.

Keep antivirus, firewall, Gatekeeper, certificate validation, and endpoint policy enabled. Discord's general troubleshooting page contains some broad suggestions, but this guide does not recommend disabling security controls to make an updater run.

If Discord still checks for updates forever

Do not repeat the cleanup. Preserve the unchanged result. Include the operating system, architecture, status result, browser result, exact splash sequence, duration, process-exit result, official reinstall result, and any safe network comparison in a Discord Support request.

If the browser also fails and Discord Status is clear, test another ordinary network only when that comparison is allowed. A changed result can point to the network path, but it does not prove a specific DNS provider, ISP, proxy, VPN, firewall, or certificate is responsible.

Do not use a VPN, proxy, DNS change, hosts-file edit, router reset, firewall exception, or security shutdown as a universal fix. On school, work, or managed networks, the administrator owns those controls.

If Discord opens but later stops responding, use the single-app hang guide. If websites and other services also fail on Windows, use the connected-without-internet guide. Those paths answer broader failures and should not be mixed into a desktop updater loop.

Where OmniMend fits

On a supported Windows x64 PC or Apple Silicon Mac, OmniMend can help organize local system and application evidence around this problem. Keep the Discord status result, exact updater state, browser comparison, OS and architecture, process result, official reinstall result, and redacted logs together for support.

OmniMend does not update Discord, restore Discord service, bypass compatibility checks, change network policy, recover an account, disable security controls, or guarantee that the desktop app will open. It does not make an Intel Mac or unsupported operating system a supported OmniMend host.

If you want a separate evidence record on a supported device, review OmniMend's diagnostic scope or download OmniMend. Read the privacy information before sharing any report.