{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Bearbeitet von Lord Snaxx:
1/16/2026 5:44:58 PM
2
Weasel (Adept)
Okay, at this point I have exhausted every network test and fix.
The issue seems to be locking down specific devices.
I have tested multiple networks, both broadband and hotspots on mobile data
I have checked router settings and performed network tests, all of which don't come back with any packet loss which Bungie suggest. Again, everything else on PC works such as streaming and other MMO's with similar network requirements to Destiny.
If I load up Destiny 2 via PS5 on WiFi, it works with zero issues or latency, however, if I try Destiny 2 on PC on the same network, through WiFi or Ethernet, it boots me out after 40 seconds with the Weasel error. There is clearly a pattern here and multiple users are experiencing the same issue. It seems to be a restriction is placed on certain hardware? But then again, I can sign into Destiny 2 on PC for roughly 40 seconds, move things between character and vault before I am inevitably kicked.
This needs addressed ASAP.
-
i may have found the solution to this problem at least it worked for me So what you're gonna wanna do is go to ur settings in windows, then go to "system", then you're going to go to "recovery", then reinstall ur current version of windows with all your (apps, files and settings being preserved) follow the steps from there let it reset ur pc or do it yourself once its done updating/downloading then try launching d2 once its done that should be it hope it works for you all cause this s*** pissed me off. An i suppose it wasn't bungies fault like i had claimed (this time at least)
-
6 AntwortenHi there, Thank you for reaching out to us again. We understand that you're still experiencing the Weasel error code. We're sorry to hear how it's persisted despite the troubleshooting steps you've taken. For our investigation into the occurrence of this error code, could you kindly let us know which region you're playing the game in, as well as which ISP you're with? We'll then review.
