[LAST UPDATED: 01/17/17 @ 3:02AM]

If there are issues with fixes that you have figured out, please send me Delkathus(Duriel) a message on discord and I will add it without breaking this layout of this page.

The auto-installer and manual installer can run into issues, some very simple and some very complicated. I have compiled a list of issues that have occurred when installing and setting up to play on Supernova. This will help both GM's and users resolve issues that may occur when setting up this tasty treat.

Windower4 Loads POL instead of xiloader

This only occurs when the pol.exe file was not replaced with the patched file. The fix is simple and easy to do. Go into the directory c:\program files(x82)\playonline\playonlineviewer\ and change the following file:

This should resolve the issue with pol running instead of xiloader.

The above solution is if you don't want to have a cluttered xml file. This was the method of the old auto-installer. It's xiloader but you don't need the <executable>xiloader.exe</executable> argument in it. Both ways work. It's all based on preference.

Windower4 Crashes when launching

There is a various amount of reasons for Windower4 to crash when loading. Here is a compiled list of the known issues I have dealt with the past while and the solutions to them. To find out why Windower4 is crashing look in the program directory and open (crash.log) with notepad. It should look like the following image. This will look confusing at first but the line you want is the first line that's highlighted, it shows what exception is thrown at you.


System.IO.IOException: The process cannot access the file 'C:\Program Files (x86)\Windower4\scripts\autoload\autoload.txt' because it is being used by another process. The autoload feature for Windower4 cannot access read/write/delete permissions to the file, requires administrative access when ran. Or the file is currently being used by another program, close the program that is using it and try again.
System.TimeoutException: The operation has timed out. Windower4 timed out when executing the hook functions. This happens when the Windows Control Settings are high and make you accept usage of the file. This will cause the program to time out and crash when loading the hook. Can also be the cause of Directx9 runtimes not being present when the client calls them.
System.ComponentModel.Win32Exception (0x80004005): Access is denied. This means that the required files are not available. Or the access to said files are restricted. This can be happening if the VISUAL C++ Dist was not installed properly or failed to complete install. This can also occur if the Universal C Runtimes are not installed via Windows Update on Windows.
System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified xiloader or pol.exe cannot be found by windower. Most common cases is that there is a syntax error occurring. i.e (POL.EXE.EXE ect.). This will cause windower to obviously crash and burn. Check files are spelled correctly and in the correct folders with administrative access.

Xiloader Issues

Unknown Command Arguments

15625933 1551409684886003 1076537220247584765 o

The solution to this can vary, usually this will indicate that there are not enough sufficient arguments that xiloader requires. Here are a few steps to follow to resolve this issue.

Add the following arguments to settings.xml between <profile name=""></profile>:

  • <args>--server</args>
  • *NOTE* You do not need at all this argument. <executable>xiloader.exe</executable>. Why you ask? Very simple. The old auto-installer would rename pol.exe to pol_org.exe and rename xiloader.exe to pol.exe. If you want to have it normal then by all means do so lol.

If you have set the correct server ip and it still gives you this noise then do the following.

  • Right-click the Windower4 Desktop icon and select properties.
  • In the Target field, everything at the end needs to be deleted, do not delete the file location. Add the following to the command to the end of the command line. --p=""
  • Before you go all correct happy, yes.. That is the profile argument. HOWEVER! Xiloader will force a manual login if this is present regardless of arguments present. This is what we want.
  • Rarely, but having not update FFXI via file check can give this error as well. Very rare it will occur. But it can happen.

This will make xiloader do the manual login/account creation and should let you login.

If this still occurs then the last thing to do is to run a File Check to see if the game version is up to date. Even though you do it at the installation it can sometimes derp and not update the vtable properly. Also remember to delete the vtable files before doing the file check to ensure accuracy.

Login Loop

16143351 1876647609031548 5196859915092633904 n

When you are getting this lovely screen it can mean 2 things.

  • The account password and/or username were incorrect.
  • The login Server is down and is rejecting login attempts.
If you believe the login server is down then go to to see the server status.

Force Close on Connect

15800192 10207878275180668 5815595377886278181 o
This only occurs when the server is doing the credential check for your client version (registry check) and will throw this error if it does not have the necessary account access (Administrative). Most commonly it is due to the vercheck failing. Run a File Check on Final Fantasy XI in the original POL client.

Microsoft Visual C++ Redist did not install or will not install


This is what happens when you don't meet the requirements of installing these runtimes.The file log file will say that the follow file is missing: api-ms-win-crt-runtime-l1-1-0.dll. You can also see this error when running xiloader.exe without installing these files.

The fix for this is actually quite simple, mind you if you have a legit copy of windows. Little more troublesome if you don't (shhh i won't tell).

So the fix for this is quite simple and also occurs on new systems or OS' that were just freshly installed. The reason for this to happen is that the Universal C Runtimes (KB2999226) were not installed via Windows Update. It is highly recommended to run all updates that are not optional, mind you no one wants the Internet Explorer 11 update so ignore that garbage. If you got all of the updates installed then you will be able to install the Microsoft Visual C++ runtimes.

There will be times where KB2999226 will not show up under Windows Update, if this is the case then go to the Windows Update Catalog: and search for KB2999226. Download the correct one for the OS & Bit type (32/64) and run the stand alone installer.

Make sure that the prerequisites are met for the installation of this Windows Update or you will get an error saying that "This patch is not applicable to your system" error. Here is a list of the requirements for this to install on your system.


  • You must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (KB2919355) installed in Windows 8.1 or Windows Server 2012 R2.
  • Install Service Pack 1 for Windows 7 or Windows Server 2008 R2.
  • Install Service Pack 2 for Windows Vista and for Windows Server 2008.

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.