Um.. the overrun issue is the issue being addressed here, Bungie even stated that specifically, with nothing being mentioned about the missing file issue. [quote] We believe this issue is related to something Bungie changed in our builds for this release. UPDATE 2: We've confirmed that a change we made in our builds for [b]safety against buffer overruns[/b] is the cause of this issue. We are figuring out how to best fix this issue. UPDATE 3: Unfortunately, this issue will not be resolved before the weekend begins.[/quote] And it wouldn't be pain staking at all; if Bungie has it's digital department setup correctly- with previous versions on hand for immediate reverting; all they would need to do is simply restore the previous version of the D2 code and implement it. If they can't do that...I wonder what else they're lacking in. And I'm not being over dramatic at all, I'm looking at this logically. This is worse than Cyberpunk's launch. With Cyberpunk's launch- xbox, playstation and PC...everyone was able to play the game. they launched it and played. Did it crash? Have bugs? Yes to both. But they could open it up and play (performance and graphic issues aside- it still ran). Destiny 2 Season of the Lost: Xbox / playstation / strada only. PC 7, 8, 10 home- dead. Windows 10 pro- playable. Only those willing to search for an answer have reported replied. The rest are probably waiting patiently while people like everyone here raise their voice. If a file is missing and 'alternative' fixes don't work...every computer that doesn't have that file..isn't going to work. Which is worse: having parts of your platforms unplayable or having crashes, but still having all platforms playable. Plus, people took time off for this launch (whether that being smart or not is another story). Bungie will have to do something to make up for it all. What is worse about all this is how long Bungie took to address the issue. I'm sure their twitter feed blew up after 12 hours, but no response. A simple "we're getting reports of the game not opening- we're looking into it." followed by "Yeah, there's an issue we've encountered, we're investigating." The fact that they're ignoring the missing file component (tells me that they never tested Windows 7 in the first place, because if they did- like they should have, they would have run into this issue and fixed it prior to launch)- they should either state how or where to get the file, if possible. I mean, they do reference Windows 7 being supported in both minimum and recommended requirements; ie, they should have tested it. If not, then they should tell us where it comes from and their plan on delivering the file or making it possible for us to go and find it. Especially since it was only required AFTER needing BattlEye- which seems to have a less than 50% accuracy. Because like all those whom are complaining- Destiny 2 worked perfectly before the update...and now afterwards, we can't even launch the game- ALL Windows 7 users are left out to dry. And I don't know about you, but I've read every comment on the threads here that are associated with the problem: Windows 7, 8, 10 home- all of them can't play it. Only Windows 10 pro can play it. If Windows 10 home people can play it, I haven't see it yet. So no, I'm not being over dramatic, I'm pointing out all the flaws in one spot. Nothing I've said here is original- its regurgitation, only all in one spot. If you don't like that, you're more than welcome to stop responding to my comments. I'm going to continue about my day and monitor the progress of this fiasco, hoping that by Wednesday I'll be back in the game on PC. If not, shame on Bungie for allowing this to happen.