I know quite a bit about computers, etc- it's half of my lively hood, I'm more hardware though than software. I know that's literally impossible to test for every scenario because of the hundreds of thousands of setups. But what I don't understand, is how an 'overrun' error equates to a 'missing file' error...because from what I understood from your paragraphs, it didn't explain it.
And the 'library' that doesn't exist...is a file; api-ms-win-core-path-l1-1-0.dll is completely missing from my system32 / syswow64 folder. Kicker, Destiny 2 ran fine the day prior to this update. So my question still remains; how does this overrun error relate to the missing file problem that every windows 7 user is experiencing, for a file that wasn't there prior to the update?
The best way for Bungie to elevate this problem is to de-integrate BattlEye from D2 and allow us to play, while they work on a fix in the background. Because if this non-sense goes on a week, Bungie will have to do something serious to save face and restore their damaged reputation. This...is looking worse than Cyberpunk's launch, because people literally can't play it vs having issues with playing it.
Your role as a moderator enables you immediately ban this user from messaging (bypassing the report queue) if you select a punishment.
7 Day Ban
7 Day Ban
30 Day Ban
Permanent Ban
This site uses cookies to provide you with the best possible user experience. By clicking 'Accept', you agree to the policies documented at Cookie Policy and Privacy Policy.
Accept
This site uses cookies to provide you with the best possible user experience. By continuing to use this site, you agree to the policies documented at Cookie Policy and Privacy Policy.
close
Our policies have recently changed. By clicking 'Accept', you agree to the updated policies documented at Cookie Policy and Privacy Policy.
Accept
Our policies have recently changed. By continuing to use this site, you agree to the updated policies documented at Cookie Policy and Privacy Policy.