TechReview
How-To & Guides

Winword.exe: What It Is, Why It Uses High CPU, and How to Fix It

Published By Shivam Sharma6 min read
Winword.exe title card: What it is, is it safe, and how to fix high CPU

Winword.exe is Microsoft Word itself, not a separate program you installed by accident. If the file sits in the Microsoft Office folder and carries a Microsoft signature, it is genuine, and high CPU use usually comes down to an add-in or a Word process that did not close properly. Both are fixable, and neither means your computer is infected.

Is winword.exe safe?

Yes, the real one is. Winword.exe is the file name of the MS Office Word program, and running it from the Run dialog simply opens Word. The question worth asking is not whether winword.exe exists, but whether the copy on your machine is the real one.

There are three quick checks. First, location. Open Task Manager, right-click the winword.exe process, and choose “Open file location.” On a modern Click-to-Run install of Microsoft 365 or Office 2019, 2021, or 2024, the genuine file is at C:\Program Files\Microsoft Office\root\Office16\WINWORD.EXE on 64-bit Windows, or under Program Files (x86) on 32-bit installs. Older MSI installs use the same Office16 folder without the “root” part. The number after “Office” varies by version.

Second, signature. Right-click the file, open Properties, and look at the Digital Signatures tab. The legitimate file is signed by Microsoft Corporation. If a file has no signature at all, that alone is reason to be suspicious.

Third, a scan. Right-click the file and choose “Scan with Microsoft Defender.” You can also upload a copy to VirusTotal for a multi-engine check, though one or two flags on a clean file are common, so treat a single flag as a prompt to investigate, not a verdict.

Two warnings belong here. No Microsoft source lists System32 as a legitimate location for winword.exe, so any copy found outside the Office folder should be treated as suspicious and scanned. And red flags for an imposter include high resource use in Task Manager and the process running when Word is not open at all. Malware does sometimes borrow trusted names like this one, which is exactly why location and signature matter more than the name.

Why is winword.exe still running after you close Word?

This confuses people most, because Word looks closed while its process keeps working. Microsoft’s support forums carry a case of winword.exe occupying 96% CPU with Word closed, so a lingering process is real, not imagined.

One known trigger is Windows Explorer’s preview pane, which can auto-start winword.exe when you merely select a document, even if you never open it. In the reported case, turning off the preview pane stopped it. Another way to test the cause is Safe Mode: hold Ctrl while clicking the Word shortcut and accept the prompt, then create a document, save, and exit as usual. If the process ends cleanly in Safe Mode, an add-in is the likely culprit. Our BackgroundTaskHost.exe guide covers the same family of background-process problems.

Why does winword.exe use so much CPU?

One honest note: Microsoft has no dedicated guide for winword.exe high CPU, so what follows comes from its support forums and troubleshooting guides.

Add-ins are the usual suspect. In one forum case of winword.exe using around 25% CPU even when Word was not in use, the answer was that the issue is usually caused by add-ins, with Word running in the background. A lingering process after closing Word is the second cause, and it can consume far more than 25%. A damaged document or a corrupted Normal.dotm global template can also make Word misbehave, and both have documented recovery procedures. The last possibility is the unpleasant one: malware impersonating the filename, which can consume high CPU and cause crashes.

How to fix winword.exe high CPU

Work through these in order, and stop as soon as the problem is gone. Most cases end at step 3 or 4.

  1. Restart your computer. Microsoft lists this first in its fix-errors guide, and its repair guide says to install the latest Windows updates and restart before running deeper repairs.
  2. End the lingering process. In Task Manager, go to the Processes tab, find WinWord.EXE, and choose End Process. Then reopen Word normally and check whether the behaviour repeats.
  3. Test in Safe Mode. Hold Ctrl while clicking the Word shortcut and accept the prompt, or type “winword /safe” in the Run dialog, noting the space before the slash. If Word works and closes cleanly in Safe Mode, an add-in is the likely cause. The “winword /a” switch also stops global templates loading.
  4. Disable add-ins one at a time. In Word, go to File, then Options, then Add-ins. Under Manage, select COM Add-ins, click Go, uncheck all add-ins, and click OK. Re-enable them one at a time until the culprit shows itself.
  5. Replace a corrupted Normal.dotm template. Close all Office programs, then run “ren %userprofile%\AppData\Roaming\Microsoft\Templates\Normal.dotm OldNormal.dotm”. Restart Word and it creates a fresh template.
  6. Update Windows and Office. Microsoft’s troubleshooting guide says to confirm both are up to date before going further. In any Office app, go to File, then Account, then Product Information, then Update Options, then Update Now.
  7. Repair Office. Right-click Start, open Installed apps on Windows 11 (or Apps and Features on Windows 10), select the Microsoft 365 or Office product, and choose Modify. For Click-to-Run installs, pick Online Repair and then Repair; Quick Repair only replaces corrupted files. Repair affects the whole Office suite, and Online Repair needs an internet connection.
  8. Run DISM, then SFC. In an administrator Command Prompt, first run “DISM.exe /Online /Cleanup-image /Restorehealth” and wait for “The operation completed successfully.” Then run “sfc /scannow” and wait for “Verification 100% complete.” Microsoft’s current guide runs DISM before SFC.
  9. Reinstall Office as a last resort. Microsoft documents “restart your computer and reinstall Office” as a step, but only after repair and system-file repairs have failed.

There are deeper registry procedures in Microsoft’s troubleshooting guide, such as deleting the Word Data key, but those are advanced steps that require backing up the registry first. They are not front-line fixes, and nothing above requires them.

What not to do with winword.exe

Do not delete the file. Microsoft’s own answer is blunt: winword.exe is the file name of the MS Office Word program, and if you delete it, Word will no longer work. Do not permanently block Word’s network access either; if you have the paid version, blocking it can stop the subscription working. And do not download a replacement winword.exe from unofficial websites. Installers from unofficial sources can bundle programs that exploit trusted process names.

FAQ

Is winword.exe a virus? No. The legitimate file is Microsoft Word. Only an imposter copy using the same name is a threat, and the location and signature checks above tell the two apart.

Where should winword.exe be located? Inside the Microsoft Office folder, typically C:\Program Files\Microsoft Office\root\Office16\WINWORD.EXE on modern 64-bit installs. Anywhere else deserves a scan.

Can I end winword.exe in Task Manager? Yes, for a lingering process. End it from the Processes tab, then reopen Word normally and see whether the problem repeats.

Why does winword.exe run when Word is closed? Usually a lingering process or the Explorer preview pane auto-starting it. The Safe Mode test in the fix steps will tell you whether an add-in is behind it.

Can I delete winword.exe to stop high CPU? No. Deleting it breaks Word entirely. Fix the cause with the steps above instead.

Sources

Related reviews and guides