Many users have a problem with Outlook missing misspelled words. In many cases this happens because the person is typing in the signature field, either accidentally or intentionally.

Outlook uses the Email Signature style for the signature and the signature style is marked Do not spell check. While this is a good setting for signatures, it's a problem when users type in the signature area. This happens when users set up their signature to insert a block of text, such as a salutation or introductory text at the beginning of the message, or when a user accidentally types in the signature area. Either way, you'll know this is the problem when you right click on a misspelled word and see the signature menu instead.

If you are using signatures to add introductory text and your signature, with the message in between, you should use AutoCorrect or Quick Parts instead. It’s easy to insert test using either method and you don't risk losing the message if the signature or account is changed.

Avoid Accidentally Typing in the Signature Area

Rather than editing the signature style to allow spell checking, you should avoid typing in the signature field, especially if you use multiple signatures or accounts with separate signatures. When you change the account or signature, your message will be replaced by the new signature and the message you composed is lost forever.

The best way to avoid accidentally typing in the signature area is to clearly mark where it begins. We recommend adding two dashes and a space ("-- ") as the very first line of your signature. For more information, see Outlook signatures and spell check.

Why two dashes? They are defined in an RFC as the universal signature identifier and many mail clients use this to identify and hide the signature in their reading pane or delete it when replying.

Begin typing your message above the dashes.

Tip: Create a blank signature that contains just the two dashes and assign it to accounts where no signature is desired. Then if you change accounts, the signature will change too.

Workaround: Change the Message's Spell Check Setting

When you discover you typed in the signature area, the easiest fix is to change the spell check settings on the message. To do this you need to select the entire message then go to the Spelling dropdown and choose Language. Clear the Do not spell check box. Back out of the dialog and press F7 to initiate the spell check.

For those times you accidentally type in the signature field and discover it at the end, you can easily change the spell check setting.

1. Select the entire message
2. In Outlook 2010 and newer: Review ribbon > Language menu > Set Proofing language command
3. Outlook 2007: Expand the Spelling button, choose Set Language.
4. Clear the Do not spell check box.
   

Now the whole message can be spell checked.

Use a macro to enable spelling

If need to change the spell check setting often, you can use a macro.

This macro will select the entire message and enable proofing for you. You'll need to set a reference to Word object library to use it. If you don't know how to use a macro, see How to use Outlook's VBA Editor.

Add the macro to a button on the ribbon and click it when you need to enable spell check on a message where you typed in the signature field.

Public Sub SpellCheckSigs()
 Dim objItem As Object
 Dim objInsp As Outlook.Inspector
 
 ' Add reference to Word library
 ' in VBA Editor, Tools, References
 Dim objWord As Word.Application
 Dim objDoc As Word.Document
 Dim objSel As Word.Selection
 On Error Resume Next

 Set objItem = Application.ActiveInspector.CurrentItem
 If Not objItem Is Nothing Then
   If objItem.Class = olMail Then
    Set objInsp = objItem.GetInspector
    If objInsp.EditorType = olEditorWord Then
        Set objDoc = objInsp.WordEditor
        Set objWord = objDoc.Application
        Set objSel = objWord.Selection
        
    With objSel
      .WholeStory
      .NoProofing = False
    End With

    End If
   End If
 End If
 
 Set objItem = Nothing
 Set objWord = Nothing
 Set objSel = Nothing
 Set objInsp = Nothing
End Sub

Problem: Using Signatures to Insert Headers

An Outlook user had this complaint:

"My signature block includes a salutation and signature information beneath it. Therefore, any text I type between the salutation and the signature is in the signature block. However, I can't get Outlook to spell check the signature block. Is there a way to do this?"

Don't use signatures to insert headers. (The feature is called signature, not header and signature for a reason.)

Use Quick parts for the header portion or create stationery with the header block in it.

Solution: Use Autocorrect and Quick Parts (Autotext)

Rather than using signatures to insert blocks of text, use autocorrect or autotext to insert text. When you type the keyword, the keyword is replaced by the full text.

Autocorrect is the feature which converts :) to a smiley face. Autocorrect entries can contain up to 256 characters and are assigned a keyword. When you type the keyword it's replaced by the autocomplete text.  This makes autocorrect an excellent choice for replacing short phrases.

Set up autocorrect entries through Tools, Options, Spelling, Spelling and Autocorrection, Autocorrect options. Assign a unique keyword that is easy to type to insert the text. I use leading characters, such as # or /, with my keywords, such as #sal (for salutation)

For longer blocks of text, use Quick Parts. This feature is similar to Autotext in older versions. After setting up the entries, you'll need to either pick the entry from the menu or type the beginning of it (enough to form a unique phrase) then press F3.

Other Causes

If the problem is not that you are typing in the signature field, there are a few things left to check.

Proofing Tools Override key

One common cause (when you aren't typing in the signature field) is an errant registry key.

Check this registry entry:

HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\ProofingTools\1.0\Override\en-US

If it exists, delete or rename it; if it doesn't exist, create it.

You can also delete the following key, but if you do, you'll need to reconfigure your spelling options. (Export it before deleting it.)

HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\ProofingTools\1.0\Office\OutlookSpellingOptions

Yes, that makes no sense at all (and I'm not sure why the key is created to begin with), but many users report removing it fixes their problem and others say if it doesn't exist then creating it fixes the problem. Go Figure.

Is the Style Marked to Skip Spell Check?

While this is mentioned in the "Workaround: Change the message's spell check settings" section above, it's worth reminding users who aren't typing in the signature block to check the style and verify it is set for spell check, especially when only some themes, messages, or stationery is affected.

1. Select the entire message
2. Outlook 2010: Review ribbon > Language menu > Set Proofing language command
3. Outlook 2007: Expand the Spelling button, choose Set Language.
4. Clear the Do not spell check box.

In Outlook 2007, the Set Language command is found under the Spelling button:

Now the whole message can be spell checked.
 

Mixed versions of Word and Outlook

When you use mixed versions of Outlook and Word, 'spell check on send' should always work (if enabled).

For the spell check as you type and grammar checking features, you need to have the same version of Word and Outlook, often installed from the same suite. If you don't have Outlook and Word installed from the same suite or are using mixed version, copy winword.exe into the same directory as outlook.exe This enables spell check as you type and grammar features.

The version of winword.exe doesn't make a difference, and it doesn't even have to be winword.exe; you can use almost any file and rename it winword.exe. (I have not had any luck with renamed text files, but renaming exe and dll files to winword.exe worked.)

Make sure you copy, not move, winword.exe!

Where can you find the Outlook and Word exes? It depends on your version.

Beginning with Office 2013, most people will have the Office suite under C:\Program Files (x86)\Microsoft Office\root\ (64-bit Windows and 32-bit Office) or C:\Program Files\Microsoft Office\root\ (both Windows and Office are 64-bit). Each installation will be in a subfolder called "OfficeXX", where XX is the version number.

Volume licensing's MSI installation and older versions of Office are found at C:\Program Files\Microsoft Office, or if using 64-bit Windows, at C:\Program Files (x86)\Microsoft Office.

Check Contextual Spelling Settings

This solution comes from Wendy:

I wanted to pass along that I am using Outlook 2010 with Office 2007. I could hit the F7 key and it would say it had checked the spelling and nothing was checked.

Solution:
I finally found that I had to go into File / Options / Mail / [Spelling and AutoCorrect] / Proofing / {Uncheck “Use contextual spelling”].

That fixed it for me. I don’t know how that got checked.

Contextual spelling is enabled by default if your computer has sufficient ram (more than 1 GB). It's part of the process that checks to see if words are used in context. It underlines the misused words in this sentence in blue: "I went their too pick up you're kids."

It may be related to using mixed versions of Office and Outlook. Spelling and grammar require both Outlook and Word to be from the same suite for best results.

How to use the macros on this page

First: You need to have macro security set to the lowest setting, Enable all macros during testing. The macros will not work with the top two options that disable all macros or unsigned macros. You could choose the option Notification for all macros, then accept it each time you restart Outlook, however, because it's somewhat hard to sneak macros into Outlook (unlike in Word and Excel), allowing all macros is safe, especially during the testing phase. You can sign the macro when it is finished and change the macro security to notify.

To check your macro security in Outlook 2010 and newer, go to File, Options, Trust Center and open Trust Center Settings, and change the Macro Settings. In Outlook 2007 and older, look at Tools, Macro Security.

After you test the macro and see that it works, you can either leave macro security set to low or sign the macro.

Macros that run when Outlook starts or automatically need to be in ThisOutlookSession, all other macros should be put in a module, but most will also work if placed in ThisOutlookSession. (It's generally recommended to keep only the automatic macros in ThisOutlookSession and use modules for all other macros.) The instructions are below.

The macros on this page should be placed in a module.

Open the VBA Editor by pressing Alt+F11 on your keyboard.

To put the code in a module:

1. Right click on Project1 and choose Insert > Module
2. Copy and paste the macro into the new module.

Set a reference to other Object Libraries
If you receive a "User-defined type not defined" error, you need to set a reference to another object library.

1. Go to Tools, References menu.
2. Locate the object library in the list and add a check mark to it. (Word and Excel object libraries version numbers will match Outlook's version number.)
   

Commonly used libraries are Microsoft Word, Microsoft Excel, Microsoft Forms, and VBScript Regular Expression.

More information as well as screenshots are at How to use the VBA Editor