As it turns out, there are several different causes that might end up causing this error code with Destiny 2:
Method 1: Ensure that you own the Game
According to the majority of affected users, the ‘saxophone’ error code seems to largely affect users that have tried the game during a weekend where it was free to play. In most cases, code saxophone is a signal that you don’t have the license to play the game or that the session to the license has expired after you have idled in the menus for a long time. In case you received the game a gift from one of Blizzard’s promotions, you’ll likely need to claim it using the launcher app on Battle.net. If you already claimed it, it’s worth a try to restart the Battle.Net client or even restart your computer and see if the saxophone error code persists. Sometimes the launcher just needs a restart to register that you actually have the full rights to run the game outside of its free-to-play promotions. In the event that you have already ensured you have the full rights to Destiny 2 and you’re still seeing the error even after rebooting your system, move down to the next potential fix below.
Method 2: Running Battle.net with Admin Access
Another fairly common cause that will produce the saxophone error code when launching Destiny 2 is a permission issue facilitated by insufficient permissions given to Battle.net. If this scenario is applicable, you should be able to it the problem by ensuring that Battle.net is launched with admin access. To deploy this potential fix, follow the instructions below: If this fix didn’t work for you, move to the next potential method below.
Method 3: Removing the CVAR files for Destiny 2
If you want to avoid uninstalling Destiny 2 along with the launcher (Battle.Net) you might be able to resolve the saxophone error code by deleting a couple of CVAR files belonging to the user profile. Several affected users have confirmed that this operation successfully allowed them to eliminate the startup error in Destiny 2 and play the game normally. To deploy this potential fix, follow the instructions below: In case the same issue is still occurring, move down to the next potential fix below.
Method 4: Reinstall Destiny 2 & Battle.net (After clearing the cache)
As it turns out, this problem can also be facilitated by some type of corrupted cached data that’s currently being stored locally. Several affected users have confirmed that they managed to fix the issue by uninstalling Destiny 2, Battle.net 2, and deleting every bit of cached data before installing everything once again. If this scenario looks like it could be applicable, follow the instructions below to uninstall the Destiny along with the game’s launcher and then clear every cache directory: Note: Keep in mind that the operation you’re about to perform will cause you to lose every persistent setting including logged user credentials, custom keybinds, and custom graphic settings for Destiny and other games that you launch via Battle.net.
Destiny 2 and Fortnite Crossover Event Leaked New Fortnite Skins Revealed For…Destiny 2 X Fortnite Crossover Officially Happening, New Destiny 2 Skins…Fix: Destiny Error Code WeaselFix: Destiny Error Code Beetle
