msthes3.dll Errors: Restore Microsoft Works Proofing on Windows

msthes3.dll is a legacy Microsoft Thesaurus component, most strongly associated with Microsoft Works 2000 and its proofing tools. If Windows reports that msthes3.dll is missing or cannot be loaded, repair the Works or legacy Microsoft installation that called it instead of downloading a replacement DLL.

What this file actually does

MSTHES3.DLL is a Microsoft Thesaurus engine used by older proofing components. Historical Microsoft Works 2000 file inventories place it with the other proofing files in:

#	Preview	Product	Price
1		McGraw-Hill's Proofreading Handbook	$7.88	Buy on Amazon
2		The Infographic Guide to Grammar: A Visual Reference for Everything You Need to Know (Infographic...	$7.82	Buy on Amazon
3		The Pocket Book of Proofreading: A guide to freelance proofreading & copy-editing	$15.89	Buy on Amazon
4		Copyediting and Proofreading For Dummies (For Dummies Series)	$14.69	Buy on Amazon
5		APA Guidelines - 7th Edition: a QuickStudy Laminated Reference Guide	$6.48	Buy on Amazon

C:Program FilesCommon FilesMicrosoft SharedProof

On 64-bit Windows, a legacy installer may instead use a path beneath:

C:Program Files (x86)

The exact path depends on the installer and operating system. It should not normally be placed in C:WindowsSystem32 or C:WindowsSysWOW64.

#1 Best Overall

Sale

McGraw-Hill's Proofreading Handbook

$7.88

Buy on Amazon

The file is not a normal Windows system component, Visual C++ runtime, DirectX library, .NET assembly, or device driver. Its strongest documented connection is Microsoft Works 2000, although other older Microsoft products could share the Microsoft SharedProof folder.

A complete Works proofing installation can include more than the DLL. Microsoft’s archived troubleshooting material names related files including:

msthes3.dll
msth3am.lex
msth3br.lex

The .LEX files contain dictionary data used with the engine. That is why copying only msthes3.dll often leaves the thesaurus broken.

Older file records describe this as a 32-bit Win32-era component. Historical version and size records are not a universal specification for every copy, so do not use an arbitrary file listing as proof that a downloaded DLL is correct.

Causes and symptoms

The exact Works messages may mention companion files instead of MSTHES3.DLL. That does not rule out this engine as the underlying problem because the thesaurus depends on several files working together.

First identify the program that is calling the DLL

Do not begin by searching the entire drive for a replacement file. First determine which application needs it.

Check the error dialog

Read the title bar and the text around the error. If it appears while launching Microsoft Works, opening a document, or using Thesaurus, Works is the likely parent application.

If the dialog appears after launching another old Microsoft program, note that program instead. Multiple products may share the Microsoft SharedProof directory, so deleting or replacing a shared file can affect more than one application.

Check Task Manager

1. Reproduce the error.
2. Press Ctrl + Shift + Esc.
3. Select Processes or Details.
4. Look for the application that stopped responding or closed.
5. Right-click it and select Open file location when available.
6. Record the executable name and installation folder.

If the process disappears too quickly, open Task Manager first and then launch the application.

Check Event Viewer

1. Press Win + R.
2. Type eventvwr.msc.
3. Press Enter.
4. Expand Windows Logs.
5. Select Application.
6. Look for an Error entry at the time of the failure.
7. Open the entry and check Faulting application name, Faulting module name, and the event details.

Event Viewer may identify the executable rather than msthes3.dll. That is still useful because the executable tells you which installation must be repaired.

Fix 1: Repair or reinstall Microsoft Works

This is the most reliable fix when the error is connected with Works 2000 or another old Works installation. The original Microsoft troubleshooting procedure involves renaming damaged proofing files and rerunning Works Setup.

Rank #2

Sale

The Infographic Guide to Grammar: A Visual Reference for Everything You Need to Know (Infographic Guide Series)

$7.82

Buy on Amazon

If Works is listed in Windows

1. Close Works and any other old Microsoft programs.
2. Press Win + R.
3. Enter:

text
appwiz.cpl

1. Press Enter.
2. Select Microsoft Works or the relevant legacy Microsoft product.
3. Choose Change, Repair, or Uninstall/Change, depending on what appears.
4. Select the repair or reinstall option.
5. Restart Windows when Setup finishes.
6. Open Works and test the Thesaurus function.

If the installer asks for a disc or source folder, use the original installation media. Do not point Setup at a random DLL file.

Rename the proofing files before running Setup

Renaming preserves the old files in case another shared application needs them.

1. Close Works.
2. Open File Explorer.
3. Browse to the proofing folder, commonly:

text
C:Program FilesCommon FilesMicrosoft SharedProof

1. If that folder is not present, check the corresponding Program Files (x86) path.
2. If the files exist, rename them as follows:

text
msthes3.dll → msthes3.old
msth3am.lex → msth3am.old
msth3br.lex → msth3br.old

1. Insert the original Works media or mount its legitimate installer.
2. Run the Works Setup program.
3. Choose Repair or reinstall the relevant proofing features.
4. Restart Windows.
5. Test the same document or Thesaurus command that produced the error.

If Windows refuses to rename a file, restart the computer and try again before Works launches. You may need administrator approval for the shared folder.

How to tell whether this worked

The repair succeeded if:

• Works starts without the DLL message.
• The Thesaurus command opens normally.
• The application can load a dictionary without reporting a missing .LEX file.
• Event Viewer no longer records the same startup failure.

If Setup completes but the error remains, the installer may not include the required proofing feature, the installation media may be incomplete, or the old program may not be compatible with the current Windows release.

Fix 2: Check antivirus quarantine before restoring anything

Security software can quarantine a damaged or suspicious DLL. It can also remove a legitimate old file when the file has unusual age, packaging, or behavior. Treat quarantine as a warning, not as proof that restoring the file is safe.

Check Windows Security Protection History

1. Open Start.
2. Type Windows Security.
3. Open it.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review entries from the time the error began.
7. Expand any entry associated with Works, the proofing folder, or msthes3.dll.

Do not restore the file automatically. First confirm that it came from the original Works installation and that the system is not infected.

The safer sequence is:

1. Run a Windows Security scan.
2. If malware is detected, follow Windows Security’s removal instructions.
3. Obtain the original Works installer or media.
4. Reinstall the proofing component.
5. Restore a quarantined file only when its provenance is trusted and your security software confirms it is safe.

If the file is immediately quarantined again, stop restoring it repeatedly. The file may be altered, compromised, or incompatible with the security product’s rules. Reinstall the parent application from trusted media instead.

Fix 3: Check the complete proofing folder

A “module could not be found” message does not always mean that msthes3.dll itself is absent. Windows may have found the DLL but failed to load one of its dependencies.

Check the folder used by the Works installation and look for:

Rank #3

The Pocket Book of Proofreading: A guide to freelance proofreading & copy-editing

$15.89

Buy on Amazon

msthes3.dll
msth3am.lex
msth3br.lex

Do not treat the presence of the DLL alone as proof of a healthy installation. The dictionary files, language data, and other proofing engines must match the application.

Also watch for a similarly named file such as:

MSTH3ES.DLL

MSTH3ES.DLL and MSTHES3.DLL are different filenames. Renaming or replacing one does not repair the other.

If the DLL exists but the application still reports a missing module, reinstall the complete proofing feature. Avoid copying files from another PC, because the other installation may have a different build, language resource, architecture, or dependency set.

Fix 4: Use compatibility settings for 32-bit Works software

Older Works releases were designed for a Windows environment very different from Windows 10 and Windows 11. A 32-bit application can run on 64-bit Windows in many cases, but old installers, copy protection, setup routines, and proofing components may not behave correctly.

Try the compatibility troubleshooter:

1. Right-click the Works shortcut.
2. Select Properties.
3. Open the Compatibility tab.
4. Select Run compatibility troubleshooter.
5. Apply the recommended settings.
6. Start Works and test the failing feature.

You can also enable Run this program as an administrator temporarily if Setup or the application cannot write to its installation directory. This does not repair the DLL, but it can reveal whether the failure is caused by access restrictions.

Do not force a 64-bit replacement into the installation. The historical component is a Win32-era file, and architecture mismatches can produce messages such as “not designed to run on Windows.”

If compatibility settings do not help, run the application in a supported older Windows environment. If you use a virtual machine or another legacy environment, keep it isolated, updated where possible, and use it only for the old application and document recovery.

Fix 5: Repair current Microsoft Office only when Office is the caller

Microsoft Works 2000 and current Microsoft 365 are not repaired through the same installer. A current Office repair procedure should not be assumed to repair an old Works proofing engine.

If Event Viewer or the error dialog clearly identifies a current Office installation:

1. Open Settings.
2. Select Apps.
3. Select Installed apps.
4. Find Microsoft 365 or the installed Office entry.
5. Select the three-dot menu.
6. Choose Modify.
7. Select Online Repair.
8. Follow the prompts and restart Windows.

Use this route only for the current Office installation that actually produced the error. If Works is the caller, use the Works media and installer instead.

Fix 6: Repair Windows components with DISM and SFC

DISM and System File Checker repair protected Windows components. They are useful when the failure began with broader Windows corruption, but they are unlikely to restore a Works-installed proofing DLL that lives outside the Windows component store.

Rank #4

Sale

Copyediting and Proofreading For Dummies (For Dummies Series)

$14.69

Buy on Amazon

Run DISM first, then SFC.

1. Open Start.
2. Type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Run:

bat
DISM.exe /Online /Cleanup-image /Restorehealth

1. Wait for it to finish.
2. Then run:

bat
sfc /scannow

1. Wait until verification reaches 100 percent.
2. Restart Windows.
3. Test the application again.

If DISM reports that it cannot complete the repair, restart the PC, install pending Windows updates, and run the command again. If SFC reports that it repaired files, restart and retest. If both commands complete successfully but Works still reports msthes3.dll, return to the Works repair procedure.

When manually tracking component corruption across DISM and SFC becomes repetitive, Outbyte PC Repair can scan and show what it identifies; its full version handles the repair, but reinstalling Works remains the definitive fix for a Works-specific proofing file.

Do not use SFC or DISM as a reason to download a DLL into a Windows folder. These commands repair Windows through its servicing mechanisms, not by registering arbitrary files.

Fix 7: Use System Restore after a recent system change

System Restore is relevant if the error began immediately after a driver installation, application removal, security cleanup, or major system change.

1. Press Win + R.
2. Type:

text
rstrui.exe

1. Press Enter.
2. Select Next.
3. Choose a restore point dated before the error began.
4. Select Scan for affected programs if available.
5. Review the changes.
6. Select Next, then Finish.
7. Allow Windows to restart.

System Restore rolls back system files, registry settings, and installed programs. It does not normally remove personal documents, but review the affected-program list before proceeding.

If the restore does not resolve the problem, reinstall Works rather than repeatedly restoring old system states.

Fix 8: Update Windows and drivers only when evidence points there

A driver is not the normal cause of a missing Microsoft Thesaurus engine. Do not use Device Manager as the first repair for this file. Check drivers when the DLL error appeared alongside broader crashes, failed graphics or storage devices, or a recent hardware change.

To check for driver updates:

1. Right-click Start.
2. Select Device Manager.
3. Expand the relevant category.
4. Right-click the affected device.
5. Select Update driver.
6. Choose Search automatically for drivers.
7. Restart Windows if a driver is installed.

For a recently updated device, open its Properties, select the Driver tab, and use Roll Back Driver when that option is available and the timing matches the failure.

Windows Update is also worth checking:

1. Open Settings.
2. Select Windows Update.
3. Select Check for updates.
4. Install available updates.
5. Restart and test Works again.

When checking dozens of devices manually is the problem, Outbyte Driver Updater can scan and identify driver versions; its full version performs the installation, but updating a driver will not replace the Works proofing component itself.

Why you should not copy msthes3.dll into System32

Copying a DLL into System32 or SysWOW64 is usually the wrong repair for this error.

The parent program expects its proofing engine in the application’s shared proofing directory. Moving the file elsewhere can cause:

• The application to continue searching the original path.
• A 32-bit program to load an incompatible file.
• Missing .LEX dictionaries to remain unresolved.
• Multiple Microsoft applications to use mismatched proofing files.
• Windows or security software to treat the copied file as untrusted.
• A different application to load the wrong version.

Manual copying is not categorically impossible in every historical deployment, but it is not the supported or reliable general solution. Reinstall the parent application so Setup restores the complete matching component set.

Why regsvr32 is generally inappropriate

Do not run:

regsvr32 msthes3.dll

regsvr32 is intended for self-registering COM or ActiveX components that provide a DllRegisterServer entry point. MSTHES3.DLL is identified as a thesaurus engine, not as an established self-registering control.

Best Value

APA Guidelines - 7th Edition: a QuickStudy Laminated Reference Guide

$6.48

Buy on Amazon

Registration cannot recreate the missing dictionary files, repair a damaged installation, or make an incompatible 32-bit application work on a newer system. If regsvr32 reports that the entry point is missing, that is expected for a DLL that was not designed for this registration process.

If the original installation media is unavailable

Search legitimate sources you already own:

• Original Works discs or product packaging.
• A backed-up installer from the same product.
• An organization’s licensed software archive.
• The original computer’s recovery media, where applicable.

Before reinstalling, back up Works documents and export any data the application stores separately. Avoid downloading a standalone msthes3.dll from a random DLL site. Such files can contain malware, have the wrong architecture or language resources, and still fail because the companion dictionaries and application configuration are missing.

No current official Microsoft standalone download for this legacy file is established here. The safe source is the original Microsoft application installation, not a generic DLL archive.

If the media cannot be recovered, install a supported replacement application where practical and convert or recover the old documents. If Works is essential, use a controlled compatible environment rather than repeatedly forcing legacy binaries into Windows system directories.

When to stop repairing

Stop replacing files when:

• The original application is no longer needed.
• The installation media is unavailable and the application cannot be verified.
• Antivirus repeatedly detects the copied or restored DLL.
• The program fails for several unrelated compatibility reasons.
• The only proposed solution is an unverified DLL download.
• The application cannot run reliably even after a complete reinstall.

Recover the documents first, then move to a supported application or isolated legacy environment. Repeatedly copying old binaries can create a less reliable system without fixing the actual dependency chain.

FAQ

Is msthes3.dll a Windows 11 or Windows 10 system file?

No. It is a legacy Microsoft Thesaurus component associated most strongly with Microsoft Works 2000 proofing tools. It should not normally be installed in the Windows system directories.

Does Microsoft Works 2000 use this file?

Historical Works 2000 inventories list MSTHES3.DLL in the shared Microsoft proofing folder. Earlier Works releases used different thesaurus engines and filenames, so do not assume every Works version uses this exact DLL.

Can I download msthes3.dll separately?

A standalone download is not the safe primary fix. Reinstall the Microsoft application that supplied it so the matching engine, dictionaries, language data, and configuration are restored together.

Why does Windows say that a module is missing when the DLL is visible?

The loader may be unable to find a dependency used by the DLL. A missing .LEX dictionary or another proofing component can produce a similar failure. Reinstall the complete proofing feature rather than copying the visible DLL.

Should I register the file with regsvr32?

Generally, no. A thesaurus engine is not established as a self-registering COM or ActiveX component, and registration cannot repair missing dictionaries or an incomplete Works installation.

Is MSTH3ES.DLL the same file?

No. The names are similar but identify different files. Confirm the exact filename shown by the error and repair the application that owns that component.

Will SFC or DISM restore it?

Usually not. SFC and DISM repair protected Windows components. They are useful for general Windows corruption but are not a dependable way to restore a legacy Works file installed in Microsoft SharedProof.

What is the safest fix?

Identify the calling program, rename damaged proofing files if present, and run the original Works or legacy application Setup repair. Then test the Thesaurus feature and confirm that antivirus has not quarantined the restored installation.

Quick Recap

SaleBestseller No. 1

McGraw-Hill's Proofreading Handbook

$7.88

SaleBestseller No. 2

The Infographic Guide to Grammar: A Visual Reference for Everything You Need to Know (Infographic Guide Series)

$7.82

Bestseller No. 3

The Pocket Book of Proofreading: A guide to freelance proofreading & copy-editing

$15.89

SaleBestseller No. 4

Copyediting and Proofreading For Dummies (For Dummies Series)

$14.69

Bestseller No. 5

APA Guidelines - 7th Edition: a QuickStudy Laminated Reference Guide

$6.48

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.