{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
8/24/2021 7:20:03 PM
3
Same issue, Win7 SP1/SP"2". Bungies really does an incredible job of covering all of their players' bases, accounting for what they allege is supported for Destiny 2.
English
-
Win 7 Home Premium SP1, same missing file system error, but no file name shown just " " as everyone else seems to be getting. Verified game file(s) using Steam, no issues. Removing Battleye, and then selecting to not install it as you launch D2 triggers the same style system error message, but with a valid file name (api-ms-win-core-path-l1-1-0.dll) Tweaked the Battleye install .bat file so it didn't auto-exit [added 'pause' as an extra line], and in the command prompt window it shows this "..\destiny2launcher.exe' is not recognised as an internal or external command" Anyone know if this has been or can be fixed by reinstalling D2?
-
Reinstalling hasn't worked
-
Edited by PhellAsleep: 8/25/2021 3:09:29 AMSomeone on Steam claims to have found a solution, if this is what you're seeing. "If you are getting an error: destiny2.exe - system error, can't launch the application because *empty space* is missing from your computer, try reinstalling the program. Its because you are most likely missing api-ms-win-core-path-l1-1-0.dll file. The empty space in the error message is a bug of BattleEye anti-cheat that incorrectly translates the error. You can check if you have the file in System32 and SysWOW64 folders. If you don't, download them from any site you trust and put them in the aforementioned folders. Fixed the error for me. Have a good day. " https://steamcommunity.com/app/1085660/discussions/0/3034850940604548272/ The thread has been taken off Steam now. Likely because it didn't work.
