Why Is Spell Check Not Working in Word? Common Causes and Fixes

Spell check is one of those features you only notice when it stops working. One day your typos are underlined in red, the next day Word goes completely silent — no squiggly lines, no corrections, nothing. Before assuming something is seriously broken, it helps to understand what's actually happening under the hood and why spell check fails in some situations but not others.

How Spell Check Works in Microsoft Word

Word's spell check isn't a single switch — it's a layered system. At its core, Word compares your typed text against a language dictionary assigned to your document. It also runs a background process called automatic spell checking, which scans text as you type and flags errors in real time.

Several components have to work together for this to function:

  • The proofing language assigned to your text
  • The automatic spelling setting being enabled
  • The document's editing restrictions (some protected documents block proofing)
  • The Office installation's proofing tools being properly installed

If any one of these breaks down, spell check can go silent — even if everything looks fine on the surface.

The Most Common Reasons Spell Check Stops Working

1. Spell Check Has Been Turned Off

This sounds obvious, but it's the most frequent culprit. Word has a setting called "Check spelling as you type" buried inside the proofing options. If this gets toggled off — accidentally or by a macro, template, or shared document — Word stops underlining errors entirely.

You can find this under: File → Options → Proofing → "Check spelling as you type"

There's also a separate setting: "Hide spelling errors in this document only." This is a document-level override that suppresses red underlines without actually disabling spell check globally. Writers and editors sometimes turn this on to reduce visual clutter during drafting — and then forget it's on.

2. The Wrong Proofing Language Is Assigned 🔤

This is where things get less obvious. Word assigns a proofing language to text, and if that language doesn't have a dictionary installed — or if the language is set to one you don't expect — spell check either won't work or will check against the wrong dictionary.

This happens more often than people realize because:

  • Pasting text from another source can bring in foreign language formatting
  • Templates may be configured for a different locale
  • Text can be accidentally marked as "Do not check spelling or grammar" — a per-text language setting that tells Word to skip it entirely

To check this, select your text, go to Review → Language → Set Proofing Language, and verify the correct language is selected and the "Do not check spelling" box is unchecked.

3. Proofing Tools Aren't Installed

Microsoft 365 and standalone Office installations don't always install proofing tools for every language by default. If your document is set to a language whose dictionary isn't installed on your machine, spell check will silently do nothing.

This is especially common when:

  • You've switched Office language packs
  • You're using a volume-licensed or enterprise-managed installation where IT controls which language packs are deployed
  • You're running Office on a new machine where proofing tools weren't included in the initial setup

4. The Document Is Protected or in a Restricted Mode

Word documents can be protected against editing using Restrict Editing controls. When editing restrictions are active, proofing tools are often disabled as a side effect. This is intentional — Word won't mark errors in text it considers locked.

Similarly, documents opened in Protected View (which Word uses automatically for files downloaded from the internet or received via email) disable spell check until you explicitly enable editing.

5. A Corrupt Normal Template or Word Settings File

Word stores many of its default behaviors — including proofing settings — in a template file called Normal.dotm. If this file becomes corrupted, unusual behavior across Word is common, including broken spell check.

Renaming or deleting Normal.dotm (Word will regenerate it automatically on next launch) resolves template corruption issues in many cases.

6. Add-ins or Group Policy Conflicts

In corporate or managed environments, Group Policy settings pushed by IT administrators can override Word's proofing behavior. Add-ins can also interfere with background proofing processes. Running Word in Safe Mode (by holding Ctrl while launching) disables add-ins temporarily and helps isolate whether an add-in is causing the problem.

How the Fix Depends on Your Setup 🖥️

ScenarioMost Likely CauseWhere to Look
Home user, personal documentSetting toggled offFile → Options → Proofing
Pasted content not checkedWrong proofing language on textReview → Language
Corporate laptop, IT-managedGroup Policy or missing language packIT department or Office admin
Downloaded or emailed fileProtected View activeEnable Editing prompt
Affects only one document"Hide errors" or "Do not check" setDocument-level language settings
Affects all documentsNormal.dotm corruptionRename/reset Normal.dotm

What Makes This Tricky to Diagnose

Spell check failures in Word are rarely caused by a single universal issue. The same symptom — no red underlines — can come from a global setting, a document-level flag, a missing language pack, or a managed IT policy. Two users experiencing the exact same problem on the surface may need completely different fixes.

Your version of Word matters too. Microsoft 365 receives ongoing updates that sometimes change where settings live or introduce new proofing behavior. Word 2019, 2021, and older perpetual licenses behave somewhat differently, particularly around language pack management and how proofing tools are installed.

Whether you're on a personal machine with a standalone Office license, a managed corporate device, or using Word through a browser via Microsoft 365 online (which has its own separate proofing behavior), the path to fixing spell check runs through your specific configuration — not a one-size-fits-all answer.