We are now over 72 hours, 3 days, of many people on Win10/8/7 being completely unable to even get to the main menu or play at all, no matter what attempted fixes they try. No sign of a daily-reset-scheduled hotfix today. Last hotfix I am aware of was Thursday. [b]I am unable to edit my previous thread[/b], so... here we are. [b]If I could have[/b], I would have e.g. edited the previous thread to indicate it had at least been added to Known Issues, etc. [b]Guardians:[/b] Things to mention in your reply, specific to the computer you run Destiny 2 on: Which OS are you running? Laptop or desktop? Did you already have Battleye installed before the first Season of the Lost download? Do you play a lot of other high-end games that might have installed a fix or something that caused problems? Do you have any software development software (e.g. SDKs/IDEs/etc) installed? Please remember to inform Bungie of anything you find that might help them fix it, and help keep the issue visible until you can play again. More individual Guardians consistently reminding Bungie they're still unable to play should put us closer to the top of Bungie's priorities for a fix, and that's what we need. [b]Bungie:[/b] The Thursday hotfix [b]did not change anything[/b] regarding this bug for anyone, as far as I can tell, and [u]I have not seen any Bungie acknowledgement of that fact [b]yet[/b][/u], nor have I seen any sort of ETA for a fix or even when to check back for an [b]ETA of a fix.[/b] [i]Even just a "won't be fixed before next week" would be better than nothing,[/i] and it's very much looking like no one affected by this bug will be able to play [b]all weekend.[/b] Given the severity of the bug, I am explicitly asking that [b]Bungie[/b] provide [u]daily updates on progress or lack thereof for this bug.[/u] Leaving it at an open-ended "investigating" is inadequate for a bug of this severity. Otherwise there will naturally continue to be hundreds of increasingly unsatisfied people who can no longer play the game milling around the forums looking for news. That's not good for anyone and it is preventable, even if it would require management to adjust their policies (that e.g. restrict what representatives are allowed to say, or what information is given to them to relay to us) to do so. It's time to improve communication re:this bug. Please give us a specific URL, like a Bungie-created thread, that is updated at least daily with progress or at least a specific acknowledgement that the bug still affects a substantial portion of the userbase after the latest hotfixes. When the game fails to even run for days on end, the Known Issues thread is insufficient unless the line is updated in more detail daily so we know e.g. that you know a hotfix didn't work. This is especially bad after all the season hype leading up to a massive shock disappointment for hundreds or thousands of Guardians of not being able to play the hyped content, or ANY Destiny 2 content at all. Bungie management needs to do better at providing the resources and freedom to workers to avoid situations like this. Also note that the entire seasonal/vault model with content being available only for limited periods makes this situation even more unacceptable. If we knew when we could get back in, or that we could just come back in a year and not miss out on the content, that would help. Bungie executives: Do better. Pete Parsons: Do better. I will attempt to catalog all the forum info on this topic: Previous (mostly uneditable/unupdatable?) threads: 5 [url=https://www.bungie.net/en/Forums/Post/259485501]BattlEye Launcher crash message[/url] 245 [url=https://www.bungie.net/en/Forums/Post/259485619]Program can't start due to mysterious missing file (win7, 8, 10)[/url] 11 [url=https://www.bungie.net/en/Forums/Post/259486445]Game became impossible to launch on any Windows 7 computer[/url] 2 [url=https://www.bungie.net/en/Forums/Post/259488736]Error message when i started game[/url] 2 [url=https://www.bungie.net/en/Forums/Post/259491351]startup error[/url] 24 [url=https://www.bungie.net/en/Forums/Post/259498258]Is the handling of this bug acceptable under the circumstances?[/url] 15 [url=https://www.bungie.net/en/Forums/Post/259508350]Can you launch Destiny 2? (Missing DLL file "api-ms-win-core-path-l1-1-0.dll" issue)[/url] 1 [url=https://www.bungie.net/en/Forums/Post/259512351]Missing a File[/url] 0 [url=https://www.bungie.net/en/Forums/Post/259515530]Destiny 2.exe-System Error[/url] 1 [url=https://www.bungie.net/en/Forums/Post/259515543]Destiny 2.exe-System Error[/url] 0 [url=https://www.bungie.net/en/Forums/Post/259517605]Error code 0xc000007b at lauching[/url] 0 [url=https://www.bungie.net/en/Forums/Post/259529080](POLL)How good is Bungie's responsiveness to customer requests and needs?[/url] (Updated) If anyone feels like pointing out more related threads, or pointing people in those threads to whatever is the most active front-page thread at the time as it changes, go for it. [b]EDIT1:[/b] The Bungie reply to the "Is the handling of this bug acceptable under the circumstances?" thread has just? been [b]updated[/b] with: [i][b]"UPDATE 2: We've confirmed that a change we made in our builds for safety against buffer overruns is the cause of this issue. We are figuring out how to best fix this issue."[/b][/i] [b]EDIT2:[/b] The Bungie reply to the "Program can't start due to mysterious missing file (win7, 8, 10)" thread has just? been [b]updated[/b] with: [i][b]"UPDATE 3: Unfortunately, this issue will not be resolved before the weekend begins."[/b][/i] Well, now I'm sad. Please still answer the polls if you haven't already, but other than that, looks like everybody still affected can go play other games until Monday - unless you want to stay for the company, of course. Remember to keep the issue alive if you want to help with that.