"Error: Failed to download configuration files from Bungie servers"
I am sure Bungie is at full throttle handling all the tasks at hand attempting to please their large fane base. Please comment and make these errors known so that they may find a solution. I have yet to be able to play this amazing game due to this error, and I very much look forward to that moment to even choose my class. As I am sure most of you have done, I have also attempted every fix possible with no prevail. Like, comment, and keep posting to make these errors be annihilated.
BattleTag: Wolf #11507
Configuration Info
CPU: Intel Core i7-6700HQ
GPU: Nvidia GeForce GTX 1070 8GB
RAM: 16GB DDR4
GPU Driver Version: Nvidia 388.00
------------------
System Information
------------------
Time of this report: 10/27/2017, 20:51:10
Machine name: WOLFWARE
Operating System: Windows 10 Home 64-bit (10.0, Build 16299) (16299.rs3_release.170928-1534)
Language: English (Regional Setting: English)
System Manufacturer: Alienware
System Model: Alienware 17 R4
BIOS: 1.0.8
Processor: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8 CPUs), ~2.6GHz
Memory: 16384MB RAM
Available OS Memory: 16256MB RAM
Page File: 4933MB used, 14265MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 96 DPI (100 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Supported
DxDiag Version: 10.00.16299.0015 64bit Unicode
Issue Information
Destination/Activity: Home Screen/Pressing Enter
Description: When I press enter and the loading screen begins to check for updates, the game gives the Error : Failed to download configuration files from Bungie servers error code: nightingale
-
bungie just simply do not care about this error, coz they dont know how to fix it, 2021, since launch and here we are, I know they got a lot of work to do, but so many players may say goodbye to the game, this gives me a lot of helplessness 8(
-
was looking to fix dis problem and found dis thread. i'am shocked that dis problem been exist since 2017 and there is still no real solution from devs for dis. smh.. and yeah, i already tried all the official "solution" offered by devs.
-
what worked for me is changing from dhcp to a static ip for some reason
-
I discovered this fix after trying lots of methods discussed here, hope it helped you!
-
I have the same issue on PC, now is February and months have passed since i am unable to play. The fact that Bungie does not even care to answer anything except reinstall the game, is very concerning....
-
I have been having the same issue and have tried multiple different solutions that have given me no results. its very frustrating when the bungie solution to this is basically turn off and back on or reinstall game, however i have done both of those and it hasn't fixed the issue. i submitted a web ticket to blizzard to see what they could do and they referred me to this forum basically saying to hope bungie eventually fixes this issue. does anyone have luck with any solutions because i have not.
-
2 RepliesI was helped by this method: Delete Destiny2.exe file and check the client files for errors via battles.net. Although the error appears periodically, after performing these actions, the game starts to work for several days.
-
Same problem. Started happening after the hotfix. Ive tried just about everything to fix it.
-
Was facing the same issue - "Failed to download configuration files from Bungie servers error code: nightingale" What did the trick for me is to change DNS to google (8.8.8.8 and 8.8.4.4), got the solution from this thread https://www.bungie.net/en/Forums/Post/236965675?sort=0&page=0&path=1 I've also disabled IPv6 Played a game for about an hour, tied re-launching it a couple of times - work fine for now
-
3 RepliesPOSSIBLE SOLUTION: [url]https://www.youtube.com/watch?v=IAkUu8WN_XY[/url] This morning I found this and tried it. It didn't work for me immediately. But somehow this afternoon, I tried to launch the game again and it works! Note that I got this error from the getgo and had never been able to pass through the first loading screen. I tried all the fixes for days not thing works until this one. So good luck and let other players know whether if it fix your game too.
-
Edited by Espiri: 10/28/2017 5:58:51 PMupvoted. If u have the same problem, please upvote this to increase visibility of the issue to bungie support. Up to this point, apparently they haven't even acknowledged this error code in their official known issue post ... P.S: I even factory reset windows 10 and did a fresh install of the game. It did not work. So yah, don't waste more time trying that.
-
I'm encountering the same issue. I've reinstalled the game 3 times, adjusted firewall settings, updated drivers, cleared caches, and adjusted network settings. I've tried every single fix for the beta and full release with no results. This is extremely aggravating, seeing as out of nowhere the game worked fine for about an hour, and boom! Back to square one. I'm surprised that out of the 4-5 threads of this I've seen there hasn't been a single official response from bungie on the matter. Please help! Even an acknowledgment at this point would be appreciated.
-
2 RepliesI have been having the exact same problem. I got Destiny 2 to work for a little bit when I reinstalled the game. Then, the next time I started it up after restarting my computer I got the "nightingale" error again. I've tried clearing all my cache, defragmenting disk, changing firewall settings, nothing has worked. It seems like a bit of a waste to have to reinstall the game after playing for a couple hours every time. Especially when it takes about a day and a half to download because you are deployed to a foreign country.
-
Alas, the error returns after thinking it was fixed. Sad day. Just keep trying to log in and hope a miracle.
-
1 Replyi have this error too.... why not fix this ?
-
A friend and I have both had this problem, then all of the sudden the game launched on its own! Just keep trying, as far as I can tell, just submit your error and let Bungie do what they can. There is not a fix you can do on your own.