JavaScript is required to use Bungie.net

Forums

Edited by Kiro - 13: 8/26/2021 11:57:06 PM
12
I found a potential work around for win10 users. worked for 3 ppl so far, a 4th going to get back to me after some game time. If it works for the 4th person I'll let ya all know, it is battle eye as the root cause if this is indeed a fix. [b] [i]UPDATE:[/i][/b] [i]Step1) You need to locate battle eye in folders C:\Program Files (x86)\Common Files\BattlEye, and take ownership of the files then give all users and system users full control. Step2) Repeat the process for battle eye located in C:\Program Files (x86)\Steam\steamapps\common\Destiny 2 Notes: should be 4 files in total between common files and steamapps. Step4) Enters windows firewall with advanced sec. on the left hand side of the app GUI select "inbound rules". Then select "new rule", select program, select the path to the battle eye files in C:\Program Files (x86)\Common Files\BattlEye & allow full access. Step5) Repeat step 4 with battle eye fles located in C:\Program Files (x86)\Steam\steamapps\common\Destiny 2, allow full access. Step6) repeat step 4 but now "out bound" to battle eye files located in C:\Program Files (x86)\Common Files\BattlEye, allow full access. Step7) Repeat step 6 for battle eye files located in C:\Program Files (x86)\Common Files\BattlEye, allow full access. Notes: You will need to name the rules, I just went with customBattleEyePath1, customBattleEyePath2, customBattleEyePath3, customBattleEyePath4 as an example. One of four users that have used this method/process with 100% success rate so far reported he was missing one file for out bound rules (As in no option/non-visable battle eye app/program).[/i]
English

Posting in language:

 

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

  • Yeah, also missing a file. I only have one sellectable Battleye file.

    Posting in language:

     

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

  • Mind sharing with us

    Posting in language:

     

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

  • I dont release untested work, im not bungie. i'll let you know after the 4th gets back.

    Posting in language:

     

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

  • Haha nice 1 Shots firee

    Posting in language:

     

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

  • Its worked for the forth person. Step1) You need to locate battle eye in folders C:\Program Files (x86)\Common Files\BattlEye, and take ownership of the files then give all users and system users full control. Step2) Repeat the process for battle eye located in C:\Program Files (x86)\Steam\steamapps\common\Destiny 2 Notes: should be 4 files in total between common files and steamapps. Step4) Enters windows firewall with advanced sec. on the left hand side of the app GUI select "inbound rules". Then select "new rule", select program, select the path to the battle eye files in C:\Program Files (x86)\Common Files\BattlEye & allow full access. Step5) Repeat step 4 with battle eye fles located in C:\Program Files (x86)\Steam\steamapps\common\Destiny 2, allow full access. Step6) repeat step 4 but now "out bound" to battle eye files located in C:\Program Files (x86)\Common Files\BattlEye, allow full access. Step7) Repeat step 6 for battle eye files located in C:\Program Files (x86)\Common Files\BattlEye, allow full access. Notes: You will need to name the rules, I just went with customBattleEyePath1, customBattleEyePath2, customBattleEyePath3, customBattleEyePath4 as an example.

    Posting in language:

     

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

  • @Kiro-13 you mentioned one person was missing a file in Battleye folder. Do you mind sharing how you worked around that? I am starting to think there's one file that's just not recognized properly by the system. I did everything else from the suggested list, but with just 6 new paths created and that one file missing, it doesn't work. Thank you in advance!!!

    Posting in language:

     

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

  • reinstall or battle eye, or have some one copy the file and send it to you and extract it or place it in the proper folder.

    Posting in language:

     

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

  • Thank you! Actually found a bit of a different solution. Seems that when I first installed Battleye, it corrupted some core files on the user profile. My cmd prompt stopped working which I only noticed when I was trying the 1000th workaround. So what I did was: - created a new user profile - installed destiny - ACCEPTED battleye from the beginning lol - Launched like a charm Best of all, now works on the original profile as well, even though I still can't find why cmd broke.

    Posting in language:

     

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

  • so a clean install of battle eye?

    Posting in language:

     

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

  • Yes! But from another user! On my original user - I first 'declined' but then when I verified files and installed the Battleye -- something got messed up, and I couldn't start, install, uninstall any of the Battleye files. Turns out something happened with the cmd prompt, which I'm still trying to figure out. So on the new user, I just logged into Steam, installed Destiny2, installed Battleye when prompted and it freaking worked. Also on the other user, cmd prompt works as usual. Crazy.

    Posting in language:

     

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

  • Edited by Kiro - 13: 9/1/2021 6:38:39 PM
    This is likely having to do with permissions or admin rights if i had to guess, but thats just a shot in the dark. as id have to look at myself to make a more educated guess.

    Posting in language:

     

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

  • It's a complete mystery, really isn't connected to permissions, it's on the admin profile, checked and rechecked all the settings. I'm also in tech but my knowledge goes just so far lol will dig in deep with an expert - their guess is it's corrupted file, but we'll know more when they dig it up.

    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