{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
5/31/2026 3:48:01 AM
6
Steam version only gets WEASEL within 1 minute, Epic version works fine
Since the latest DLC update, Destiny 2 on Steam always returns WEASEL within 1 minute.
Important findings:
- Steam version only
- Epic version works normally
- Happens on character select screen as well
- Happens on all characters
- DIM works normally
- Bungie.net works normally
- Tried a different Steam account
- Tried a different Windows user account
- Tried mobile tethering
- Reinstalled Destiny 2 completely
- Reinstalled Steam
- Deleted BattlEye and reinstalled
- Disabled IPv6
- Removed old VPN adapters
- Updated Intel LAN driver
- No crash logs
- No BattlEye errors in Event Viewer
The game does not crash.
It simply returns to the title screen with error code WEASEL.
This started around the latest DLC release.
-
Just wanted to post an update in case it helps anyone else. After trying pretty much everything (network troubleshooting, tethering, VPN, file verification, BattlEye reinstall, different Steam account, new Windows user account, etc.), the issue appears to have been resolved by using the Windows 11 repair option: Settings → System → Recovery → Fix problems using Windows Update This performs a repair installation of Windows while keeping files and applications intact. Before doing this, I would consistently get a WEASEL error within about 1-2 minutes of pressing "Start." I could reach character selection, but would disconnect shortly afterward. After the repair completed, I was able to enter the Tower and play in Sorrow's Harbor for over 10 minutes without any disconnects. I'm still testing, but so far this is the first thing that has made a difference. Thank you to everyone who took the time to help troubleshoot this issue, review my DxDiag report, and suggest possible causes. I really appreciate all the assistance.
-
10 RepliesCan you link a Dxdiag report? (Upload it on a site like https://pastebin.com/ and link it here).
-
1 Replyare you on windows 10? im having the same thing on windows 10 and wondering if thats why
-
Same issue, this NEEDS to be addressed. Ive been playing since beta and have never experienced anything like this. From the data I've gathered IPv6 enabled temporarily solved it, VPN also helped for a moment. But the issue reappears with no reason. Epic Games version works, but Im not repurchasing all DLC just to be able to play the game.
-
Edited by BNGHelp3: 6/1/2026 4:29:39 PMHi there, Thanks for reaching out. We're sorry to hear these Weasel errors are still affecting you! If you've already gone through all the usual, network-related troubleshooting, we have a few potential solutions from other affected community members that might help. We recommend launching Destiny 2 after each attempted fix to see if each one has an effect on the situation. 1) Ensure that BattlEye is whitelisted in your chosen antivirus software. 2) Repair the integrity of your Destiny 2 game files via the steps on [url=https://help.bungie.net/hc/en-us/articles/4405096052244-Error-Code-MARMOT]this page[/url]. Please go through the steps for Steam specifically, and go through the Advanced Steps if the initial ones don't help. 3) As a last resort option, you can try fixing the issue via Windows Update. To do so, go to Settings -> System -> Recovery -> Fix problems using Windows Update. Please keep us posted!
-
Exact same boat. It works fine on Epic, but not on Steam. I never used to encounter this.
