Fixing missing Outlook signatures after an Office update

If your Outlook signatures vanished after an Office update, usually the files still exist and only the active client or default selection changed. Confirm which Outlook client you run, check the signature folders for .htm/.rtf/.txt and the image subfolders, reassign defaults in Outlook’s Mail > Signatures, and run the supplied PowerShell dry-run to verify or restore files safely.

Symptom: what you see and when this happens

You lose signatures in new messages or replies, or signatures show but images are broken. This can happen after an Office or Windows update, switching between New Outlook and Classic, or a profile/container mount failure such as FSLogix or OneDrive problems.

• You open Outlook and new messages or replies no longer include your signature.

• File > Options > Mail > Signatures shows no signatures or empty entries while you remember them before the update.

• Signatures appear in the UI but images are broken, or signatures appear on one machine but not another using the same account.

Before you start (applicability, permissions, safe checks)

Start by confirming applicability and getting the right permissions. These steps apply to Outlook on Windows desktop (both Classic and New Outlook) and Outlook for the web; they do not apply to mobile Outlook apps. You need access to your Windows user profile folders. Administrator rights are usually not needed to copy files into %APPDATA%\Microsoft\Signatures, but check with IT if your environment restricts writes.

• Close Outlook before copying signature files.

• Confirm whether your profile uses roaming storage (OneDrive, FSLogix, network redirection) before overwriting local files.

1. Open File Explorer and run:

%APPDATA%\Microsoft\Signatures

2. If the folder exists, copy it to a safe backup location (for example C:\Users\you\Desktop\Signatures-backup).

Quick triage checklist (get signatures back in 5 minutes)

Follow these low-risk checks first. They restore signatures in many cases and avoid unnecessary changes.

1. Confirm which Outlook client is running.

• Classic desktop Outlook shows a ribbon and the About Outlook version string under File > Office Account. New Outlook often labels itself "New Outlook" in the title bar and uses a single-window modern UI.

2. Open File > Options > Mail > Signatures and check for signature names.

3. If signatures are listed, reassign defaults for New messages and Replies/forwards, click OK, then restart Outlook.

4. If no signatures are listed, check the local signature folder:

%APPDATA%\Microsoft\Signatures

5. If files exist in that folder, close Outlook, copy the files to the destination folder if they aren’t already there, then reopen Outlook and reassign defaults.

6. If your profile uses OneDrive or FSLogix, confirm the service is signed in and fully synced or that the FSLogix container mounted. If sync or mount failed, resolve that first or escalate to IT.

Which Outlook build you have and why it matters

Identify the active Outlook client before restoring files. The Classic desktop client reads local signature files, while some New Outlook builds use a different store or cloud-synced settings. If you restore Classic files but the user runs New Outlook, the restored files won’t appear until Classic runs or New Outlook reads local files again.

1. How to detect which Outlook you’re running:

• Classic desktop Outlook: open File > Office Account > About Outlook to see a version string. The composer is multi-window and the Options dialog lives under File.

• New Outlook: the app may say "New Outlook" in the title bar, has a single-window UI, and may be delivered via the Microsoft Store.

• Outlook for the web: signatures live in mailbox settings and are not affected by local files.

2. Why this matters:

• Classic desktop Outlook reads and writes signature files from %APPDATA%\Microsoft\Signatures.

• Some New Outlook builds either use a different internal store or cloud-synced settings, so copying files into the classic signature folder might not restore signatures if New Outlook ignores local files.

Stop condition: Do not edit registry keys, delete roaming containers, or overwrite signature folders until you know which client is active and you have a backup of the existing signature folder.

Restore from disk and common storage locations to check

If signatures are on disk, you can restore them safely. Look in local paths, OneDrive, FSLogix-mapped profiles, or backups first. Signature files come as .htm, .rtf, .txt plus a same-named image subfolder.

Where to look first (desktop Outlook):

• Primary local path:

%APPDATA%\Microsoft\Signatures

• Signature files appear as a set sharing the same base name with extensions .htm, .rtf, .txt and a same-named subfolder that contains images (.png, .jpg, .gif).

• Per-profile: check each Windows user profile if multiple profiles exist.

• OneDrive: check OneDrive\Microsoft\Signatures or search OneDrive for .htm files with your signature name.

• FSLogix: signatures should appear at %APPDATA%\Microsoft\Signatures when the FSLogix container is mounted. If the container failed to mount the user will see an empty local folder; the real files remain in the profile store.

Manual restore steps (safe, reversible):

1. Close Outlook.

2. Locate the source signature files (backup, OneDrive sync folder, FSLogix-mounted profile). Confirm the set: .htm, .rtf, .txt and the image subfolder with matching base name.

3. Back up the existing destination folder if present.

robocopy "%APPDATA%\Microsoft\Signatures" "C:\Users\you\Desktop\Signatures-backup" /E

4. Copy the entire signature set into the destination folder.

%APPDATA%\Microsoft\Signatures

5. Start Outlook and open File > Options > Mail > Signatures. Reassign defaults for New messages and Replies/forwards.

What to do if images are missing or broken:

• If the .htm file references images by absolute cloud URLs, open the .htm in a text editor and change image references to the local image filenames, then ensure the images live in the signature subfolder.

If you can’t find any signature files on disk:

1. Search backups (Windows File History, Shadow Copies, company backup, OneDrive online, FSLogix profile store).

2. If nothing exists, recreate the signature or restore from a company-managed backup. Gather the evidence listed in Escalation before recreating so IT can attempt a restore if needed.

Automated recovery: PowerShell export/import (dry-run first)

Run a dry-run to confirm what files would copy before making changes. The script lists .htm signatures in a source folder and shows the files it would copy into the local signature folder. It copies only when you run it with -PerformAction.

1. Save the script to Restore-OutlookSignatures.ps1.

param(
  [string]$SourcePath = "$env:USERPROFILE\OneDrive\Microsoft\Signatures",
  [string]$DestPath = "$env:APPDATA\Microsoft\Signatures",
  [switch]$PerformAction = $false
)

if (-not (Test-Path $SourcePath)) {
  Write-Output "Source path not found: $SourcePath"
  exit 1
}

$signatures = Get-ChildItem -Path $SourcePath -Filter *.htm -File -ErrorAction SilentlyContinue
if (-not $signatures) {
  Write-Output "No .htm signature files found in source."
}
else {
  foreach ($sig in $signatures) {
    $base = [IO.Path]::GetFileNameWithoutExtension($sig.Name)
    $files = Get-ChildItem -Path $SourcePath -Filter "${base}.*" -File -ErrorAction SilentlyContinue
    Write-Output "Found signature: $base"
    foreach ($f in $files) { Write-Output "  -> $($f.Name)" }
    $imgDir = Join-Path $SourcePath $base
    if (Test-Path $imgDir) {
      Write-Output "  -> images folder: $imgDir"
      Get-ChildItem -Path $imgDir -File | ForEach-Object { Write-Output "     - $($_.Name)" }
    }

    Write-Output "Would copy files to: $DestPath"

    if ($PerformAction) {
      if (-not (Test-Path $DestPath)) { New-Item -ItemType Directory -Path $DestPath | Out-Null }
      foreach ($f in $files) { Copy-Item -Path $f.FullName -Destination (Join-Path $DestPath $f.Name) -Force }
      if (Test-Path $imgDir) { Copy-Item -Path $imgDir -Destination (Join-Path $DestPath $base) -Recurse -Force }
      Write-Output "Copied $base to $DestPath"
    }
  }
}

Write-Output "Dry-run complete. Rerun with -PerformAction to perform the copy."

2. Run a dry-run pointing -SourcePath at your backup or OneDrive folder.

.\Restore-OutlookSignatures.ps1 -SourcePath "C:\Users\you\OneDrive\Microsoft\Signatures" -PerformAction:$false

3. If output lists the expected signature sets, run with -PerformAction $true to copy them to %APPDATA%\Microsoft\Signatures.

After copying, open Outlook and set defaults in File > Options > Mail > Signatures.

Verify success, managed-environment checks and when to escalate

Verify the fix by creating messages and checking images. If problems remain, gather logs and environment details before you escalate to IT or Microsoft support.

1. Create a new mail message and confirm the signature inserts automatically for New messages.

2. Reply to an email and confirm the reply/forward signature inserts.

3. If the signature contains images, send a test to an external address or view the sent item and confirm images display.

Managed-environment checks to run before escalating:

• Group Policy / Intune: ask IT whether a signature policy or device configuration was deployed during the update window.

• OneDrive: confirm OneDrive is signed in and shows no sync errors. Look for files with cloud-only icons or sync warning badges.

• FSLogix: confirm the container mounted correctly and check FSLogix event logs for mount failures.

• Registry/policy defaults: if UI entries exist but defaults are reset, reassign in Outlook first. Only change registry keys with IT approval and exact values.

What to collect before escalating to IT or Microsoft support:

• Screenshot of File > Options > Mail > Signatures showing the problem.

• Directory listing of %APPDATA%\Microsoft\Signatures or the output from the PowerShell dry-run.

• OneDrive client status or FSLogix event logs showing sync/mount errors.

• Exact Outlook build string from Help > About Outlook and whether the user is running New Outlook or Classic.

When to escalate:

• You cannot find signature files in any backup or roaming store and need recovery beyond re-creation.

• FSLogix containers fail to mount or OneDrive shows permanent sync errors after basic troubleshooting.

• A registry or policy change appears to be forcing empty signatures across multiple users.

• An Office update changed the default Outlook binary (for example New Outlook replaced Classic) and this affects many users; IT should raise a ticket with Microsoft if necessary.

Conclusion

If the quick checks show files on disk, run the PowerShell dry-run to confirm and then copy the files into `%APPDATA%\Microsoft\Signatures` before reassigning defaults in Outlook. If files are missing and you use FSLogix or OneDrive, collect sync and mount logs and escalate to your IT profile or storage team rather than recreating signatures immediately.