I had this exact same thing after the December patch. From what I gathered, error 3002 usually means the launcher can’t authenticate or connect to the Discord servers properly often due to corrupted update files. Sometimes Windows firewall or a VPN interferes causing the app to fail during startup.
Try deleting %AppData%/Discord and %LocalAppData%/Discord, then reinstall. That fixed it for me.
Same here! On my end the issue was actually conflicting antivirus software. My AV was blocking parts of Discord after the update. Whitelisted Discord in my antivirus and boom no more error 3002. You might want to check that.
Just to add error 3002 can also pop when your internet connection is unstable or if specific ports Discord relies on are blocked. I had wonky ISP routing, and Discord failed to authenticate because the handshake kept timing out. Switched networks and it launched fine.
Interesting so does this error mean it’s always a network/auth issue? I don’t use a VPN or firewall tweak. Could it still be Discord’s servers acting up?
Not always, but yeah it can be server side. When Discord pushes a bad update, some builds fail to launch globally. You can check Discord’s status page or Twitter. If lots of people suddenly have error 3002, then it’s likely a backend deployment issue just wait for the hotfix.
If you’re on Windows, also try resetting the Discord app through the OS settings:
Settings → Apps → Discord → Advanced options → Reset
That’s different from uninstall/reinstall since it nukes the app state entirely. Helped me once when files kept reappearing.
Just throwing this out there if you’re on a corporate network or school Wi-Fi, proxy/firewall rules can block authentication endpoints. Tried logging in from mobile hotspot and Discord opened instantly. That narrowed it down for me.
Tried deleting AppData and whitelist stuff but still getting error 3002.
Is there a way to force Discord to start in a diagnostic / safe mode? Something like command line flags?
You can try starting Discord with --disable-gpu or --no-sandbox from the terminal/Run prompt — some Electron bugs cause startup failures. Not a guaranteed fix for error 3002 specifically, but worth a shot if other steps fail.