This error has to be the most annoying thing I've come across because the cause is random, making it impossible to pin down the source, solutions found online (and by bungie) aren't consistent and most solutions online are doing some random weird things, indicating even more it's not just a "corrupted file error". Please for the love of god at least say something about it
[u][b]Solutions I tried that worked temporarily, on PC (like I said before, since it's random, don't even get your hopes up if you're looking for a solution that works):[/b][/u]
- Downloading/Changing the language and changing back (lasted a day)
-Reinstalling the game (lasted a few days)
[u][b]Solutions I've tried that didn't work:[/b][/u]
- Reinstalling the game on a different drive
- Changing my -blam!- ram sticks even though memory diagnostics didn't show anything (yes, I went out to buy new ram sticks)
- Deleting every file in the game directory except the packages folder and then redownloaded/verified files
- Uninstalled then reinstalled Battleye
- Delete every other game besides D2 that uses Battleye
- Allow D2 through the firewall for both Private and Public networks
- Making sure my drivers are up to date
- Restarting my router
- regedit solution
- Deleted and verified the "w64_sr_environments_0110_0.pkg" file
I've almost had enough man. I don't have the data to constantly reinstall d2 and it's impossible to even play the game sometimes
Edit (30/05):
I literally went into the tower to get bounties. Went to the moon to do them. Then when I travelled back to the tower, I got marmot. What the actual -blam!- is wrong with this game
-
1 ReplyHave you tried uninstalling then doing a drive repair? This could be an instance of a bad partition on the drive that you are installing the game on over and over
-
5 Repliesi have the same problems and the fact no one say nothing about is most stupid and unprofessional think i ever see, i pay for season that i cant play just ridicolous how they managed situation.
-
1 ReplyWindows 10/11?