Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.“This application failed to start because intlname.dll was not found.”
The intlname.dll error usually points to an old Microsoft Office component rather than a missing Windows system file. intlname.dll belongs to Microsoft Office 2003, also known as Office 11, and should normally be restored through Office repair or reinstallation.
As an Amazon Associate I earn from qualifying purchases.
Which fix applies to you
Use the description that matches what you see:
- A program will not start and says
intlname.dllis missing or was not found: repair Microsoft Office 2003 first. - Microsoft Word crashes and lists
Intlname.dllas the faulting module: install Office 2003 Service Pack 3, then repair Office if necessary. - Windows Security recently quarantined the file: check Protection History before restoring anything.
- You copied the DLL into
System32,SysWOW64, or a game folder: remove the copied file and repair the application that originally installed it. - The popup names a modern game or unrelated program: verify the actual executable and faulting module.
intlname.dllis associated with Office 2003, not a general Windows, DirectX, Visual C++, .NET, or game dependency. - The message says “The specified module could not be found”: the named DLL or one of its dependencies may be unavailable. Repair Office rather than downloading a loose DLL.
- The error appeared with broader Windows corruption symptoms: use DISM and SFC as secondary diagnostics.
- You are maintaining an unsupported Office 2003 installation: repair it only when necessary, then plan migration to a supported Office version.
What is intlname.dll?
intlname.dll is a Microsoft Office 2003 component installed with Microsoft Office 11. Historical Office installations place it in the Office Smart Tag directory:
C:Program FilesCommon FilesMicrosoft SharedSmart TagINTLNAME.DLL
On 64-bit Windows running 32-bit Office, the equivalent location is typically under the 32-bit Common Files directory. The exact path can vary with Windows architecture, language, and installation method.
#1 Best Overall
- The Microsoft Office 365 Bible: The Most Updated and Complete Guide to Excel, Word, PowerPoint, Outlook, OneNote, OneDrive, Teams, Access, and Publisher from Beginners to Advanced
- ABIS BOOK
The file is associated with Office Smart Tags, particularly the “Person Name (International Name with Outlook Contact)” action. Smart Tags identified text and offered Office-related actions, including looking up a person in Outlook.
This is not established as a normal Windows component. It is not a Visual C++ runtime, DirectX file, .NET component, device driver, or general-purpose game library. Public records identify a 32-bit Office build, but there is no current Microsoft file manifest confirming one version and size for every Office edition.
First fix: repair Microsoft Office 2003
Office repair is the safest and most likely solution when the file is missing, damaged, or was never installed.
Free tools Windows power users keep installed
One-click scans. No signup required.
Repair from Control Panel
- Close Word, Outlook, Excel, and every other Office program.
- Open Control Panel.
- Select Add or Remove Programs on Windows XP, or Programs and Features on later Windows versions.
- Select Microsoft Office 2003.
- Click Change.
- Choose Repair, Repair Office, or Detect and Repair.
- Follow the prompts.
- Insert the original Office CD or provide the licensed installation-source path if Windows Installer requests it.
- Restart Windows when the repair finishes.
The wording differs between Windows versions and Office editions, but the operation is the same: Windows Installer compares the Office installation with its source and restores missing files to their intended locations.
Repair from Word 2003
If Word still opens:
- Start Word 2003.
- Select Help.
- Click Detect and Repair.
- Follow the repair wizard.
- Restart Windows.
How to tell whether repair worked
Start Word and open the document or workflow that previously produced the error. The missing-file message should no longer appear, and INTLNAME.DLL should be restored under the Office Smart Tag directory rather than under System32 or SysWOW64.
If repair asks for installation media that you do not have, do not substitute a downloaded DLL. Use the original licensed CD, a legitimate administrative installation point, or reinstall Office from an authorized source.
Second fix: install Office 2003 Service Pack 3
A separate problem occurs when Word crashes and reports Intlname.dll as the faulting module. That wording does not necessarily mean the file is missing. It can mean that Word crashed while executing code in the DLL.
Recommended Free Tools
Microsoft documented an Office 2003 Word crash involving Intlname.dll. Office 2003 Service Pack 3 addresses that problem and should be installed before spending time on manual file replacement.
Download the official package from the Microsoft Download Center. The package is named:
Office2003SP3-KB923618-FullFile-ENU.exe
To install it:
- Close all Office programs.
- Download the package from Microsoft.
- Right-click the downloaded installer and select Run as administrator if that option is available.
- Follow the setup prompts.
- Restart Windows.
- Test Word again.
If the installer reports that Office is not present, the installation source is unavailable, or the update cannot apply, repair or reinstall Office first. Do not copy a file from a different Office build into the installation.
Third fix: check Windows Security Protection History
Defender or another antivirus program may have quarantined an Office file. Check that before manually restoring anything.
- Open Windows Security.
- Select Virus & threat protection.
- Click Protection history.
- Look for an entry involving
INTLNAME.DLL, Microsoft Office, or the original Office directory. - Expand the entry and review the detected path and action.
- Confirm that the path belongs to your licensed Office installation.
- Update Defender and run a full scan before deciding whether to restore the file.
Only restore the file when its original path, Office source, signature, and contents are trusted. Microsoft warns that Allow on device can reintroduce a genuine threat. If the file was found in a game folder, a temporary directory, or a random download location, do not restore it as an Office file.
After a trusted restoration, run Office repair so Windows Installer can validate the complete installation.
Fourth fix: remove manually copied DLLs
Do not copy intlname.dll into any of these locations:
C:WindowsSystem32
C:WindowsSysWOW64
A game folder
A modern Microsoft Office folder
A 32-bit Office DLL belongs with the Office installation that owns it. Copying it elsewhere can create architecture conflicts, version mismatches, or a new security problem. It can also leave the original Office installation damaged.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →If you already copied the file:
- Delete the manually copied copy from the unrelated directory.
- Empty the Recycle Bin if appropriate.
- Run Office repair from Control Panel.
- Restart Windows.
- Test the Office application again.
System32 does not mean “all system DLLs,” and SysWOW64 does not mean “the correct location for every 32-bit DLL.” Windows searches directories according to the executable and dependency context. A file in the wrong directory may be loaded by the wrong program or may mask the actual installation problem.
Fifth fix: test Word without add-ins
A damaged Word profile, template, Smart Tag setting, or add-in can cause a crash even when the DLL exists.
- Press Windows key + R.
- Enter:
winword.exe /a
- Press Enter.
The /a switch starts Word without global templates and add-ins. If Word works normally this way:
- Open Word normally.
- Select File, Options, and Add-ins where those controls are available.
- At the bottom, select COM Add-ins from the Manage list.
- Click Go.
- Clear the add-ins.
- Restart Word.
- Re-enable add-ins one at a time until the failing add-in is identified.
For older Word 2003 installations, Microsoft’s guidance for resetting user options and registry settings also covers the Normal.dot template and Word registry data. Export registry keys before deleting or changing them. A registry reset is a later diagnostic step, not the first repair.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallSixth fix: repair broader Windows component corruption
intlname.dll is not known to be a protected Windows system file, so System File Checker normally will not restore it. Use these commands when Windows itself shows additional corruption symptoms, updates fail, or other protected system files are also damaged.
- Open Start.
- Type
Command Prompt. - Right-click Command Prompt.
- Select Run as administrator.
- Run DISM first:
DISM.exe /Online /Cleanup-Image /RestoreHealth
- Wait for it to complete.
- Run SFC:
sfc /scannow
- Restart Windows.
- Retry Office repair and test the affected program.
DISM repairs the Windows component store that SFC uses. SFC then checks protected Windows files. If SFC reports that it found no integrity violations, that does not prove that intlname.dll is present; continue with Office repair.
When repeatedly hunting through Windows components and interpreting SFC or DISM output becomes impractical, Outbyte PC Repair can show what it identifies in a free scan; repairs are performed by the full version, and it is not required for an Office-specific fix.
Seventh fix: use System Restore after a recent change
If the error began immediately after a software installation, failed update, or system modification, System Restore may return Windows to an earlier restore point.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Press Windows key + R.
- Enter:
rstrui.exe
- Press Enter.
- Select Choose a different restore point if available.
- Select a restore point from before the error began.
- Click Next, review the affected programs, and select Finish.
- Restart Windows and test Office.
System Restore does not replace a missing Office installation source. If the error remains, use Detect and Repair or reinstall Office.
Do not use regsvr32 as a general repair
This command is often recommended for missing DLL errors:
regsvr32 intlname.dll
It is not a verified repair for intlname.dll. regsvr32 works only when a DLL provides the registration entry point that the command expects, such as DllRegisterServer. There is no reliable Microsoft instruction confirming that intlname.dll is a self-registering DLL.
Office repair is the correct method because it restores the file, related files, registry data, and version-compatible components together. If regsvr32 reports that the entry point was not found, that does not mean the DLL is missing or that another copy should be downloaded.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsIf the popup names a game or unrelated application
First identify the actual program producing the message.
- Note the executable named in the error window.
- Open Task Manager if the program remains running.
- Check the application’s installation directory.
- Review Event Viewer or Windows Error Reporting for the application name and faulting module.
- Confirm whether the faulting module is really
intlname.dll.
If the executable is a game or modern utility, reinstall that program from its official source and contact its publisher if it still requests an Office 2003 file. Do not place intlname.dll in the game directory. The evidence associates this DLL with Office 2003, not with modern games.
If the message says “The specified module could not be found,” Windows may be unable to load a dependency of the named DLL. The visible filename is not always the complete cause. Repair the owning Office installation and inspect the application’s event record rather than guessing at individual dependencies.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Drivers and Windows Features are usually unrelated
Device Manager, Windows Features, DirectX repair, Visual C++ redistributables, and driver reinstallation are not primary fixes for an Office-owned intlname.dll.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Use Device Manager only when the error occurs alongside a separate hardware problem:
- Right-click Start.
- Select Device Manager.
- Expand the relevant device category.
- Right-click the affected device.
- Select Update driver or Uninstall device only when troubleshooting that device specifically.
- Restart Windows and install the driver from the hardware manufacturer if required.
Do not enable random Windows Features to obtain this DLL. If you are separately maintaining several machines and manually identifying stale hardware packages is taking too long, Outbyte Driver Updater can scan for driver issues; its free scan identifies findings, while driver installation is performed by the full version. It is not a substitute for repairing Microsoft Office.
Why random DLL downloads are unsafe
Avoid websites offering a standalone intlname.dll download. A loose DLL may be:
- Malware or a modified file
- The wrong Office build
- The wrong architecture
- Incompatible with the executable loading it
- Missing related Office files
- A copy that causes Windows to load the wrong version
Even a clean file may not fix the underlying Office installation, Windows Installer registration, Smart Tag configuration, or documented Word crash.
Use Microsoft Office repair, the original licensed installation source, and Microsoft’s Office 2003 SP3 package instead.
Frequently asked questions
Is intlname.dll a Windows system file?
No credible evidence places it in the normal Windows component set. Historical Office installations place it in the Microsoft Shared Smart Tag directory.
Which program installs intlname.dll?
Microsoft Office 2003, also called Microsoft Office 11. Word 2003 and other Office 2003 applications may trigger it.
Is intlname.dll 32-bit or 64-bit?
Public Office records identify a 32-bit build. No separate 64-bit build has been verified. On 64-bit Windows, 32-bit Office normally uses the 32-bit Common Files location.
Does a faulting-module error mean the DLL is missing?
No. If Word lists Intlname.dll as the faulting module, Word may have crashed while using the file. Install Office 2003 SP3 and repair Office instead of replacing the DLL blindly.
Should I run SFC?
Only as a secondary Windows diagnostic. SFC normally will not restore an Office-owned DLL. Repair Office first.
Should I install Office 2003 SP3?
Yes, when maintaining Office 2003 or troubleshooting a Word crash involving Intlname.dll. Use Microsoft’s official SP3 package and restart afterward.
Can I register the file with regsvr32?
There is no verified Microsoft instruction that intlname.dll requires registration. Do not treat regsvr32 as a general missing-DLL repair command.
Is Office 2003 still supported?
No. Microsoft Office 2003 reached end of support on April 9, 2014. If possible, migrate to a supported Office release rather than continuing to maintain the legacy installation.
Prevention
Keep the original Office installation source and license information available, and do not delete Office files manually. When antivirus quarantines an Office component, review Protection History before restoring it. Keep Office 2003 patched with its official updates if it must remain in use, and plan migration because the product is unsupported.
For this specific file, the dependable repair path is Office Detect and Repair, followed by reinstalling Office 2003 and applying Service Pack 3 when necessary. Loose DLL downloads, System32 copying, and blind regsvr32 commands are not substitutes for repairing the application that owns the file.
Quick Recap
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.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems
