Troubleshooting


Verifika crashes after installation

Install all required updates for .NET Framework 4 on the Control Panel. Verifika™ requires Microsoft .NET Framework 4 on your computer.

The software crashes when opening the context viewer

Please update your .NET 4.0 to the latest version. Click here to update.

Actions with bilingual files in other applications fail

E.g. you cannot convert TTX files back to MIF files etc.

Please make sure these files are not included in a project currently open in Verifika. As it locks project files, you won’t be able to edit them or perform some other actions on them. If this is the case, close the project in Verifika and repeat your action with the files.

I have installed Verifika, but it does not start

If you had previous versions of Verifika installed, the new version may sometimes install incorrectly. Please delete Verifika you currently have installed (either via provided Uninstall or via Windows Control Panel) and re-install it.

I upgraded to a permanent license, but I can’t enter the new key

You need to remove the license code info.
For Verifika 2.1.3 or earlier:

  1. Press WIN + R.
  2. Type in REGEDIT and press Enter.
  3. Delete “Verifika” following exactly this path HKEY_CURRENT_USER\Software\Palex\Verifika
  4. Delete all files following this path C:\Users\<Your User Name>\AppData\Local\verifika

For Verifika 2.5. or later:

  1. Press WIN + R.
  2. Type in REGEDIT and press Enter.
  3. Delete “Verifika” following exactly this path HKEY_CURRENT_USER\Software\Palex\Verifika

I purchased an LSP license, but cannot work with all languages

Most probably you are referring to spell-checking. Hunspell engine currently supports 112 languages. You can also download and enable any Hunspell dictionaries for any language that you can find on the Internet. Check Tips and Tricks for the procedure.

If you use MS Word spell-checking engine, please make sure you have installed Miscrosoft Office Proofing Tools for the language in question.

Verifika closes unexpectedly

The only known case when it does at the moment is when you start a process monitor (this fact is known for Procmon 3.3.0.0 from Sysinternals, but may happen with other similar applications) when working in Verifika. If a process monitor is running and you try to start Verifika, a message will pop up to let you know it is impossible. However, if you start a process monitor when Verifika is already running, Verifika closes without notifications.