I think the issue is that Bungie maybe forgot 8ntegrating windows 7 architecture into the new update. Being a company once support for windows 7 was closed they must have moved on to windows 10.
From what I gather windows 10 has some advanced functionality that is not present in win 7. Direct X 12 for instance, or .Net 5 both of which have no support on win 7. It's just my speculation. However I am going to try and install windows 10 and see if this revolves the issue.
But the root of all evil lies in the fact that Bungie did not test for win 7 compatibility and went forward with the expansion. If we are lucky they will provide a quick solve otherwise it may be a massive wait since they will have to rework the entire windows architecture to make in compatible with windows 7.
English
-
So as I thought I jus installed windows 10 and destiny 2 started I haven't logged in or played but it started without any error to the login screen So I will test further but it's too late today. Basically 1:30 am in night So see you all and good luck
-
[quote] Direct X 12 for instance, or .Net 5 both of which have no support on win 7.[/quote] Not quite true. I ran and beat Cyberpunk 2077 and just installed .net 5 on my windows 7 machine.
-
Could be true my dear friend but D2 works on win 10 so yeah it's some difference in architecture or as so many have suggested could be that battle eye clashes with win 7 dll's or simply battle eye is incompatible with windows 7
-
it's exactly the same crash issue on Win10 and Beta Win11, tested on both with a fresh install of Win10