XivAlexander Autoload Not Working: Fixes
Autoload is convenient when it works and confusing when it does not, because a failure can look identical to the tool simply not being installed. The game opens normally, nothing obviously errors, and weaving feels unchanged. That silence is the clue: autoload either did not load the DLL, loaded it from the wrong place, or was disabled by a change you did not notice. This guide checks each of those possibilities in order, and it assumes portable mode already works, because if portable mode does not work, autoload is not your problem.
Step 1: Confirm portable mode works first
Test XivAlexander in portable mode, following How to Install XivAlexander on Windows and How to Check If XivAlexander Is Working. If portable mode fails, fix that first, starting with patch compatibility in XivAlexander Not Working After a Patch. If portable mode works but autoload does not, you have isolated the fault to the autoload configuration, which is a much smaller problem to solve.
Step 2: Check the DLL name, location, and game folder
Autoload depends on a DLL in the game folder with the exact name the game will load, d3d11.dll or dxgi.dll, depending on your setup. Check that the file exists in the game folder you actually launch from, not in an old installation, a backup folder, or the extracted XivAlexander folder. If you use Steam, XIVLauncher, or a standalone launcher, each may use a different game folder, and autoload configured for one will not affect the other. See XivAlexander Loader Cannot Find Game for the multiple-installation problem, which is also the most common autoload problem. After any install, update, or uninstall step, restart a running game; autoload changes do not apply to a game that was already open.
Step 3: Check for chain-loading and launcher overwrites
If you use ReShade or GShade, the DLL name collision described in XivAlexander with ReShade and GShade may mean the visual tool occupies the file name and XivAlexander is not chained through it, or vice versa. Check which tool occupies the name and whether a chain is configured. Separately, a game update or a launcher repair can replace files in the game folder, removing a manually placed DLL without warning. After any game update, re-check the game folder for your autoload DLL before assuming the tool broke. Antivirus software can also quarantine a DLL in the game folder; see XivAlexander Antivirus False Positive if a file disappears after a scan.
Step 4: Reset autoload cleanly and reconfigure
If checks do not reveal the fault, reset autoload completely: turn off automatic loading in the loader, delete any manually placed DLL you added for XivAlexander, restart the game to confirm it launches cleanly without the tool, and then set up autoload again from scratch, following the loader’s own option rather than copying files by hand. Test immediately after reconfiguring, and note exactly which game folder and which file name you used. A clean reset is preferable to layering a second autoload configuration on top of a broken first one, which is how duplicate and conflicting DLLs accumulate.
Frequently asked questions
Is autoload required?
No. Portable mode gives you the same latency feature, with an extra manual step each session. Autoload is convenience, not capability.
Why did autoload stop after a patch?
A patch can change the game folder contents, invalidate the build, or both. Turn autoload off, test the base game, and follow How to Update XivAlexander After a Patch before reconfiguring.
Can I use autoload with XIVLauncher?
Yes, if the game folder XIVLauncher uses is the folder you configured. See How to Install XivAlexander with XIVLauncher.
Autoload failures are configuration failures far more often than tool failures: wrong folder, wrong file name, missing chain, or a file removed by an update or a scan. Confirm portable mode, check the actual game folder, check the chain, and reset cleanly. When autoload works, it should be as boring as portable mode, just automatic.
Important: Final Fantasy XIV prohibits third-party tools that inject code into the game client or alter its network behaviour. XivAlexander is an unofficial, community tool, not affiliated with Square Enix. Using it carries a risk of account restriction. This guide is for information only; decide for yourself whether that risk is acceptable, and never use a third-party tool on an account you are unwilling to risk.
