We are aware of an issue currently affecting Xbox/Microsoft Store players, resulting in Error Code 6003 when a DLC class operatve is selected.
This is due to an Xbox outage, and is unfortunately outside of our control.
You can view Xbox’s status here:
Error - (Other)
keep getting error 6003 when trying play any of the DLC operatives. Have uninstalled and reinstalled, done everything else I’ve seen for trouble shooting.
No, I don’t use mods
Constant (100%)
PC - Microsoft Store
This is happening to many other players seems Fatshark broke something since they’re on vacation haha maybe the authentication, or a guy that’s supposed to reset something like the reset timers for havoc got glitched one time
We’re aware of Error Code 6003 reports occurring for Microsoft Store players, and we’re investigating.
Apologies for the inconvenience in the meantime.
Purchases & Aquilas
I Bought the skitarri and Arbitrator but I am unable to play them. When I click continue nothing happens, I restarted the game and I restarted my Xbox. I looked for game add-on’s and nothing shows up but the game.
No, I don’t use mods
Xbox
Happening to me too I just got off work and logged on but can’t log into any DLC characters only the base 4
Error - (Other)
Only when I try to log into ANY of the DLC characters do I get the error message 6003 and get kicked back to the character select screen.
This happens with mods and without after a full wipe and reinstall. worked fine yesterday but now none of my toons can I play that I paid for. please help, also all drivers are updated and the MS store is updated as well.
Purchases
Seems something’s broken with the DLC classes, (the authenticity maybe?) try logging with a DLC class, load into mourning star, get can’t connect to server errors
Start game go to operative select pick DLC class get “can’t connect to server” error
Constant (100%)
Xbox
How is Error 6003 not resolved yet? I took the day off to game and play Darktide as I bought the DLC characters. Do we have an ETA as to when this will be fixed?!
Have just updated the post. This error is a result of an Xbox outage and is unfortunately not something we’re able to resolve on our end. We can only sit tight and monitor status updates from Xbox, here:
Xbox services appear to have stabilised again now.
