So does this mean that we can get compensated or something, because I've heard a lot about people getting compensated when this happened before or whatnot...I did miss a lot of grinding so far (I grind on pc, but do main activities on Xbox when I have time), which really impacts my experience in activities like Iron Banner (which is Power based) and now Trials (which is so cool, you guys should try it out). But I honestly want to say thank you because I really want to play the game on my pc again and am just happy that Bungie decided to fix it and not tell people to just upgrade.

20: 07:55: Starting the BattlEye service... 20:07:57: Starting the game... 20:07:58: A modification of the Windows kernel was detected. Please repair or reinstall the system. 20:07:58: The game could not be started. And how does this mean where is the promised correction and ?

After the hotfix (more like a coldfix really) the game is actually loading. Unbelievable! I better not jinx it. [Update] Cutscenes are still broken lmao.

exited to play again after a MONTH. Get Home turn on pc. open steam. Go to Destiny 2 Click launch. Game pops up on my task bar. Gets exited Destiny2.EXE Application Error "The instruction at 0x00000000 referenced memory at 0x00000000. The memory could not be written. Click on OK to terminate the program" It does not look fixed to me. Instead of it just crashing instantly it instead gives me the icon for the game THAN crashes.

What really gets me is there isn't a single apology here I haven't been able to play a game I purchased on a supported OS for what will be a full month because they didn't do ANY testing and they haven't even owned up to that it was their fault let alone make even an attempt at apologizing for it. This is extremely unprofessional and they should be ashamed at what happened and people are out here saying they understand and take their time. At this point I just want a refund I don't WANT to play a game where the company is this bad at fixing things and is this unprofessional treating their player base.

Morning of September, 16 2021... no fix :(.

How are we gonna be compensated for this fiasco? That's all I wanna know... ...and it beter not be 200 silver for Eververse!

Today is the day boys, lets go, i need my buddy back on my fireteam, pls let him play, let this fix work!!!

[quote]UPDATE 6 - Sept. 9 This issue will be fixed in our next update, which will go out on Sept. 16. It is not possible to include in an update sooner due to limitations beyond our control.[/quote] Glad there's a fix, but.... Ooof. Season of the Lost! Yes, what an ironically appropriate name! Paying customers will have [i]lost[/i]: * 23 days * or 3¼ weeks * or 12.7% of the much-longer-than-normal season With that in mind--and assuming the fix works--the community needs some answers: 1. What changes [u]will[/u] Bungie make to its QA process to prevent a debacle like this from happening again? 2. What changes does Bungie plan to address the impact of the downtime? (For example, repeating Eververse selection weeks.) 3. Will the 10-month-old cutscene bug--that can even kick players to orbit--be fixed?

Seriously Bungie, you need to fix this, I have more than 3000 hours on the game and never had this problem before. Since the release of the new season my screen freeze and the game crash without any error code. And it is doing it A LOT. FIX THIS!!!!!!!!! plz

I came from my work thinking i finally can play D2 and nope still not fixed? still telling me the same error...

Bungie, please fix the Windows 7 Launch Issue. My husband and I rarely get a chance to game together since having a kid this year. He has the next 5 days off, and if we don't get to play Destiny 2 together these next few days, we're probably going to end up playing something else that ends with me getting pregnant again. Please fix this issue today, my uterus depends on it.

So... thousands of people are going to miss the entire first 3 weeks and then some of the season, after that massive hype event leading up to it? How will they be compensated, especially the ones that preordered/prepurchased? I just want to note in passing that Bungie's own description of "what not to do" in their own post, not unlike abstinence education, provides more than enough information to duckduckgo or google it and do it. And I also want to point out, in passing, that if anyone gets banned for that, there will probably be more Cain raised than if Bungie, say, made all hand cannons take purple ammo, or deleted vaults again like Destiny 2 Vanilla: it would be a much worse idea than inadequate testing by itself. And finally, on that note, I want to point out that while placing strange files in the Destiny 2 folders IS highly unadvisable and could be interpreted very loosely as modifying the game, the same very much does not hold true for system folders like System32 (though by nature, tampering with system folders should only be done with the greatest of caution.) It is especially unwise on a system that has any access to your credit card/tax/health/etc information. Stay safe, be smart, people. With all that said, I feel it's necessary to say that, frankly, Bungie's treatment of the portion of the community affected by this bug has been pretty frequently very poor, disrespectful, and inappropriate. I will be keeping this in mind, as I have with the Destiny 2 Vanilla Vault debacle, in my future purchasing decisions. Please, Bungie: Do Better. I want to feel good about spending money on your products again, like back in the Taken King era. If you can't re-hire O'Donnell, Dinklage, Torres and the rest, at least try harder to recapture the spirit Bungie had back then. Let my people play (Destiny!) The console cert process and similar issues should NOT be able to delay roll-out of a PC-specific fix like this so much. Look at Warframe and their sub-hour-turnaround no-downtime patches. Management needs to invest in re-tooling Bungie's patch capabilities closer to that. They have all the same constraints Bungie does. It can be done, Pete. So do it. It shouldn't take over 3 weeks and some public pointers from Russian hackers to get this fixed. Are you trying to tell us something with the suspiciously-timed re-issue of [armory]Legal Action II[/armory] this season? What are you trying to say to the community, Bungie? Here's hoping I'll see everyone back in game on the 16th. Or at least everyone who hasn't given up on Bungie entirely.

Almost looks like Bungie is waiting for a lawyer with a class action to show up at this point...

Will we lose another weekend is the question of the day.

Limitations beyond our control So its q battleye problem and now they are working on a patch? It took you almost 2 weeks yo realize that Realize something that community was telling you since season launch.

[quote]UPDATE 5 - Sept. 8 We are verifying a fix and are figuring out when to deploy it once it's verified.[/quote] ...and you wouldn't push the update the second you've confirmed it works because...? Wait you did actually test it this time, right?