Getting this error after battleye starts
Windows 7
This has been reported on Windows 8 and 10 as well.
Reinstalls haven't helped, replacing dll hasn't worked, reportedly upgrading to Windows 10 has had some success but also some failures.
Patience is required, but silence isn't
If you're having the same problem, please post here so we can keep the pressure up.
"which system are you having this bug on" poll: https://www.bungie.net/en/Forum/Post/259508350/0/0
Our issue made it to the top of the issue list in todays TWAB, so we have some progress, however shallow it may be.
-
Edited by Feltharion: 8/27/2021 4:34:48 PM[b]DON'T LET THIS THREAD DIE[/b] Seriously, they can't just ignore Win 7 users/players/Guardians, and I personally don't want to stop playing if the game works fine without BattleEye...I play since Destiny 2's Beta and [i]this is the first time I face such an issue[/i], also if not obvious, I'm also on Windows 7. I didn't even bother to get Beyond Light because of the cutscenes update that broke them for us too (asides being a heretic and wielding the Dark, of course), but like...come on Bungo. I ignored the New Light issue because I can watch the cutscenes later on YouTube, but this? My game refuses to open, so I'm unable to even play it. Also the issue is -blam!- BattleEye, it's not working properly on Windows 7, not detecting the game's executable somehow. I just want to thank you guys for upvoting my comment/reply, Bungie needs to be aware we're part of the player base, even on an outdated OS, some can't afford certain upgrades, that along with other issues (like data trading), so to any of you reading this, please don't come over here telling us to upgrade our System. Please. [i]It's worth noting Windows 7 is in the System Requirements, even in the Recommended Specs.[/i] And I get you guys must be as mad as I am, but let's keep it a supportive place. Bungie employees are people and workers just as we are, so let's [b][i]not[/i][/b] attack anyone or simply be aggressive towards them. I'm sure they'll look forward to it considering we are their users, regardless the time it takes. [b]UPDATE:[/b] It's confirmed it's something on Bungie's end (the game itself), they had changes in the build along with Season of the Lost release. Bungie has noticed us and is currently investigating our issue. I didn't comment before, but I [i]did[/i] try as many things as I could and always do with games not working on our System and it usually solves the issue. However, this time was different. All I could get was more "information" in a way, and these would be what everyone probably knows at this point, which is the lack of "api-ms-win-core-path-l1-1-0.dll" in the System, a DLL not needed so far, which is weird at the very minimum. And then eventually, if you work around that (replacing the DLL in any way), you get [i]another[/i] error, which is Error Code "0xc000007b". And then if you also manage to work around [i]that[/i] you get yet another error, this time for some reason it's not finding "destiny2.exe", which is also weird considering it's right there in the Game Folder. That's all I got Guardians. Hopefully we'll get a fix and update soon, stay tuned everyone! And thank you, LordShenlong, for creating this Topic and helping us get Bungie's attention. Eyes up!