Windows OS Hub
  • Windows Server
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Active Directory Domain Services (AD DS)
    • Group Policies
  • Windows Clients
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows XP
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
    • KVM
  • PowerShell
  • Exchange
  • Cloud
    • Azure
    • Microsoft 365
    • Office 365
  • Linux
    • CentOS
    • RHEL
    • Ubuntu
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Active Directory Domain Services (AD DS)
    • Group Policies
  • Windows Clients
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows XP
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
    • KVM
  • PowerShell
  • Exchange
  • Cloud
    • Azure
    • Microsoft 365
    • Office 365
  • Linux
    • CentOS
    • RHEL
    • Ubuntu

 Windows OS Hub / Outlook / Fix: Signature Button Not Working in Outlook 2019/2016/365

October 10, 2022 MS OfficeOutlookWindows 10Windows 11

Fix: Signature Button Not Working in Outlook 2019/2016/365

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?

Signature option does not open in outlook 2016

Contents:
  • Uninstalling the Built-in UWP Microsoft Office Desktop App
  • Repairing Outlook Signature Button via Registry
  • Adding Outlook Signature Files via Registry

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).

remove Microsoft Office Desktop App

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}}

You can also use the Get-Package and Uninstall-Package cmdlets to uninstall any program on Windows using PowerShell (win32, uwp, or msi).

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.

LocalServer32 - fix outlook signature button not opened

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.

find outlook.exe executable full path on windows

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.

If a signature problem occurs in Office 2010, replace 16 with 14; if in Outlook 2013, replace 16 with 15.

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).

create signature files for outlook

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.

inssert signature in outlook 2016 manually

What else can be checked?

  • Check that NTFS compression is disabled on the %APPDATA%\Microsoft\Signatures directory (disable the Compress contents to save disk space option in the properties of this folder); disable signature folder ntfs compression with file explorer
  • If the Signature button is inactive (grayed out) in the Outlook interface, make sure that your system administrator has not enabled the policy Do not allow signatures for e-mail messages under the following GPO section Microsoft Outlook 2016 -> Outlook Options -> Mail Format (this policy is available after installing ADMX GPO Templates for MS Office); enable signature in outlook via gpo
  • Run the registry editor, use the search (CTRL + F) to find all branches whose names begin with 0006F03A-0000-0000-C000-000000000046, and delete them. Then restart your computer and check if the signature works in Outlook cleanup outlook profile in registry.

 

25 comments
7
Facebook Twitter Google + Pinterest
previous post
How to Send a Message to Teams Channel with PowerShell?
next post
Configuring Windows Firewall Rules Using Group Policy

Related Reading

Configuring Event Viewer Log Size on Windows

May 24, 2023

How to Detect Who Changed the File/Folder NTFS...

May 24, 2023

Enable Single Sign-On (SSO) Authentication on RDS Windows...

May 23, 2023

How to Create, Change, and Remove Local Users...

May 17, 2023

Fix: BSOD Error 0x0000007B (INACCESSABLE_BOOT_DEVICE) on Windows

May 16, 2023

Categories

  • Active Directory
  • Group Policies
  • Exchange Server
  • Microsoft 365
  • Azure
  • Windows 11
  • Windows 10
  • Windows Server 2022
  • Windows Server 2019
  • Windows Server 2016
  • PowerShell
  • VMWare
  • Hyper-V
  • Linux
  • MS Office

Recent Posts

  • Configuring Event Viewer Log Size on Windows

    May 24, 2023
  • How to Detect Who Changed the File/Folder NTFS Permissions on Windows?

    May 24, 2023
  • Enable Single Sign-On (SSO) Authentication on RDS Windows Server

    May 23, 2023
  • Allow Non-admin Users RDP Access to Windows Server

    May 22, 2023
  • How to Create, Change, and Remove Local Users or Groups with PowerShell?

    May 17, 2023
  • Fix: BSOD Error 0x0000007B (INACCESSABLE_BOOT_DEVICE) on Windows

    May 16, 2023
  • View Success and Failed Local Logon Attempts on Windows

    May 2, 2023
  • Fix: “Something Went Wrong” Error When Installing Teams

    May 2, 2023
  • Querying Windows Event Logs with PowerShell

    May 2, 2023
  • Configure Windows LAPS (Local Administrator Passwords Solution) in AD

    April 25, 2023

Follow us

  • Facebook
  • Twitter
  • RSS
Popular Posts
  • Outlook Keeps Asking for Password on Windows
  • Configuring KMS License Server for Office 2021/2019/2016 Volume Activation
  • Send Outlook Emails Using Excel VBA Macro or PowerShell
  • How to Completely Uninstall Previous Versions of Office with Removal Scripts?
  • How to Extend Office 2021/2019/2016 & Office 365 Trial Period?
  • Installing an Open Source KMS Server (Vlmcsd) on Linux
  • Blank Sign-in Screen in Office 365 Apps (Outlook, Teams, etc.)
Footer Logo

@2014 - 2023 - Windows OS Hub. All about operating systems for sysadmins


Back To Top