JavaScript is required to use Bungie.net

Forums

8/29/2021 3:35:42 AM
1
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.
English

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon