Alright, let's go over the situation. A lot of people obviously can't even run the game to get to the title screen. It seems to include all win7/8 users and a portion of win10 users as well. It also appears to affect both 32 and 64-bit operating systems, even when fully patched and updated. It affects both high-end and low-spec PCs with a wide variety of graphics subsystems. I would speculate that most of the people who can run Destiny 2 at this point are Win10 users with high-spec hardware that ran some other game or SDK/development software that install a workaround of their own that also fixes Destiny 2 - or perhaps people who already installed Battleye manually or with a different game before some autoupdate that interacted with it. Can anyone confirm Season of the Lost running on Win10 32-bit (preferably Home,) or getting these specific errors on Win10 64-bit (preferably Professional?) Nothing a user can do generally helps: "upgrading" to win10, verifying the game cache, reinstalling completely, installing "missing" DLLs, etc. All of these "solutions" are reported as failing. Common elements are references to a missing "api-ms-win-core-path-l1-1-0.dll" and, when brute-forcing past that, a 0xc0000007b error. Battleye may be part of the problem and letting people run the game without access to Crucible when Battleye isn't running might be a partial solution that, at the very least, might help gather less obfuscated error info since it appears to be corrupting error messages. And it still isn't acknowledged in the "Known issues/Vital Info" thread - this is not "low performance", it is "no performance." "Hello. We're currently investigating this issue." seems to be the ONLY acknowledgement Bungie has given this issue, in one of the largest threads about it with hundreds of users saying they are unable to play, and some of those statements mysteriously just disappearing over time. The near-silence from Bungie despite the severity of the issue is deafening. The minimum requirements still state Windows 7, yet Windows 7 cutscenes have apparently been dysfunctional since Beyond Light launched, and now for a complete day the game has been unusable for everyone running win7/8 and a substantial portion of the win10 userbase as well. A lot of people do not want to run Windows 10 for various reasons. I have two words Bungie management should keep in mind here: False Advertising. To the executive suite: Fix this and give workers the resources to do proper minimum requirements beta testing. If the problem is Battleye, pressure them to support Bungie's entire userbase including the 7/8 users on threat of losing Bungie's business to another service provider and becoming known as the problem here, which might lead to a boycott of Battleye. If they don't want to listen and support Bungie and Bungie's userbase, they can suffer the consequences. Chances are, after this, if Destiny 2 doesn't return to previous levels of compatibility quickly, they're going to suffer reputation damage anyways, because everyone will suspect they were largely responsible unless there's clear evidence to the contrary. This bug will probably also generate a lot of lost sales for Season of the Lost and Witch Queen, proportional to how long it takes to get fixed. I hope Bungie is taking that into account when prioritizing it relative to e.g. problems in season content for those who can actually play.