XIVLauncher Error

[TuggerJaegger]

Update disclaimer

• [X] Yes, I have checked and my issue is not related to FFXIV updating and plugins not working correctly.

What did you do?

I'm getting for two straight the same XIVLauncher error with the text:

''Failed to inject the XIVLauncher in-game addon. Please try restarting your game and your PC. If this keeps happening, please report this error.''

I never got this specific error before after a game update and updating the launcher, but ever since i started using the Launcher months ago, i have to CTRL+ALT+DEL to force quit it when it gives me a system sound and the window is unresponsive and not starting the game properly.

after force quitting it always shows the error:

''XIVLauncher could not start the game correctly. This may be a temporary issue. Please try restarting your PC. It is possible that your game installation is not valid.''

Platform

Windows

Wine/Proton runner version

No response

Relevant log output

No response

[NotNite]

Could you please attach %AppData%/XIVLauncher/dalamud.log?

[TuggerJaegger]

Could you please attach %AppData%/XIVLauncher/dalamud.log?

how do i do that? the site doesn't allow .OLD files as attatchment

[Kyouki-DotExe]

dalamud.log

got the same error, here is my log

[NotNite]

how do i do that? the site doesn't allow .OLD files as attatchment

Sorry for the long wait, getting around to our issues again. Is this still happening? Can I redirect you to our Discord server? We have a bot that can parse your logs.

[chenasraf]

Same error, happened several times... Fixed itself once, now happens again... Not sure what's the cause exactly.

My log is attached:

log.txt

[reiichi001]

@TuggerJaegger and @Kyouki-DotExe, is this still happening? There have been a few Dalamud updates and FFXIV patches since this issue was opened, and this issue may be stale now.

---

@chenasraf It looks like you may have some broken/outdated plugins that are crashing Dalamud. Most of the log you attached was just a single troubleshooting blob, and I could not find a full launch's worth of logs. In this case, please try removing (or move elsewhere) your devPlugins and installedPlugins folders and try launching that game with XIVLauncher.

Please let us know if you're able to launch and use Dalamud without any plugins installed.

[chenasraf]

Thought so too, I removed both directories to another location and tried again.

In my case (before and now both) FFXIV never booted, didn't crash after booting, but before. I tried looking live at the log file, noticed it wasn't updating - that log that I sent was probably from the working session yesterday.

Found dalamud.boot.log, which did update every time I tried to boot. Maybe it could help?

Also might be related or not, but I'm running Windows 11 ARM.

dalamud.boot.log

[reiichi001]

@chenasraf The dalamud.injector.log might have some useful information, but this could be a Windows on ARM issue in your case. You will want to check your computer's settings for x64 emulation support, and to make sure it uses the libraries we provide instead of native ARM ones. It is entirely possible that Microsoft's x86/x64 emulator is not compatible with the tools we use to modify FFXIV's process for Dalamud.

[chenasraf]

It worked yesterday, and as I said, the error happened before, and "fixed itself" (in reality - I don't know what changed in the environment to cause it to not reproduce).

So what you're saying might be true, but I'm not sure how to approach this.

Injector log seems a bit more informative, saying it timed out after 21s.... Could I increase the timeout somehow to know if that might be enough?

Here is the log:

dalamud.injector.log

[reiichi001]

Injector log seems a bit more informative, saying it timed out after 21s.... Could I increase the timeout somehow to know if that might be enough?

The FFXIV process should be there the moment the game is launched (it's run before Dalamud). If it's not able to find the game window after 21 seconds, injection has for sure failed, although it's harder to determine the cause in that case. It could be a process being blocked by an antivirus, it could be something inconsistent the x64 emulator is doing (we see this on Apple Silicon because it will not always map the memory consistently), or it could be another injector like Rivatuner/RTSS/MSI Afterburner, FRAPS, etc.

[chenasraf]

Injector log seems a bit more informative, saying it timed out after 21s.... Could I increase the timeout somehow to know if that might be enough?

The FFXIV process should be there the moment the game is launched (it's run before Dalamud). If it's not able to find the game window after 21 seconds, injection has for sure failed, although it's harder to determine the cause in that case. It could be a process being blocked by an antivirus, it could be something inconsistent the x64 emulator is doing (we see this on Apple Silicon because it will not always map the memory consistently), or it could be another injector like Rivatuner/RTSS/MSI Afterburner, FRAPS, etc.

I see... I am using Apple Silicon so that must be related. Any known fix/workaround/thing to try?

[reiichi001]

I see... I am using Apple Silicon so that must be related. Any known fix/workaround/thing to try?

You probably want to use XIV On Mac instead of XIVLauncher in Wine/CrossOver. The've had to make several adjustments to Wine/CrossOver to handle FFXIV correctly.

https://www.xivmac.com/

[chenasraf]

I see... I am using Apple Silicon so that must be related. Any known fix/workaround/thing to try?

You probably want to use XIV On Mac instead of XIVLauncher in Wine/CrossOver. The've had to make several adjustments to Wine/CrossOver to handle FFXIV correctly.

https://www.xivmac.com/

Had no idea there was a Mac equivalent 😮 I tried the official Mac client but it didn't work for me... that was a while ago. Giving this a shot, thank you!