A fix for BattleEye failing to run destiny2launcher.exe, destiny2.exe, etc.
Last night I was toying with permissions for my WindowsApps folder in hopes of finding the Destiny 2 installation folder and maybe a .ini to change the language on the game without changing the locale of my system. I play on the PC XboxApp and Microsoft doesn't make it easy to change the language like Steam. Well, it messed something up and I started getting these errors. Launching the game from the app starts BattleEye but it can't launch the game. Running destiny2.exe directly would load the game but stop short of sign-in with a PLOUT error (BattleEye failed to launch with the game). The change in permissions didn't affect any other game luckily. After uninstalling and reinstalling and speaking with Windows support and twelve plus hours later I got it figured out. I don't know exactly what the issue was, but in general it is permissions.
[url=https://www.winhelponline.com/blog/windowsapps-folder-restore-default-permissions/?expand_article=1]Here's a link to the article that helped me step by step reset permissions
[/url] I know what it's like to have a problem and find a solution online only for the article/tool to no longer be available, so in case you're reading this in the future and the article is gone I will provide the steps here.
The following commands should be typed in an elevated command prompt. Press "Win + X" and a little menu will pop up, click the admin option of Command Prompt/PowerShell.
First, make sure you do have ownership of the WindowsApps folder
[b]Command #1[/b]
[quote][i]takeown /f "%programfiles%\WindowsApps"[/i][/quote]
You should see:
[quote][i]SUCCESS: The file (or folder): "C:\Program Files\WindowsApps" now owned by user "computer_name\user_name".[/i][/quote]
[b]Command #2[/b] applies default permissions to the WindowsApps folder:
[quote][i]cacls "%programfiles%\WindowsApps" /s:"D:PAI(A;;FA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;OICIIO;GA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;;0x1200a9;;;S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204)(A;OICIIO;GXGR;;;S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204)(A;;FA;;;SY)(A;OICIIO;GA;;;SY)(A;CI;0x1200a9;;;BA)(A;OICI;0x1200a9;;;LS)(A;OICI;0x1200a9;;;NS)(A;OICI;0x1200a9;;;RC)(XA;;0x1200a9;;;BU;(Exists WIN://SYSAPPID))"[/i][/quote]
When you’re prompted with the question, Are you sure (Y/N)? type Y.
[u]Alternatively[/u]
[b]Command #3[/b] will also change the owner of the folder back to TrustedInstaller
[quote][i]icacls "%programfiles%\WindowsApps" /setowner "nt service\trustedinstaller"
[/i][/quote]
If that succeeds you will see:
[quote][i]processed file: WindowsApps
Successfully processed 1 files; Failed processing 0 files[/i][/quote]
If it fails it's probably because the the second command worked the first time.
It's important to note that calcs and icalcs are essentially the same with calcs being deprecated and no longer planned to be included in future Windows releases. It's also important to note to [b]never make changes to the WindowsApps folder[/b] if you don't know what you're doing. I hope someone finds this as helpful as I did.
Aiat.
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.