{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Witness's Hair Line (TL):
6/10/2026 8:35:52 PM
2
SOLVED/CLOSED.
Platform: Steam, Windows 11 PC
Please Please Please Help
Issue:
Destiny 2 fails to launch. BattlEye installs successfully, updates, reaches “Launching game...”, then Windows displays:
“Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.”
Current executable path:
C:\Steam\steamapps\common\Destiny 2\destiny2.exe
Troubleshooting already done:
- Moved Destiny 2 from exFAT D: drive to NTFS C: drive
- Reinstalled Steam outside Program Files to C:\Steam
- Reinstalled Destiny 2 fresh
- Deleted and reinstalled BattlEye service
- Verified Destiny 2 and BattlEye file signatures as valid
- SFC found and repaired corrupt Windows files
- DISM completed successfully
- File permissions show my user has Full Control
- Defender logs do not show a clear block
- Code Integrity/AppLocker logs did not show a Destiny/BattlEye block
- Process Monitor shows BattlEye and launcher activity, but no clear ACCESS DENIED result
- BattlEye reaches the “Launching game...” stage before the Windows access error appears
Windows version:
Windows 11 Version 25H2
OS Build 26200.8457
Request:
Please advise whether this is a known BattlEye/Destiny 2 PC launch issue, and what further logs or diagnostics are needed.
A small edit of what worked:
I reset my windows but chose to "keep data"- keeping all my files and whatnot but yeah, it seems the answer all along was just to do the most simple of things. I hope this helps anybody if anybody comes across it.
-
1 ReplyEdited by Crisidelm: 6/9/2026 2:54:18 PMI had the same problem some time ago; it turned out that a botched video driver update had left behind a single .dll in Windows/System32 that did not match the working video driver version set therefore it triggered BattlEye into believing there was a cheat disguised as that .dll file. I had to manually delete the file and replace it with the correct .dll version by loading a recovery OS from a USB pen... PS. the file was atiadlxx.dll, I remembered that I did not delete it, I just renamed it and replaced it with the correct version. It's still there in my System32...
-
4 RepliesNot sure if it'll work as its been a few years, but a common but semi-unreliable fix on here/Steam forums/Reddit was to go to the D2 game folder -> battleye -> run the service x64 as admin then launch Destiny directly as admin. Some had it work, others didn't; but given your list of thing's you've tried - its worth a shot.
