Didn't find what you were looking for?

New post
Bungie Answered

Stuck on Weasel Error code at Launch.

Hi.

Description of the issue :

During the last exfil (red card) on outpost, while playing with Rook, my game disconnected with an error code called monkey at the last seconds of the run during the extraction animation.

After multiples attempts, i couldn't return to the lobby, so i choose to get to the main menu.

Since, i can't manage to get to the home menu of the game (when you see the shell you choose) since i'm blocked by the same WEASEL error code over and over at the first menu (just after you have to left click in order to get to the game).

I tried to reinstall the game, verify game files, disconnect from steam, reset steam guard and all of the steps of the bungie's networking guide and it doesn't work at all.

Is there any fix ?

My Bungie ID is : Mandisis#1693

Platform : Steam

Rough Date : 1 April 2026 approx 23h00-15 UTC+2

Thanks.

0

Comments

2 comments
  • Hello there,

    Thank you very much for reaching out to us. I'm sorry to hear that you are seeing these error codes in the game. While some of these error codes are being actively monitored and investigated, these codes usually appear when there's some connectivity issues in-game. As you've already attempted most of the troubleshooting available, while we continue to investigate the issue, we'd recommend going through our Advanced Network Troubleshooting Guide to see if it helps. Lastly, your Internet Service Provider may have some additional troubleshooting that may help mitigate any issues that may be occurring locally..

    1
  • Update : After one hour, i've managed to get back to the game.

    A ginger error code appeared at the last try, then i was asked to choose between return to the main menu or go to the past lobby (which wasn't possible obviously because it was expired). So, i choose the first option and i get access to the summary.

    While i get my extracted stuff of the last game back, the game presented me an unknown status and a backpack value of Zero despite the fact that the extraction was completed.

    Screenshots here :

    https://i.imgur.com/RCXHPMv.png

    https://i.imgur.com/FpqaAbZ.jpeg 

    I think you guys should take a look at this kind of error cases.

    Anyway, thanks for the reply.

    0

Please sign in to leave a comment.