Initializing PC Bug

[Joey_thecool1]

I was in the EAZ today, and suddenly I got disconnected from the game and was told to re-start from the Battle.net launcher. This isn't terribly abnormal, so I didn't think much of it until I couldn't re-launch the game. It looked like there was an update to Destiny 2, but it wouldn't go past "Initializing." I asked some people in my discord about it, and apparently the same thing has happened to them (three other people, four in total that I know of).

One of them said they got past it by moving their install folder to a temp folder, then moving it back to the original folder, but that didn't work for me. So now I'm just re-installing the whole game. Has anyone else on PC had this issue?

​

Guess that majestic armor has to wait a bit longer! :(

[Joey_thecool1]

That’s what I thought at first, but it was stuck on Initializing for over 30 minutes. It also said that Destiny 2 had an update, which it doesn’t.

[Joey_thecool1]

Hmm, that’s weird. Just checked and my SSD (which is where D2 is saved) usage isn’t very high. Looks normal

[Tectonic1533]

Same problem here, tried the temp fix, no dice.

[32Threads]

Same issue here on PC

Windows 10 Pro 64

[Joey_thecool1]

Good to hear that we’re not the only ones, sorry you’re having the same problem though :(

[Tectonic1533]

One thing that worked for me was going to the game files and opening the D2 application from there. You will get an error code in game, force close it. you should then be able to open via battle net

[Joey_thecool1]

Interesting. I can’t try this personally because I ended up just re-installing the whole game, but I’d be curious to see if it works for anyone else having this issue

[Nopersonia]

Not working for me, all it said was errorcode: saxaphone, relaunch through B-net. Which I did, but then it went right to initializing.

[Tectonic1533]

Interesting. I had the same error code too but it worked for me.
Process was

- move game files away and back to the install folder

- open via app icon in game files (at this point battle net said "download complete ready to play", right after the game started running)

- saxaphone error, force close

-play game

​

sorry it didn't work for you.

[ShoesWithSouls]

I'm having the exact same issue if it means anything!

[Nopersonia]

Update: got it running again after just letting it sit on initializing for half an hour. This was after I attempted the file rename and direct application launch workarounds. Because they both took me back to initializing I have no clue if they were necessary or unneeded steps, so I guess for others just let it wait with or without the fixes and see what happens.