"Something went wrong" error in Discord on Windows 11 24H2

This error is a pain, I get it

You open Discord after that Windows 11 24H2 update and bam — "Something went wrong" with a sad Wumpus. I've seen this hit right after a restart, usually when Discord tries to check for updates but chokes on corrupted cache files. Let's fix it fast.

Fix 1: Clear the cache (works 90% of the time)

Discord stores temporary files in a hidden folder. If those get corrupted — and they often do after a major OS update — the app errors out before it even loads. Here's what to do:

1. Press Win + R, type %appdata%, hit Enter.
2. Find the discord folder, open it.
3. Delete the Cache, Code Cache, and GPUCache folders. Don't delete the whole discord folder — just those three.
4. Restart Discord. It'll recreate the cache and should load fine.

If you're on Windows 11 24H2, you might need to run Discord as admin. Right-click the shortcut, select Run as administrator. Some security changes in 24H2 block cache writes for non-admin processes.

Fix 2: Reinstall Discord completely

If clearing cache didn't work, the updater itself is likely broken. The "Update.exe" or "Discord.exe" in your AppData folder may have been flagged or modified by Windows Defender. Do a full wipe:

1. Close Discord. Check Task Manager for leftover processes.
2. Go to Settings > Apps > Installed apps on Windows 11 24H2, search for Discord, click the three dots, and choose Uninstall.
3. After uninstall, open File Explorer, navigate to %localappdata%\Discord and delete that folder too. Yes, this is overkill. But those leftover files cause the error on reinstall.
4. Download the latest installer from discord.com/download. Run it as admin.

Fix 3: Disable hardware acceleration

This is the "skip the fancy stuff" fix. Discord uses your GPU to render the interface. On some Windows 11 24H2 builds (especially with NVIDIA drivers 552.44 or later), this causes a conflict that produces the "Something went wrong" error. You'll need to do this before the error appears, so do it after a successful launch from Fix 1 or 2.

1. Open Discord, click the cog icon (User Settings) next to your username.
2. Scroll to Advanced under App Settings.
3. Toggle Hardware Acceleration off. Discord will ask to restart. Let it.
4. Test by closing and reopening Discord a few times. If it stays stable, leave this off.

Less common variations

"Something went wrong" on startup with error code 0005

This is an access denied error. Discord can't write to its own cache folder because the folder permissions got messed up. Right-click the %appdata%\discord folder, go to Properties > Security, make sure your user account has Full control. Apply, then retry.

Error after a voice call

If the error shows up mid-call — especially after switching audio devices — the culprit is often the audio subsystem in Discord crashing. Go to User Settings > Voice & Video and set Audio Subsystem to Legacy instead of Standard. Restart Discord.

Black screen with "Something went wrong" after overlay

This one's tied to game overlays. In Discord, go to User Settings > Game Overlay and turn it off. Then disable overlay per-game in the same section. Reboot your PC. I've seen this on Valorant and Fortnite specifically.

Prevention tips

• Don't run Discord as admin permanently. It breaks cache permissions over time. Only use admin for the initial launch after a clear.
• Update your GPU drivers every few months. Stale NVIDIA or AMD drivers are the #2 cause of this error after cache corruption.
• Set Discord to not auto-update? No — that's a bad idea. Let it update, but after a Windows update, always clear the cache manually before launching Discord for the first time.
• Keep Windows 11 24H2 and Discord builds in sync. If you've paused Windows updates, Discord may try to use features that aren't present. Install the latest Windows quality updates.

That's it. Nine times out of ten, clearing those three cache folders does the job. If you're still stuck, try the reinstall. And if you disabled hardware acceleration, leave it off until Discord patches the conflict for good. You'll be back in your servers in five minutes.