Troubleshooting

Table of Contents

• Basic Troubleshooting
• Resetting the tool/settings
• Accessing log files for issue reporting
• Anamnesis cannot find the ffxiv_dx11.exe process
• The tool asks you to install .NET despite .NET 5.0.x being installed
• Anamnesis.exe is deleted when the tool is extracted
• A 'Screenshot Failed' error appears when using Anamnesis in conjunction with a post-processing tool such as ReShade or GShade
• My issue isn't here!

Basic Troubleshooting

It is good practice to ensure you have adhered to the following basic rules while using Anamnesis. Failure to do so will result in most of, if not all issues, crashes, etc. you may encounter.

• Make sure the folder you have extracted the program to is owned by an Administrator.
• Make sure you have either turned off your Antivirus program, or at the very least made an exception for the Anamnesis executable in your Antivirus program and Windows Firewall.
• Make sure you have launched Final Fantasy XIV and logged into a character before launching Anamnesis.
• If you did not previously have .NET 5 installed on your system and have installed it for the purpose of using Anamnesis, make sure you reboot your PC after installing .NET to ensure it's installed completely.

      ^{↑ back to top}

Resetting the tool/settings

In the event that a setting has not saved correctly, the settings file has corrupted, or you simply wish to reset the tool to its default settings, press and hold the Shift button while launching the tool, and continue holding until you are presented with the message seen to the right.

* This dialogue window will be in English regardless of any language settings previously used.

      ^{↑ back to top}

Accessing log files for issue reporting

Anamnesis provides easy access to logs via the About menu, so please use those instead of taking screenshots of an error message, as images of error messages will not give the developers enough information to work with. Anamnesis will retain the last fifteen instance logs for your convenience.

You can also manually access these logs if you don't have the tool open:

1. Press the Windows key on your keyboard and enter %appdata%, then hit the Enter key- this will take you to the Roaming folder
2. Double-click on the Anamnesis folder
3. Double-click on the Logs folder

From there you can drag and drop your log files into a Github Issue text box, which will upload it for the developers to read.

No identifying information is kept in these log files- they are completely anonymous, and are only used for the express purpose of troubleshooting and issue resolution only.

      ^{↑ back to top}

Anamnesis cannot find the ffxiv_dx11.exe process

Anamnesis only supports the DX11 version of the game, as we believe Square Enix will be dropping support for the DX9 version as technology evolves. Please ensure you are running the DX11 version of the game before running Anamnesis.

If, for whatever reason, you cannot use the DX11 version of the game, then you will not be able to use Anamnesis. We apologise for this inconvenience.

Additionally, Anamnesis currently only works with the international (JP/NA/EU) client; there are plans to support the KR and CN clients, but the developers do not have access to these clients at this time, so an estimate on this feature being added cannot be given.

      ^{↑ back to top}

The tool asks you to install .NET despite .NET 5.0.x being installed

Older installations of .NET Framework/Core can occasionally interfere with newer installations, including 5.0.x (used by Anamnesis). This is caused by newer versions of .NET failing to correctly update its Host Version on installation, and not something caused or remedied by Anamnesis.

To check if this is affecting you, please follow these instructions:

1. Open a Command Prompt window by typing cmd into the search bar of the Start menu and pressing Enter
2. Type (or copy and paste) dotnet --info and press Enter
3. Scroll down until you see Host- check to see if the Version below it is 5.0.x

If the version is not correct/up to date, please note down which version it was, as you will need to uninstall it to prevent Windows from silently failing to read the correct version.

      ^{↑ back to top}

Anamnesis.exe is deleted when the tool is extracted

Occasionally your Anti-virus software will delete the executable when the archive is extracted. To circumvent this:

1. Right-click the archive and select Properties
2. Press the Unblock button at the bottom
3. Press Apply and Okay
4. Extract the archive either on top of the existing installation and overwrite the files when prompted, or extract the archive to your folder of choice.)

If this alone does not resolve the issue, then you will need to whitelist the tool and its related folders in your Anti-virus software. The method for whitelisting applications varies from program to program. Below is a list of popular antivirus programs and links to their documentation.

• Avast
• AVG
• BitDefender
• ESET NOD32
• McAfee
• Windows Defender (preferred by the developers)

The folders that will need to be whitelisted include:

• The folder you extracted the tool to
• %appdata%\Anamnesis
• Documents\Anamnesis

      ^{↑ back to top}

A 'Screenshot Failed' error appears when using Anamnesis in conjunction with a post-processing tool such as ReShade or GShade

This is due to a Windows Security feature, and usually only appears when the user is trying to take a screenshot when Anamnesis has window focus. To remedy this, try the following fixes in order until the issue is resolved:

• Click anywhere in the game window to ensure it has focus before pressing the Print Screen button
• Ensure GShade/ReShade has been added to the Windows Firewall
• Check your keybinds in-game and in GShade/ReShade to ensure they aren't conflicting
• Roll back any recent Windows Updates

If none of these options resolve the issue, then you may not be able to use Anamnesis until a workaround is found. As such, please wait for an update on our Discord. We apologise for this inconvenience.

This is a feature of Windows Security, and not a bug with either Anamnesis or your chosen post-processing injector. As this isn't an Anamnesis or program problem, developers will not be able to assist you with questions about this.

An alternative to using your set Screenshot button is to utilise the Snipping Tool, which is a stock Windows tool, and is covered in detail by Microsoft.

      ^{↑ back to top}

My issue isn't here!

If you have checked ensured that your issue is not caused by failing to adhere to the above practices, then you have likely encountered a bug that has been missed during our extensive testing phases.

If this happens, please open a ticket in the Issues tab, ensuring you have included as much detail as possible, and have attached any relevant logs. The information we require to fully act on a bug report includes:

• a brief description of the bug as the issue title
• any error messages displayed, these can be pasted directly into the body of the issue
• the exact steps you took to trigger the issue
• how many times you encountered the issue
• the log files for the session that you experienced the issue in

Requests for basic help and incomplete bug reports will be closed without comment. Please make the effort to read all documentation and complete your issue reports as robustly as possible. Anamnesis is created and maintained by volunteers in our spare time, and responding to poor bug reports or reports based on user-made errors or misuse is time-consuming. Reporting issues requires an email verified Github account.

      ^{↑ back to top}