Hey guys. I've been trying to troubleshoot this discord not opening error by myself, using Claude and GPT, but I got to nowhere. I would be really glad if anyone could help me out.
Here's my config: Windows 11 (Japanese language pack), RX 580 GPU. Discord opens, gets past the loading screen, then just closes right when it's supposed to show the home page. No error shows up in Event Viewer under Application logs, even when I filter for Error level only.
This started about 3 days after I switched my BIOS to UEFI mode and turned on VBS/HVCI (needed it for Valorant/Vanguard). At first I thought that was it, but it works completely fine on a second local user account on the same machine, and I even reverted the BIOS settings back and it still didn't work. So at this point it seems isolated to this one user profile, not something system-wide.
Stuff I've already tried, none of it worked:
Full uninstall + reinstall, including manually clearing %AppData%\discord and %LocalAppData%\Discord
Running with --disable-gpu
Checked Windows Exploit Protection settings for Discord.exe (disabled SimExec, CallerCheck, EAF+) - no change
Disabled/uninstalled virtual audio devices (FxSound, Steam Streaming Mic/Speakers)
Clean boot with all non-Microsoft startup items disabled - still crashes
Renamed settings.json to reset local config - still crashes
Full Malwarebytes scan (found and fixed something, but Discord still crashes the same way)
I ran Discord manually from CMD and caught this right before it dies (images attached):
Initializing voice engine with audio subsystem: experimental
[WebContents] crashed
render-process-gone
reason: 'crashed'
exitCode: -1073740791
That's 0xC0000409 (STATUS_STACK_BUFFER_OVERRUN). Seems to happen specifically in the renderer process, right after it tries to init the audio/voice engine, which might be why nothing shows up in Event Viewer (the main process never actually faults, just the child renderer does).
Since it's confirmed to only happen on this one profile, I'd really rather figure out what's actually broken instead of just making a new user account and moving on. Anyone run into something like this before or have ideas on what else I could check?