AndyB

I have to confess I’m uncertain what happened then. The drops and inventory system are on Twitch’s end; all we do is feed the items into it and set campaign dates. We wouldn’t have taken any physically claimed rewards away to my knowledge. Like, as long as you’ve actually hit that Claim button on your Twitch Inventory then you should have the reward and keep it.

You may want to contact Twitch support and see if they know anything?

Hmm, strange. Are you absolutely certain you’re on the right Twitch account? I just checked my personal Twitch account and I still have all the drops I claimed visible in my Twitch inventory.

Is this issue still occurring after the 2.4.5 update (assuming you can download it)?

We appreciate your understanding and believe us, we totally get how frustrating freezing up and losing progress must be on top of getting an unknown error to boot. This is hardly an ideal situation but we’re doing what we can to work around the issue in the meantime.

Edit: And I certainly apologize if I seemed short or flustered; I was caught off guard by the issue and since it was emergent, I didn’t have a ton to go off of yesterday until we were able to investigate further. Thanks again for your patience and understanding.

Update from Scott J about what’s been going on:

Hello everyone! We’ve got an update from Project Director Scott Junior on what’s been going on with updating the game from the Xbox App (commonly reported as error “0xD05E0108”):

Hey Exiles,

I wanted to update everyone on a few of the urgent issues we are working on with the Microsoft Store/Xbox App version of the game.

Yesterday we released version 2.4.5 which addressed some certification issues and fixed a client freeze that could happen when teleporting (admin teleport, dying, entering a dungeon, etc). Unfortunately we discovered that the Microsoft Store / Xbox App was giving an error code 0xD05E0108 to anyone that tried to update from 2.4.4 to 2.4.5.

We have been in communication with Microsoft about this issue and we just discovered that it is due to an error in the patching system. This is not something we control and Microsoft has told us they will try to fix it as soon as possible. Until the patching issue is fixed the only way to...

Gotcha. If you don’t have a D: drive then don’t worry about it - not much you can do there. We’re still investigating the matter; more news as soon as we’re able to share.

It is unlikely 2.4.6 will contain a solution for this issue.

Did you make sure to physically press the ‘Claim Item’ button on the drops you received?

If you only have a C:\ drive then there is nothing more to do (and nothing wrong on your end as the user).

If I’m not making sense please let me know and please describe exactly what the issue you’re experiencing is.

In a nutshell, the computer’s main hard drive is always labelled “C:” and additional drives go up alphabetically from there (D:, E:, F:, etc.). If you only have a C: drive showing up when you check on Windows, then that’s all you have and you shouldn’t worry. In the example shown, the person has an additional hard drive.

Thanks for the update and info. Yeah, the vexing part is the error has no official public-facing definition anywhere that I can find. We’re looking into it!

Hi friends, update on this. We aim to have a potential fix for this in the next update, v2.4.6. Should be out in the next week or two.

Yeah sorry, this is a measure to prevent automated spam. I’ve bumped your level up a little so you should be able to post images now.

It looks like you have an 11th-generation Intel CPU installed. Please take a look at this thread and let us know if this helps:

Apart from the usual server restarts, 6422 has crashed exactly once in the past 48 hours. It appears to have gone down a total of five (5) times in the past week, looking back to June 7th. Obviously we’d prefer this number to be 0, but it doesn’t seem to be nearly as dire a situation as you describe. As mentioned, Zendesk is a good resource to report these outages and hopefully the maintenance can help.

Assuming we don’t run into any last-minute issues (like cert, etc.) then the update is planned to launch on all platforms at around the same time.

2.4.6 is the next scheduled update for all platforms, which includes a number of bug fixes for each specific platform. Should be in the next week or two assuming we don’t run into any critical last-minute issues.

Personal curiosity, but are any of you experiencing this error using mods?

Hmm, alright, thanks you three. I’m sorry this continues to be an issue (Although I’m glad reinstalling the game worked at least for you, @Frost_I, although that’s not really a sustainable solution).