A "buffer overrun safeguard" isn't the error that's being addressed here. It happens to be related to the file that is missing. A buffer overrun doesn't equate to a missing file error — that doesn't mean anything nor is it what's being said here. There [i]is[/i] a missing file. The wording is a bit vague but it can be interpreted in two ways: 1) The file that is missing is api-ms-win-core-path-l1-1-0.dll which holds the library implementation of some buffer overrun safeguard code. They added buffer overrun safeguards and it uses this library. The library is missing on some systems so the game can't load and crashes. 2) The file that is missing is api-ms-win-core-path-l1-1-0.dll and the reason that it is missing is because of some new code, being the buffer overrun protection, that worked incorrectly (commonly used during string manipulation) and altered the search path of the file so that the file couldn't load. I chose to go with option 1, because users have reported the library file actually not being present (such as yourself) and the error changing to another error when trying to replace it. So it likely isn't #2. As far as your last paragraph goes, it would be very painstaking to try and remove BattlEye temporarily from the game and almost certainly not worth the effort. I have no doubt the many things would have to be completely reverted or reworked again to keep the current build but also have battle not affect it. Since BattlEye is, well, meant to be a permanent addition, and a good one at that, they very likely did not integrate it with little "toggles" for everywhere it's integrated. That wouldn't make sense from a development point of view. Stuff happens and yeah it sucks but you are being [i][b]very[/b][/i] over dramatic about them having to "save face" and this is "worse than Cyberpunk's launch". The game peaked at 177k concurrent active players and has peaked at the 120k's to 130k's (and rising) every day after. The reviews in the past 5 or so days on steam are also very positive with launch day coming in at 85%, higher than destiny's current average. Bungie's reputation is no where close to being at stake. The truth of the matter is that unfortunately this bug and the others, while affect a lot of players, is still a minority of players and is not nearly as many as you think it is. It'll get sorted out within a couple of days, and at most a week. So give it some time and hop on another game for a bit while you are waiting. I'm on Win11 and have been since first access on the dev channel so I've had to deal with bugs and crashes for months due to library incompatibilities, but it is what it is. I just play another game while I'm waiting.