Honestly, this is the same issue everyone else is having. I'm just posting this to add one more to the pile so the person who's job it is to comb through the forums and submit the issue to the dev team can pass whatever threshold they need to consider it a real problem so they actually do so. Assuming it has already happened, I'm posting this for whoever's job it is to relate the progress to the community passes whatever threshold THEY need to hit so we can have some communication.
Being aware of the issue doesn't mean you have the instant ability to fix the issue, sometimes that's just the way it plays out. That said, when so many users are missing out on the content they paid for it seems the least that you could do is set expectations or acknowledge that it's even happening in the first place. We are so easy to take money from yet simultaneously so easy to ignore, it's difficult to discern if this is a cowardly act or they truly just don't care?
Anyways, to make this more legit, I too have been having the issue since 3/10 after the Hotfix. I've re-installed the game, rebooted the system, even installed it on the internal harddrive rather than the external I had it on previously. The steam version works well but, as you know the Witch Queen and paid Season content will not work across marketplace stores. I'm using an Acer Helios 300 with an Intel Core i7-9750H CPU @ 2.60GHz 2.59 GHz with a GTX 1660-ti graphics card on Windows 11. About 3-5 seconds into the load where you see the rotating triangles in the loading splash screen freeze, then the game will crash out/close. In the rare instances that it does not close, I've left those frozen triangles sit for a half-hour with no resulting resume in operation.
I have seen the fixes people have posted up, but downloading random files from the internet seems potentially unsafe. While those fixes seem to be based on rolling back the Microsoft gaming services and therefore it would be tempting to think that it was more a Microsoft Issue than a Bungie or Destiny issue, this problem seems related to the latest Hot Fix, indicating that they changed something that resulted in the issue in terms of compatibility.
Be the change you want to see, by being decent.
-
same issue