I want to report here that I'm having the same problem as the original poster.
Windows 7 Home Premium.
Destiny 2 worked great for me (besides cinematic framerate bug) the whole last month up until 1-2 hours before the update on Tuesday, 8/24.
I tried verifying integrity of game files through Steam, and that didn't cause any changes.
I thought perhaps Battleye wasn't booting properly during Destiny 2 startup, so I tried manually running Battleye during Destiny 2 startup, but I received the same error message.
It might be important to note that I get a security popup for my approval when opening Battleye manually. I wonder: could Battleye be rejected during Destiny 2 startup because Windows doesn't allow it without admin permission, and with no Battleye open, the game doesn't launch? Maybe this is causing the failure to launch? It might explain why some people with Windows 7 can play fine while others can't. Perhaps it's a Windows setting?
I'm pretty new to Destiny 2. I've really enjoyed playing it since I started a month ago. I am looking forward to playing my first whole season. I bought all the expansions. Thanks for working on this Bungie. I hope you find a solution soon.
English
-
[quote] It might explain why some people with Windows 7 can play fine while others can't.[/quote] What Players do you speak of and where are they? Because as far as I know, not a single Windows 7 user can play.
-
welcome to the club , this game has an amazing perfect world, one dream city is worth something)
-
Welcome to the party, pal!