In different versions of Outlook (2019/2016/2013/Microsoft 365 Apps), a bug occurs periodically when the create signature button stops working. When the user clicks the Signature button in the Outlook settings, the signature creation dialog doesn’t appear, or Outlook hangs/closes. The problem most commonly occurs on OEM computers with pre-installed Office or on computers that previously had a previous version of Outlook installed.

This time the bug appeared on Windows 10 with the newly installed RTM version of Outlook 2019 with all the latest updates. After clicking the Signatures button in the File -> Options -> Mail, nothing happened and the signature didn’t appear.

I’ve tried to repair, reinstall, or completely remove MS Office with registry cleanup, but nothing helped. How to set a user Outlook signature in this case?

Uninstalling the Built-in UWP Microsoft Office Desktop App

There is a description of a similar bug in Windows 10 and 11 on support.office.com. To solve the problem of the Signatures button that is not working, it is recommended to remove the UWP app Microsoft Office Desktop App (Settings -> Apps -> Apps & Features).

The modern Microsoft Office Desktop App must be uninstalled for all user accounts on a computer. To uninstall a built-in UWP/APPX app on Windows, you can use the PowerShell command:

Get-AppxProvisionedPackage -online | %{if ($_.packagename -match "Microsoft.Office.Desktop") {$_ | Remove-AppxProvisionedPackage -AllUsers}}

Repairing Outlook Signature Button via Registry

I have found some opinions on technical forums that the signature issue often occurs after mailbox migration to another domain or on computers with the pre-installed Office. In order to make the Signatures button work, try manually modifying the registry:

You need the values of the Default and LocalServer32 registry parameters under the following registry keys (for x64 and x86 versions of Office, respectively)

• HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{0006F03A-0000-0000-C000-000000000046}\LocalServer32
• HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{0006F03A-0000-0000-C000-000000000046}\LocalServer32

The values for the Default and LocalServer32 parameters must point to the full path to the outlook.exe executable on your computer.

You can quickly find the location of the outlook.exe file on your computer with the commands:

cd /
dir OUTLOOK.EXE /s /p

For example, for Outlook 2016 it is C:\Program Files (x86)\Microsoft Office\Office16\Outlook.exe.

Use the following path format:

"C:\\Program Files (x86)\\Microsoft Office\\Office16\\outlook.exe"

You can make changes to the registry using a REG file. Create a text file with the *.reg extension on your computer with the following content (for Outlook 365, 2019, and 2016):

Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Outlook.Application]
@="Microsoft Outlook 16.0 Object Library"
[HKEY_CLASSES_ROOT\Outlook.Application\CLSID]
@="{0006F03A-0000-0000-C000-000000000046}"
[HKEY_CLASSES_ROOT\Outlook.Application\CurVer]
@="Outlook.Application.16"
[HKEY_CLASSES_ROOT\Outlook.Application.16]
@="Microsoft Outlook 16.0 Object Library"
[HKEY_CLASSES_ROOT\Outlook.Application.16\CLSID]
@="{0006F03A-0000-0000-C000-000000000046}"
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{0006F03A-0000-0000-C000-000000000046}]
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{0006F03A-0000-0000-C000-000000000046}\InprocServer32]
"Assembly"="Microsoft.Office.Interop.Outlook, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71E9BCE111E9429C"
"Class"="Microsoft.Office.Interop.Outlook.ApplicationClass"
"RuntimeVersion"="v2.0.50727"
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{0006F03A-0000-0000-C000-000000000046}\InprocServer32\16.0.0.0]
"Assembly"="Microsoft.Office.Interop.Outlook, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71E9BCE111E9429C"
"Class"="Microsoft.Office.Interop.Outlook.ApplicationClass"
"RuntimeVersion"="v2.0.50727"
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{0006F03A-0000-0000-C000-000000000046}\LocalServer32]
@="C:\\Program Files\\Microsoft Office\\Office16\\OUTLOOK.EXE"
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{0006F03A-0000-0000-C000-000000000046}\ProgID]
@="Outlook.Application.16"
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{0006F03A-0000-0000-C000-000000000046}\Typelib]
@="{00062FFF-0000-0000-C000-000000000046}"

Import this REG file into the registry by double-clicking on it.

After that, the signature in Outlook should work.

Adding Outlook Signature Files via Registry

In one of the previous articles, we talked about how to automatically generate a signature in Outlook based on user data from Active Directory. There we mentioned that in Windows 11, 10, 8.1, and 7 Outlook signatures files are located in the user profile folder %APPDATA%\Microsoft\Signatures (C:\Users\username\AppData\Roaming\Microsoft\Signatures).

As a workaround, you can generate an HTML/RTF/TXT file with the signature text and copy it to the specified directory. Then when creating a new email in Outlook or replying to a message, you can insert your signature using the corresponding button from the Outlook interface (Outlook needs to be restarted). You can create signature files on any other computer and copy signature files to the %APPDATA%\Microsoft\Signatures directory on the affected computer.

Then, use the registry to specify paths to new HTML/RTF/TXT files with Outlook (in this example, we set the signature file my_sign file for Outlook 365, 2019, or 2016). Use the following PowerShell commands to make changes to the registry:

Remove-ItemProperty -Path HKCU:\Software\Microsoft\Office\16.0\Outlook\Setup -Name First-Run -Force -ErrorAction SilentlyContinue -Verbose
New-ItemProperty HKCU:'\Software\Microsoft\Office\16.0\Common\MailSettings' -Name 'ReplySignature' -Value my_sign -PropertyType 'String' -Force
New-ItemProperty HKCU:'\Software\Microsoft\Office\16.0\Common\MailSettings' -Name 'NewSignature' -Value my_sign -PropertyType 'String' –Force

However, this fix is rather inconvenient, because the user needs to manually press the button each time to insert the signature.