Get a working client

DriftwoodXI runs on the real FINAL FANTASY XI client, on the build Square Enix shipped in September 2026: 30260904_1. Do not use an up-to-date retail client. Download the September client from the #getting_started channel in the Driftwood Gaming Discord instead. No Square Enix account. No subscription. Nothing to pay.

0. Which one are you?

Find yourself in this list, then start at the step it names.

  • You have never installed FINAL FANTASY XI. Start at step 1.
  • You have a client from Square Enix’s own installer, or one PlayOnline has updated since September. Start at step 1. It is not the build this server runs on.
  • You are already on 30260904_1. Start at step 2.

Where to read your build number

  • In the launcher. Look at the top bar. A chip reads Client 30260904_1. It shows what your client reported the last time you pressed Play, so it is only true after a launch.
  • In PlayOnline. Open the PlayOnline Viewer and click Check Files on the left. The screen names the FINAL FANTASY XI version, like Ver.30260904_1. You do not have to run the check to read it.

1. Get the September client from the Discord

  1. Join the Driftwood Gaming Discord.
  2. Open the #getting_started channel and download the September 2026 client (build 30260904_1) from there.
  3. Set it up as that channel describes, and note the folder your FINAL FANTASY XI client ends up in — step 2 needs it.

Do not update it. Logging in to PlayOnline, or running Check Files and File Repair, fetches the newest retail patch and moves you off the September build. You never need a PlayOnline ID, a registration code or a Square Enix account to play here.

Already have a client from Square Enix’s own installer? It will be on whatever build Square Enix shipped last, not September’s. Use the Discord download rather than trying to patch it.

2. Get the DriftwoodXI launcher

The launcher is the only other thing you need from us. It installs Ashita, keeps Ashita and all the add-ons matched to the server, and starts the game.

Get the DriftwoodXI launcher

  1. Install it. It installs for you only and does not ask for administrator rights. Windows SmartScreen may warn that the publisher is unknown — More info, then Run anyway.
  2. If you already have it, let it update itself. Take the update when the title bar offers it. You want 0.33.0 or newer; anything older cannot replace Ashita’s own files, which is what fixes blank item names on this build.
  3. On first run, press Install Ashita for me. Do not download Ashita yourself.
  4. Point it at your game folder if it asks — the FINAL FANTASY XI folder of the client from step 1.
  5. Create a DriftwoodXI account if you have not, add it in the launcher, and press Play.

3. If Windows Defender eats the game loader

Every so often a Defender definition update decides our game loader is a threat named Trojan:Win32/Bearfoos.A!ml. It is a false positive — Microsoft’s own analysts reviewed the file and found nothing. The !ml means a machine guessed, not that anything matched real malware. The symptom is the game refusing to start, often with the launcher saying the loader was removed.

  1. Open Windows Security → Virus & threat protection → Protection history.
  2. Find the Bearfoos entry for driftwood-xiloader.exe.
  3. Choose Restore, then Allow on device.

Both halves matter. The launcher rewrites that file every time you launch, so a file that was restored but not allowed gets taken again on your next Play.

If you would rather not touch Defender, waiting is also fine: Microsoft corrects these within a few days and the launcher puts the loader back by itself.

If it still refuses

What you seeWhat it meansWhat to do
Login fails with "The games data has been updated.", or the launcher says the login server refused the client version.Your client is on a build older than September’s. This is the server turning away an out-of-date client on purpose.Do step 1. Nothing else fixes this.
The game starts, but item names show as item 4940 or come up blank in the DriftwoodXI windows.Ashita is a version older than 4.3.2.0 and reads the new item files at the old positions.Update the launcher (step 2) and launch again. It replaces Ashita’s own files for you.
"Please wait while Windows configures PlayOnline Viewer" appears one to three times every time you start.A leftover registration from the PlayOnline installer makes Windows health-check the product, fail, and repair forever. Harmless, just slow.See the PlayOnline repair loop below.
Nothing happens on Play, and the Launch Log says Failed to locate profileServerPortAddress2!The loader could not recognise your PlayOnline files. Almost always a client that is not the September build.Do step 1, then try again. If it survives a completed update, post the log in the Discord.
The launcher says Windows Defender removed the game loader, or launching fails right away with no game window.Defender’s automated scanner flags our loader from time to time. It is a false positive.Do step 3.
Verify Game Files reports that a thousand files differ.The file list it compares against was made before a retail patch. Retail rewrites about a thousand files every patch.Ignore it. Only the missing list is worth acting on, and never by deleting DAT files.
PlayOnline asks for a registration code, or an ID and password.That is Square Enix’s own service. It is not us.You never need one to play here. Skip it, and do not log in to PlayOnline: that updates the client past the September build.

The PlayOnline repair loop

If Windows says it is configuring PlayOnline Viewer every single launch, the 2023 PlayOnline installer left a registration behind that can never finish repairing itself. The game still works; it just costs you twenty seconds a boot. To stop it, open Command Prompt as administrator and run this one line exactly:

reg delete "HKLM\SOFTWARE\Classes\WOW6432Node\CLSID\{E697F40A-B701-4F75-A201-635FA69A41B3}\InprocServer32" /v InprocServer32 /f

It removes one leftover value and nothing else. Only installs that came from Square Enix’s own installer have it, which is why this does not happen to everyone.

Still stuck

Ask in the Discord. Bring three things: the build number from your Check Files screen, your launcher version, and what the Launch Log says — that is the panel on the launcher’s home screen, with the News / Log switch set to Log. With those three, this is usually answered in one reply.

Playing on Linux?

Step 1 is the same: the September client from the Discord, inside your Wine prefix. Everything after that is different — the Linux guide is the one to read.