Outlook Signature Not Saving? 8 Fixes That Actually Work

1. Permissions issue on the Signatures folder

The most common and most overlooked cause. Outlook saves your signature as a set of files in a specific Windows folder. If that folder’s write permissions got changed — after a system migration, a corporate policy push, or a Windows update — Outlook can read the existing signatures but can’t write new ones. From your perspective, it looks like the save just did nothing.

The folder is:

Paste that path into the File Explorer address bar and press Enter. Windows expands the %APPDATA% variable for you.

How to check and fix write permissions

2. Antivirus blocking file creation

Kaspersky, Norton, and Bitdefender are the three antivirus programs most commonly reported to interfere with Outlook signature saving. The reason is that the %APPDATA%\Microsoft\Signatures folder is a known target for malware that injects malicious content into email signatures. So some antivirus products apply aggressive protection to it — blocking any process that tries to write new files there, even Outlook itself.

From your perspective: you edit the signature, click save, Outlook says “OK” — but when you check the folder, no new files were created.

The fix

If you’re on a corporate laptop and can’t change antivirus settings yourself, raise a ticket with IT. They can add the exclusion from the central management console.

3. Roaming signatures conflict

Microsoft 365 has a feature called roaming signatures that syncs your Outlook signatures across devices via the cloud. In theory, great. In practice, it causes a specific and confusing problem: you edit your signature locally, save it, it looks right — and then a few minutes or hours later it reverts.

What’s happening: the cloud copy of your signature is older than your local edit, and when the sync runs, it overwrites your local version with the cloud version. Or you edit on one device, but Outlook on another device hasn’t synced yet and is still pushing the old version. See the full breakdown in the Outlook roaming signatures guide.

Option A: Disable roaming signatures

If you only use Outlook on one device, the easiest fix is to turn roaming signatures off:

Option B: Edit via Outlook on the web

If roaming is enabled by policy and you can’t disable it, edit your signature through Outlook on the web (outlook.office.com) instead. That editing session writes directly to the cloud copy, so the sync won’t overwrite it.

Go to outlook.office.com → Settings (gear icon) → View all Outlook settings → Mail → Compose and reply → Email signature. Edit and save there.

4. Cached mode vs. online mode

Outlook’s Cached Exchange Mode keeps a local copy of your mailbox so you can work offline. It also means Outlook sometimes operates against cached data rather than live server data — and occasionally this creates conflicts with signature settings, especially when roaming signatures are involved.

The symptom: signature saves fine, but when you compose a new email, Outlook still inserts the old one. Closing and reopening Outlook doesn’t fix it.

Try switching modes temporarily

If your organization requires cached mode (for performance or compliance reasons), you may not be able to turn it off permanently. But the temporary toggle often clears the stuck state and lets signatures save correctly going forward.

5. Corrupted Outlook profile

An Outlook profile is a configuration container that stores your account settings, data file locations, and preferences. Over time — especially after Office reinstalls, Windows upgrades, or repeated sync errors — profiles can become corrupted. A corrupted profile causes all kinds of strange behavior, including signatures that won’t save, won’t appear, or save correctly but don’t get inserted into new emails.

If you’ve tried everything else and nothing works, creating a new profile almost always fixes it. Your emails, calendar, and contacts are not deleted — those live in your mailbox or a .pst file, not in the profile itself.

How to create a new Outlook profile

For rebuilding the signature quickly, use the NeatStamp editor — you can build a professional-looking signature in a few minutes and it generates Outlook-compatible HTML you can paste directly.

6. Group Policy overriding personal settings

In corporate environments, Windows Group Policy can control almost every aspect of how Outlook behaves — including whether users can create, edit, or save personal signatures. If Group Policy is locking down signatures, you can’t fix this yourself. You need to talk to IT.

Common policies that cause this:

• •"Prevent users from creating personal signatures" — disables the New/Edit buttons in signature settings
• •"Do not allow users to change signature settings" — makes the entire Signatures dialog read-only
• •Policies that enforce a company-wide signature template via Exchange transport rules — these add a signature at the server level and may conflict with personal ones
• •Policies that lock the %APPDATA%\Microsoft\Signatures folder permissions

How to check if Group Policy is the cause

Open the signature editor in Outlook. If the New, Edit, and Delete buttons are greyed out, Group Policy is restricting access. Another tell: go to File → Options → Mail — if the Signatures button is missing entirely, a policy has removed it.

Your IT team can check the relevant GPO under User Configuration → Administrative Templates → Microsoft Outlook → Outlook Options → Mail Format → Internet Formatting. Ask them specifically whether the “Signature” policies are configured and whether personal signatures can be allowed alongside company templates.

7. Registry key issues

When Outlook saves a signature assignment — which signature to insert into new emails, which to use for replies — it stores those settings in the Windows Registry. If those registry values are missing, corrupted, or point to a signature name that no longer exists, Outlook behaves unpredictably: it may show no signature, revert to a previous one, or claim to save while actually doing nothing.

The key to check

Inside this key, look for two string values:

• NewSignature

  The name of the signature to insert into new emails. Should match the exact filename of your .htm signature file in the Signatures folder (without the .htm extension).

• ReplySignature

  The name of the signature to insert into replies and forwards. Same format as above.

How to fix it

If you’re not comfortable editing the registry, ask IT — this is a standard Outlook fix they should know. Alternatively, if you use an Outlook signature manager, the registry handling is done for you automatically.

8. New Outlook bug — signature saves but doesn’t appear

This one is particularly maddening because everything looks correct. You go into settings, you see your signature, it’s assigned to new messages — but when you open a new compose window, the signature isn’t there. Microsoft acknowledged this bug in the new Outlook (the web-based version that started rolling out as the default in late 2024).

The new Outlook is fundamentally different from classic Outlook — it’s essentially a wrapper around Outlook on the web, and it stores signatures in Microsoft 365 cloud settings rather than local files. This architecture introduces new failure modes that didn’t exist in classic Outlook.

Workarounds while Microsoft patches it

If you’re on Microsoft 365 and signatures keep disappearing across sessions, also check the Outlook signature disappeared guide and the email signature not showing in Outlook article, which cover additional cloud-specific causes.

Troubleshooting flowchart

Not sure where to start? Walk through this decision tree. Each branch points you to the right section above.

The nuclear option: completely reset signatures

When nothing else works, a full reset of the Signatures folder clears whatever corrupted state is causing the problem. This wipes all your saved signatures — so back them up first. Here’s the exact process:

If the problem returns after doing this, the cause is external — antivirus, Group Policy, roaming sync, or a corrupted Outlook profile. Go back to the relevant section above and fix that first before rebuilding.

How NeatStamp prevents this problem entirely

Every fix in this guide addresses a symptom of the same underlying issue: Outlook’s signature system stores everything locally on your machine, making it vulnerable to permissions issues, antivirus interference, sync conflicts, profile corruption, and Group Policy.

NeatStamp takes a different approach. Your signature is stored in the cloud and accessible from any browser. When you need to use it, you click one button and copy it — then paste it into Outlook’s signature editor or directly into a compose window. No save issues, no sync conflicts, no file permissions.

You can set up your signature in the NeatStamp editor in a few minutes. Pick from the signature templates, add your details, and you’re done. The editor generates HTML that works in Outlook 365, classic Outlook, and everywhere else. Check the pricing page — there’s a free plan that covers most individual use cases.

If your team is dealing with this problem across multiple people, the NeatStamp for teams plan lets you manage everyone’s signatures centrally — updates everyone at once, no IT involvement needed.

Related guides

Frequently asked questions