I'm trying to gather information from players who have been receiving the Weasel Error that began on January 14, immediately following the Destiny 1 Maintenance update. If you are a player who has been experiencing this issue, please read this post and then leave a comment below. The issue has been affecting PC players using Steam or the Xbox Windows app. PC players using the Epic Games launcher, as well as Xbox One & PlayStation 4/5 console users, seem to be unaffected. Starting January 14, as soon as Bungie released the D1 update, affected players would receive the error roughly 30 seconds after logging in. It is a 100% reoccuring issue, and these players have been completely unable to play Destiny 2 using Steam or the Xbox Windows app. Bungie still has not acknowledged this problem. Now, this could be because they are working on the issue in silence, the issue has flown under their radar because it is not affecting enough people, or they are simply ignoring it altogether. I'm looking to accomplish two things: the first is to gather information from affected players, and the second is to urge everyone to make posts on Bungie X accounts, especially @Bungie & @Destiny2Team. If you are a player receiving this issue, please comment below with your region, ISP, platform, when the issue began, if you have Cross-Save enabled, which is your main account, if you were able to solve it, if you attempted Bungie's basic and advanced troubleshooting steps, and any other information you think might be relevant. If you did in fact manage to fix this issue yourself, please list it below as well so other players might be able to give it a shot. I urge everyone, even those that dont have this problem, to go make posts about it all over their X accounts to increase exposure to the problem.