Black screen after launching the game

I still need to rename the "steam_api64.dll", but with the new Steam beta (with the reworked overlay) I can activate the overlay for the game again and it works as it should :D

Once again, major patch, 6.4, the issue resurfaces for those who applied the temp fix, and requires the file to be renamed again. It's almost been a year and SE hasn't addressed it/fixed it.

Quote:

---

Originally Posted by CaffeinePanda

Once again, major patch, 6.4, the issue resurfaces for those who applied the temp fix, and requires the file to be renamed again. It's almost been a year and SE hasn't addressed it/fixed it.

---

Yup :/ at least this thread is starting to feel like home

what do i do if i dont use steam and have this issue?

EDIT: i renamed/removed said files but the issue persists

Hello everyone!

I had this issue after a new clean install of Win 11 on my laptop.
I tried every fix previously suggested but nothing really worked, exept the Steam .dll one (removed from its directory) but it was just a temporary fix.
After that I decided to make another clean install of the OS and then reinstalling all the drivers/updates available, now the game works like a charm, just like months ago!
I know that for some people this isn't still an optimal solution since doing a file backup, formatting the disks and then reinstalling everything could take a good chunk of time, but if you can it's definitely worth a try.

Hope this could help someone!

I just want to thank everyone who has helped in this thread. I recently just had this problem after factory resetting my pc and reinstalling the game. I got the black screen after clicking play and was able to fix it by renaming the steam_api64.dll file.

Stopping by again to confirm that:
- this thread is about a bug that prevents a number of players from logging in, unless they perform 1 of a handful of really specific workarounds, like renaming a particular file
- this thread is ~1 year old and hasn't received an official response, nor a fix, more importantly
- the actual issue is actually a little older, but this is just the thread that we happen to spend the most time on
- players have shared they asked SE support to attend this thread over the phone, but it hasn't eventuated into anything (anecdotal)

What is the issue:
- Client upon launching enters in a black screen state
- Client is not able to be forced closed using ctrl+alt+del or anything similar, as the task manager will open behind the window
- You can only force close by opening another desktop using win+tab, however, there's a better semi-permanent workaround

How to fix this issue:
1) visit your FF14 within Steam folder => <Steam Folder>\steamapps\common\FINAL FANTASY XIV Online\boot
2) find steam_api64.dll
3) rename it to steam_api64-bak.dll
4) repeat this every major patch e.g. 6.5, 6.6, 6.7, 6.8 and so on

Have a great day, friends.

Hi again! I recently had to reinstall Windows 10 onto my NEW drive as the old one was corrupt. So fresh Steam, fresh FFXIV. Just wanted to update that I am STILL having issues with this black screen nonsense since 6.2 and have not been able to access the game through normal means :)

Stopping by again to confirm that:
- this thread is about a bug that prevents a number of players from logging in, unless they perform 1 of a handful of really specific workarounds, like renaming a particular file
- this thread is ~1 year old and hasn't received an official response, nor a fix, more importantly
- the actual issue is actually a little older, but this is just the thread that we happen to spend the most time on
- players have shared they asked SE support to attend this thread over the phone, but it hasn't eventuated into anything (anecdotal)

What is the issue:
- Client upon launching enters in a black screen state
- Client is not able to be forced closed using ctrl+alt+del or anything similar, as the task manager will open behind the window
- You can only force close by opening another desktop using win+tab, however, there's a better semi-permanent workaround

How to fix this issue:
1) visit your FF14 within Steam folder => <Steam Folder>\steamapps\common\FINAL FANTASY XIV Online\boot
2) find steam_api64.dll
3) rename it to steam_api64-bak.dll
4) repeat this every major patch e.g. 6.5, 6.6, 6.7, 6.8 and so on

Have a great day, friends.

Quote:

---

Originally Posted by CaffeinePanda

Stopping by again to confirm that:
- this thread is about a bug that prevents a number of players from logging in, unless they perform 1 of a handful of really specific workarounds, like renaming a particular file
- this thread is ~1 year old and hasn't received an official response, nor a fix, more importantly
- the actual issue is actually a little older, but this is just the thread that we happen to spend the most time on
- players have shared they asked SE support to attend this thread over the phone, but it hasn't eventuated into anything (anecdotal)

What is the issue:
- Client upon launching enters in a black screen state
- Client is not able to be forced closed using ctrl+alt+del or anything similar, as the task manager will open behind the window
- You can only force close by opening another desktop using win+tab, however, there's a better semi-permanent workaround

How to fix this issue:
1) visit your FF14 within Steam folder => <Steam Folder>\steamapps\common\FINAL FANTASY XIV Online\boot
2) find steam_api64.dll
3) rename it to steam_api64-bak.dll
4) repeat this every major patch e.g. 6.5, 6.6, 6.7, 6.8 and so on

Have a great day, friends.

---

This is what worked for me.

I have been struggling with this issue for months, seemed to happen right around when I purchased all the DLC...
Support has been very unhelpful and continued to offer meaningless advice from port forwarding to re-installing steam.
It also seems that their support system is insanely not optimized as each time I would get a response from someone new.
I will continue to try to get them to acknowledge this issue but it seems that might not get anywhere as they do not seem to be recognizing the issue.

So far the only that that has worked for me have been the solutions posted here. As well I directed them to this thread multiple times and it seems they just ignore it...

Stopping by again to confirm that:
- this thread is about a bug that prevents a number of players from logging in, unless they perform 1 of a handful of really specific workarounds, like renaming a particular file
- this thread is ~1 year old and hasn't received an official response, nor a fix, more importantly
- the actual issue is actually a little older, but this is just the thread that we happen to spend the most time on
- players have shared they asked SE support to attend this thread over the phone, but it hasn't eventuated into anything (anecdotal)

What is the issue:
- Client upon launching enters in a black screen state
- Client is not able to be forced closed using ctrl+alt+del or anything similar, as the task manager will open behind the window
- You can only force close by opening another desktop using win+tab, however, there's a better semi-permanent workaround

How to fix this issue:
1) visit your FF14 within Steam folder => <Steam Folder>\steamapps\common\FINAL FANTASY XIV Online\boot
2) find steam_api64.dll
3) rename it to steam_api64-bak.dll
4) repeat this every major patch e.g. 6.5, 6.6, 6.7, 6.8 and so on

Have a great day, friends.

Quote:

---

Originally Posted by CaffeinePanda

Stopping by again to confirm that:
- this thread is about a bug that prevents a number of players from logging in, unless they perform 1 of a handful of really specific workarounds, like renaming a particular file
- this thread is ~1 year old and hasn't received an official response, nor a fix, more importantly
- the actual issue is actually a little older, but this is just the thread that we happen to spend the most time on
- players have shared they asked SE support to attend this thread over the phone, but it hasn't eventuated into anything (anecdotal)

What is the issue:
- Client upon launching enters in a black screen state
- Client is not able to be forced closed using ctrl+alt+del or anything similar, as the task manager will open behind the window
- You can only force close by opening another desktop using win+tab, however, there's a better semi-permanent workaround

How to fix this issue:
1) visit your FF14 within Steam folder => <Steam Folder>\steamapps\common\FINAL FANTASY XIV Online\boot
2) find steam_api64.dll
3) rename it to steam_api64-bak.dll
4) repeat this every major patch e.g. 6.5, 6.6, 6.7, 6.8 and so on

Have a great day, friends.

---

It is absolute ridiculous this SPECIFIC ISSUE has not been FIXED or even acknowledged, and yeah it takes two seconds so no big deal BUT THAT ISN'T THE BLOODY POINT

Hmm, I don't play the game on Steam, but had this very same issue after the patch. I repaired the game and it started working. I have renamed the file, let's see if it reoccurs later.

I was really confused for a second about the blackscreen after the update - and then I remembered...

I had to do it again after the update. You'd think they'd fix it after all this time.

Stopping by again to confirm that:
- this thread is about a bug that prevents a number of players from logging in, unless they perform 1 of a handful of really specific workarounds, like renaming a particular file
- this thread is ~1.5 years old and hasn't received an official response, nor a fix, more importantly
- the actual issue is actually a little older, but this is just the thread that we happen to spend the most time on
- players have shared they asked SE support to attend this thread over the phone, but it hasn't eventuated into anything (anecdotal)

What is the issue:
- Client upon launching enters in a black screen state
- Client is not able to be forced closed using ctrl+alt+del or anything similar, as the task manager will open behind the window
- You can only force close by opening another desktop using win+tab, however, there's a better semi-permanent workaround

How to fix this issue:
1) visit your FF14 within Steam folder => <Steam Folder>\steamapps\common\FINAL FANTASY XIV Online\boot
2) find steam_api64.dll
3) rename it to steam_api64-bak.dll
4) repeat this every major patch e.g. 6.5, 6.6, 6.7, 6.8 and so on

Have a great day, friends.

same issue... seems to be affecting a lot of people, wonder why there isn't any news on why this is happening.

Yea, I just found this was happening to me too after rebuilding my computer and installing Windows 11. I didn't have this problem before I switched to Windows 11 since my last computer had Windows 10 on it. So simply having to remove the steam_api64.dll after update is only solution?

I have been tempted to try reinstalling Windows 11, just to see if it did anything since I am not sure what is making the game "sometimes" get black screen on startup, and get a black screen on exit "everytime". I'm not sure what steam_api64.dll does but it seems it was breaking the connection between the game, and the computer whenever you exit the game.

I had this issue now happening to me too, just to find out that this bug is present for at least 2 years? This is ridicules. Renaming the steamclient file did work however. Thanks for that!

This is happening to me as well. Closing Steam after logging in works, but renaming the dll did not.

New patch same issue with a little FLAIR

None of the provided solutions work. Closing Steam after logging in doesn't work. Deleting or renaming the dll will ensure that steam doesn't even load the launch page. It just closes itself. Thanks Square!

EDIT: Wasn't following the directions of the first post correctly. Force closing Steam did the trick.

Experiencing this same issue, started last night. After roulettes I was walking around Limsa, and everything except chat locked up. When attempting to quit, I received "An unexpected error has occurred. Exiting FINAL FANTASY XIV.16a." Since then, I am unable to launch the game. Windows 11 (22631.3296), AMD 24.3.1, Steam version 1709846872. This only started after patch 6.58 for me, but I have all of the same symptoms as described from some posts in 2022.

Yeah, simply renaming the .dll doesn't work anymore for me as well.

An alternative to closing Steam that is working for me is to keep the .dll-filename like it was installed, open the launcher, enter the credentials and verify your login data BUT DON'T CLICK TO START THE GAME YET, open your installation folder, rename the .dll to something else, click the play button, wait for the game to start und rename the .dll again (so that the launcher is working the next time). Quite a hassle to just play the game...

Steam User here!
https://prnt.sc/iBxv7-9Pobou
"Unable to complete the version Check"
Before patch , played normaly

Not sure exactly what did the trick, but here's what I generally did - I'm up and running again.

1. Made sure Windows and my GPU drivers were up-to-date.
2. Ran "DISM /Online /Cleanup-Image /CheckHealth" and "sfc /scannow" because why not.
3. Restarted my workstation.
4. Uninstalled the game from Steam.
5. Completely deleted the folder C:\Program Files (x86)\Steam\steamapps\common\FINAL FANTASY XIV Online.
6. Disabled all overlays (Discord, Steam, Windows Game Bar).
7. Completely deleted the folder C:\Users\<USERNAME>\Documents\My Games\FINAL FANTASY XIV - A Realm Reborn.
8. Reinstalled the game from Steam.
9. Allowed the game and patches to download over night.

Hope this helps someone else get back into Eorzea.

Quote:

---

Originally Posted by Drannaos

Not sure exactly what did the trick, but here's what I generally did - I'm up and running again.

1. Made sure Windows and my GPU drivers were up-to-date.
2. Ran "DISM /Online /Cleanup-Image /CheckHealth" and "sfc /scannow" because why not.
3. Restarted my workstation.
4. Uninstalled the game from Steam.
5. Completely deleted the folder C:\Program Files (x86)\Steam\steamapps\common\FINAL FANTASY XIV Online.
6. Disabled all overlays (Discord, Steam, Windows Game Bar).
7. Completely deleted the folder C:\Users\<USERNAME>\Documents\My Games\FINAL FANTASY XIV - A Realm Reborn.
8. Reinstalled the game from Steam.
9. Allowed the game and patches to download over night.

Hope this helps someone else get back into Eorzea.

---

Thanks for sharing, but I believe this has already been done before as mentioned by other players in this thread (plus someone even made a complete windows reinstall) yet the issue usually comes back a few weeks later.

As also been mentioned by someone who got a response from tech support this is an old bug/issue with FFXIV client that SE still was not able to fix. Seems that only steam users are affected.

!!! Could anyone moderating this Technical Support forum branch please pass along a message to Tech Support that last update broke only semi-reliable fix for this issue by making "steam_api64.dll" (FFXIV "boot" folder) mandatory during launcher start-up !!!

Got the exact same problem after todays patch completely out of nowhere, whats strange is that when i logged in right after updating the game it worked fine, came back later again tried logging in and got the blackscreen. Im not even sure what fix still works.

Same issue as everyone else. Renamed the DLL file and it was working until this latest patch not i have to jump through hoops just to play the game. Would be nice to transfer accounts to a non steam one or just have this issue resolved as it has been ongoing for years now

Same issue.
Have been doing the steam_api64-bak.dll for a month now.
A fix would be great.

After using the task manager Steam shutdown fix for a long time, today I was able to load the game normally without issues. Is this fixed for anyone else?

@KooriGraywolf Glad it works for you, you are the chosen one for today haha

I've been playing for a month casually and i've never been able to launch the game properly...
All i can do is the task manager Steam shutdown fix...
I've tried everything, it is frustrating that nobody knows exactly what's up !

How can the technical support be so silent about this issue among Steam Users.

Unfortunately, I haven't deliberately changed anything for it to work. I think even at the start of Dawntrail I still had this problem. Then somewhere along the line something happened (maybe in one of the patches) that then made it work on my PC. But I didn't try starting FF14 normally on every single patch just out of having of ending the Steam process in the task manager, so if a patch solved it then I don't know which one..

But I haven't changed PC or Windows version of anything, other than Windows' periodic updates (which I doubt have anything to do with it) and FF14's patches.

Quote:

---

Originally Posted by HuaTuo

I logged into the game just fine yesterday. Now, after downloading the 6.2 patch, after clicking on "play", game launches, expands to fullscreen, but the screen stays black. When I click mouse button while on the black screen, the game closes and I have to re-start launcher, put in login details again, rinse and repeat. Is this happening to anyone else?

---

This same EXACT thing is happening to me, so frustrating. Something in the patch is messing us up.

while my symptoms are exaclty like yours, these fixes did not work for me

UPDATE

Updating my graphics driver seems to have done the trick

Found a solution that possibly circumvents the issue without sacrificing steam's functionality:
1. Install XIVLauncher, launch it and tick "Use Steam service account", login and quit the game
2. Find FINAL FANTASY XIV ONLINE in your steam library and add "C:\Users\**YOUR USERNAME HERE**\AppData\Local\XIVLauncher\XIVLauncher.exe %command%" launch option in properties
3. Launch normally through Steam

So far so good, tell me what you think

Quote:

---

Originally Posted by KolpoPirate

Found a solution that possibly circumvents the issue without sacrificing steam's functionality:
1. Install XIVLauncher, launch it and tick "Use Steam service account", login and quit the game
2. Add "C:\Users\**YOUR USERNAME HERE**\AppData\Local\XIVLauncher\XIVLauncher.exe %command%" launch option in your steam library
3. Launch normally through Steam

So far so good, tell me what you think

---

I would LOVE to get this work, but no luck here. I'll keep trying.
AMD System.
I've been using the dll rename start, rename back for the past couple months.
Trying the XIV launcher in hopes I can get chat and screenshots going again.

HUZZAH it works. Finally.
So The Add instruction is for the original FFXIV Launcher in Steam, not adding the XIVLauncher. After running XIVLAUNCHER, getting that working, add the launch command to the OG FFXIV program setting in steam.
Also, be sure to turn back on the switch for steam overlay in the settings for the FFXIV Steam. I'd turned it off in og debugging.

Thanks KolpoPirate! I've been wanting this fixed for a long time.

That's great news, i'm glad it worked. I've clarified step 2 a bit just as you said too
Sometimes the game still crashes on launch but second launch does the trick. Since XIVLauncher remembers your password etc i can live with that

I found a "solution", of sorts... not a pretty one, but in the end it turned out to be the most time effective for me.

In short, I figured that my installation of Windows had gotten some kind of bit-rot, that made FFXIV unable to run, because it worked just fine on another computer.

So I...

1) Took a backup of documents, pictures, music, etc

2) Wiped C: and reinstalled Windows, Steam and FFXIV

Took me about 2 hours... and that is minor compared to the amount of time I have spent banging my head against the black screen.

Sorry I could not provide a more elegant solution, but at least it is effective.

//Shridia

I have been trying to help a friend with this issue for weeks, and none of the steam based help worked, however, if you are using a nvidia driver, that can be the culprit, updating the driver can solve the issue.

looking through the forum you can tell that the issues began during 6.2 which was the beginning of the graphical updates for FFXIV for Dawntrail, causing issues with nvidia drivers, updating, or waiting for updates for the new drivers, seemingly only laptop nvidia graphics cards are having this issue (if you are having this issue otherwise please let me know.)

while i was looking at path notes i noticed that the reason why it seems to only occur on "major updates" is because that is when their graphical overhauls occur.

however this only works if steam itself itself is not the direct culprit.

if the steam fixes dont work, and you have an nvidia driver, this might be a solution.