Knowledge Base

Client Application in CodeTwo Email Signatures for Email Clients crashes

This article is meant for users of CodeTwo Email Signatures for Email Clients. This software has been discontinued. If your organization uses Office 365, check out CodeTwo Email Signatures for Office 365.


The CodeTwo Email Signatures for Email Clients' Client Application crashes or the following entries appear in your logs:

01:49:31: Root element is missing. (C:\Users....\user.config)


01:51:24: Configuration system failed to initialize


If the issue persists the user.config file is needed to be checked. By default the file is located over there:

C:\Users\<current user name>\AppData\Local\CodeTwo\EmailSignatures.Client.*<the newest one>\<version number>\user.config

The example of a full path:


The file should contain the content you can see in Fig. 1.:

Fig. 1. The user's config file of the Client Application.

If there is no content like that, please disable your Client Application (you can kill the process or just right click on the application icon in the system tray)  and then remove all the folders whose names start with EmailSignatures.Client.ex - see the Fig. 2.:

Fig. 2. Removing the folder which contains the config file.

You can also do that by typing below cmdlets in your ps PowerShell:

# This script:
# 1. Stops the Email Signatures Client App process
# 2. Removes Email Signatures Client App folders from:
# C:\Users\<name of the current user>\AppData\Local\CodeTwo\EmailSignatures.Client.*<rest of characters>

Stop-Process -ProcessName EmailSignatures.Client; $userName = [Environment]::UserName;$FaultyFilesLocation = "C:\Users\$userName\AppData\Local\CodeTwo";Remove-Item $FaultyFilesLocation\EmailSignatures.Client.*;

Last but not least, please ensure that the files located under the following directories have appropriate permissions assigned and are not read-only:

%ProgramData%\CodeTwo Email Signatures
%AppData%\CodeTwo Email Signatures

After you start the Client Application again, the file will be created anew and everything should be working now.

Was this information useful?