Box art - Destiny 2

Destiny 2 Signing In Error and More: How to Fix PC Launch Problems

Destiny 2 PC has experienced a relatively smooth launch, though there are some problems that players are encountering as they try to play the game on its release day. While some of these issues have direct fixes, others require some patience while Bungie works through its selection of teething issues.

With that being said, here are a few of the most common problems the PC version of the game is currently suffering from and how to fix them.


Destiny 2 signing in error

You may find that you’re forever struck on Destiny 2’s signing in screen, with the game failing to load beyond this point. While many players are simply being placed in server queues before they can enter into a game session, others are finding that they’re unable to access the game whatsoever as a result of this signing in error. Unfortunately, Bungie doesn’t seem to have this problem sorted out at the time of this writing, with the developer’s support page reading: “We are actively investigating reports of players blocked from signing in to Destiny 2.”

Also: PSA: Destiny 2 PC Voice Chat is Enabled by Default

I personally experienced this error a couple of times while playing today, and found that closing down the game and opening it up again usually worked, though it seems that this simple fix isn’t a solution for everyone. Bungie will likely roll out a patch that will address this issue sooner rather than later.


Destiny 2 persistent issues

Bungie recommends that players who encounter persistent issues with Destiny 2 delete the game’s existing CVARS.xml file. This can be found in:


Players must close the game before doing so and then relaunch it, with Destiny 2 regenerating this file and hopefully sorting out any recurring problems that the player was experiencing.


Destiny 2 TRUMPET error code

Bungie is currently investigating all of the error codes that are being displayed to Destiny 2‘s PC players, though the developer has a fix for the TRUMPET error code. This error can apparently be rectified if the player changes their Blizzard region, with instructions from Blizzard’s Support Forum Agent Eloemaz included below:

“To switch regions on the App log out of the App. On the App above your log in information click on the drop down box to change the region you want to log in to. 

To change the region for a specific game click on the drop own menu above the play button for the game to change the region.”