msain900.dll is a legacy Microsoft Office component, not a Windows system DLL. If Access reports “Can’t find Language DLL msain900.dll,” the safest fix is to repair or reinstall the Office or Access installation that is requesting it.
Do not begin by downloading a replacement DLL and copying it into C:WindowsSystem32. That file belongs with the Office installation and its language resources. A replacement with the wrong build, language, or architecture may fail again, introduce malware, or hide the actual installation problem.
What is msain900.dll
msain900.dll is associated with Microsoft Office 2000. Public file inventories identify it as a Microsoft Corporation component with the reported version 9.0.0.2719, a 32-bit architecture, and a size of about 0.62 MB. Those details come from historical file metadata rather than a current Microsoft file catalog, so treat them as identification clues rather than a guarantee that every installation contains the same build.
It is not part of:
- Windows itself
- Visual C++ Redistributable
- DirectX
- .NET
- A graphics driver
- A device driver
- A game runtime
The file is normally loaded from an Office program directory or a related language-resource directory. On 64-bit Windows, old 32-bit Office software generally runs through Windows’ 32-bit compatibility environment. The presence of 64-bit Windows does not make msain900.dll a 64-bit system file.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#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
What the error means
The most specific reported message is:
Can’t find Language DLL msain900.dll
The error has been reported when starting Microsoft Access and when opening an existing Access database. It can also appear after an Office upgrade, repair, partial removal, or side-by-side installation involving different Office generations.
Possible Windows loader wording includes messages that say the program cannot start because the file is missing or that the DLL could not be loaded. The exact wording is less important than the caller. Check which program displays the message and whether the problem occurs during startup, while opening an .mdb file, or during Office maintenance.
Work through the fixes below in order.
1. Repair the Office installation
Time needed: 10 to 30 minutes
This is the primary fix when Access or another Office program requests msain900.dll. Repair restores missing files and rebuilds the installation’s component registration without requiring you to locate an individual DLL.
Office 2000
Microsoft documented this maintenance path for Office 2000:
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- Close Access and every other Office program.
- Press
Windowsand typeControl Panel. - Open Control Panel.
- Select Uninstall a program. On older Windows versions, open Add or Remove Programs.
- Select Microsoft Office 2000.
- Choose Change, Change/Remove, or Repair, depending on the Control Panel view.
- Select Repair Office.
- Choose Repair errors in my Office installation.
- Insert the original Office media or provide the original installation source if Windows requests it.
- Allow the maintenance operation to finish.
- Restart Windows.
- Open Access and repeat the action that produced the error.
Microsoft’s documented Office 2000 repair guidance is available on Microsoft Support.
Office 2007 MSI installations
For a traditional Office 2007 installation:
- Close all Office programs.
- Open Control Panel.
- Select Programs and Features.
- Select Microsoft Office or the specific Office 2007 edition.
- Click Change.
- Choose Repair and continue through the wizard.
- If the wizard offers feature selection, make sure Microsoft Access and the required language features are not set to Not Available.
- Restart Windows.
- Test Access again.
If the installation uses an original CD, network share, or administrative installation point, keep that source available. Older Office maintenance operations may not complete without it.
Microsoft 365 or newer Office
Microsoft 365 does not provide a direct replacement for an Office 2000 DLL. If the error appears on a computer that also contains an old Access application, determine which executable is producing the message before repairing the current Office suite.
For current Click-to-Run Office:
- Close Office programs.
- Open Settings.
- Select Apps.
- Open Installed apps or Apps & features.
- Find Microsoft 365 or Microsoft Office.
- Select the three-dot menu and choose Modify.
- Try Quick Repair first.
- If that does not help, repeat the process and choose Online Repair.
- Restart Windows and test the affected program.
Online Repair can reset more of the Office installation and may require sign-in or a working internet connection. It is not a way to install Office 2000 components into an unrelated legacy application.
Free tools Windows power users keep installed
One-click scans. No signup required.
If repair succeeds, the error should disappear when the same Office program or database is opened. If Access still requests msain900.dll, continue with the version and feature checks below rather than copying a DLL manually.
2. Check whether Access or an Access Runtime is involved
Time needed: 10 to 25 minutes
Some database applications do not use the full Microsoft Access program. They use an Access Runtime installation. Repairing the wrong Office product will not necessarily restore the runtime’s files.
First identify the caller:
- Right-click the taskbar and open Task Manager.
- Start the application that displays the error.
- On the Details tab, look for
MSACCESS.EXEor the application’s own executable. - Right-click the process and select Open file location.
- Note whether the path is under
C:Program FilesorC:Program Files (x86). - Close the application.
If the program is an Access Runtime application, open Control Panel → Programs and Features and look for an Access Runtime entry. Repair that exact entry if a Change button is available.
For an Office Access 2007 Runtime installation, Microsoft identifies the official servicing package as Microsoft Office Access Runtime and Data Connectivity Components 2007 Service Pack 3 (SP3). Its package information is on Microsoft Support, and Microsoft’s Update Catalog lists the related packages.
Do not assume the current Microsoft 365 Access Runtime is a replacement for an Office 2000 component. It is a modern runtime with separate x86 and x64 packages. Check the database application’s compatibility requirements before installing it.
After repairing or reinstalling the runtime, restart Windows and launch the database application again. If it still calls for msain900.dll, the application may depend on a separate legacy Office installation or an incomplete upgrade.
3. Check for mixed or partially removed Office versions
Time needed: 15 to 45 minutes
A common pattern is an old Access application alongside Office 2007, Microsoft 365, a trial edition, or an Office version that was only partly removed. Different installers can leave language resources and maintenance records pointing at different locations.
Check the installed products:
- Open Settings → Apps → Installed apps.
- Search for Office, Access, and Runtime.
- Also open Control Panel → Programs and Features if the list is incomplete.
- Record every Office and Access-related entry before changing anything.
- Note which edition the failing application requires.
Repair the specific product that owns the failing executable first. Do not uninstall every Office entry immediately. If repair does not work:
- Back up important Access databases and templates.
- Confirm that you have the product key, installer, installation media, or licensed download for the version you intend to keep.
- Uninstall the damaged or unwanted Office edition through Installed apps or Programs and Features.
- Restart Windows.
- Repair or reinstall the Office edition that the application actually requires.
- Restart again and test the application.
If the error appears while uninstalling Office, do not delete Office folders or registry keys by hand. Use the supported Microsoft removal process for that Office generation, then reinstall from legitimate media.
4. Check antivirus quarantine
Time needed: 5 to 15 minutes
Security software may quarantine or delete an Office file. That is a possible cause, not a confirmed cause specific to msain900.dll.
- Open Windows Security.
- Select Virus & threat protection.
- Open Protection history.
- Look for an Office-related detection or a quarantined file with this name.
- Check the original path, detection details, and date.
- Run a full scan before restoring anything.
Only restore the file if the original path and Office installation are trustworthy and the security product identifies it as a false positive. If the file’s source is uncertain, repair Office instead. Restoring an isolated DLL does not rebuild the installer records or restore companion language files.
5. Confirm the program’s architecture and location
Time needed: 5 minutes
Office 2000 was a 32-bit product. On 64-bit Windows, its files commonly appear under:
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →C:Program Files (x86)
A 32-bit Access executable may search its own Office directory or a language subdirectory. It may ignore a file placed in C:WindowsSystem32, and a file copied from another computer may be the wrong language or build.
To inspect the application path:
- Find the Access shortcut or affected application shortcut.
- Right-click it and choose Properties.
- Review the Target field.
- Open the directory shown there in File Explorer.
- Look for the Office installation and its language folders.
- Do not add a downloaded DLL to the directory unless it came from an official repair or installation process.
A missing dependency can also produce a message that names msain900.dll even when the named file exists. That is another reason repair is more reliable than copying a single file.
6. Do not use regsvr32 as a routine fix
Time needed: 2 minutes
regsvr32 is for DLLs that expose a registration entry point such as DllRegisterServer. There is no reliable evidence that msain900.dll is a self-registering COM server.
Do not treat this as a repair:
regsvr32 msain900.dll
It may return an error stating that the DllRegisterServer entry point was not found. That does not mean Windows needs a different copy of the file. It means registration is not the right repair model for this Office component.
Recommended Free Tools
Office’s installer maintains its own files, language resources, and configuration. Use Office repair or reinstall the affected product instead.
7. Repair Windows components if other system files are failing
Time needed: 15 to 45 minutes
SFC and DISM repair protected Windows components. msain900.dll is an Office application file, so these commands are not the primary or guaranteed fix. Use them when Windows itself is unstable, other protected system files are damaged, or Office repair is failing because the operating system has broader corruption.
- Press
Windows. - Type Command Prompt.
- Right-click Command Prompt.
- Select Run as administrator.
- Run this command:
DISM.exe /Online /Cleanup-image /Restorehealth
- Wait for it to finish.
- Then run:
sfc /scannow
- Restart Windows.
- Retry Office repair and test Access.
Microsoft’s instructions for these commands are available through Microsoft’s System File Checker guidance.
If you repeatedly run SFC and DISM without knowing what changed, Outbyte PC Repair can scan for broader Windows problems and show what it finds; any repair is performed by the full version, and it is not required for this Office-specific fix.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteIf SFC reports that it could not repair some files, save the result, restart, and return to Office repair. Do not assume that a successful SFC scan means msain900.dll has been restored.
8. Update or reinstall related software only when the evidence points there
Time needed: 15 to 60 minutes
This is not a graphics, audio, chipset, or device-driver DLL. Device Manager is therefore not the normal repair path.
Use Device Manager only if the same computer also has unrelated hardware failures:
- Right-click Start.
- Select Device Manager.
- Expand the relevant hardware category.
- Right-click a device and choose Update driver.
- Prefer the driver supplied by the hardware manufacturer or Windows Update.
- Restart if Windows requests it.
Do not expect a driver update to restore an Office language DLL. When manually hunting through many driver versions is the problem, Outbyte Driver Updater can scan and identify stale drivers; its driver installation is handled by the full version, and it is optional rather than a requirement for msain900.dll.
If the error began immediately after installing or removing another application, use Settings → Apps → Installed apps to repair or remove that application instead. If the problem affects only one Windows account, test the same Office program from another account; a damaged per-user configuration is possible, although it is not a confirmed msain900.dll-specific cause.
9. Reinstall Office or Access from original media
Time needed: 30 to 90 minutes
Use this step when repair repeatedly fails, the installation source is damaged, or Office entries are clearly mixed.
Before uninstalling:
- Back up
.mdband other database files. - Record product keys and activation details.
- Confirm that the original installer or licensed source is available.
- Export any required Office templates or custom settings.
- Close every Office process.
Then:
- Uninstall the affected Office or Access product through Windows.
- Restart the computer.
- Remove only leftover folders through normal supported procedures, not registry deletion.
- Install the required Office generation from its legitimate media or source.
- Select Access and the required language features during setup.
- Apply the service pack or supported updates for that product.
- Restart Windows.
- Open Access and test the database.
For a legacy application, reinstalling the exact required Office or Access Runtime generation is usually more dependable than installing a modern runtime and hoping it supplies old files.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.10. Consider System Restore only for a clearly timed change
Time needed: 20 to 45 minutes
System Restore is a fallback, not a file-specific repair. Consider it only when:
- The error began after a clearly identifiable installation or removal.
- A restore point from before that change exists.
- Office repair has not solved the problem.
Open Control Panel → Recovery → Open System Restore, select a suitable restore point, and review the affected programs before confirming. Back up current work first.
If the restore does not correct the Office installation, use the repair or reinstall path rather than repeatedly restoring the system.
Why this error happens
The likely causes are:
| Likely cause | What it means | Best response |
|---|---|---|
| Damaged Office installation | The DLL or its language component is missing | Repair Office |
| Incomplete upgrade | A newer Office setup left an older Access dependency unresolved | Repair the calling product, then remove conflicts |
| Mixed Office versions | Multiple installers disagree about files or components | Identify the required edition and reinstall cleanly |
| Access Runtime problem | A database uses a runtime with missing features | Repair or reinstall the exact runtime |
| Antivirus quarantine | Security software removed the file | Review quarantine, scan, then repair Office |
| Disk or filesystem damage | Files were lost or corrupted | Back up data, check disk health, repair Office |
| Missing dependency | The named DLL exists but another required module does not | Repair the complete Office installation |
The message does not prove that the file itself is absent. “The specified module could not be found” can refer to a dependency loaded by the named DLL.
Why copying msain900.dll to System32 fails
Copying a DLL into System32 is the wrong approach for this file for several reasons:
Windows 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 reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match- Access may search its own installation directory.
- The required language subdirectory may be different.
- The copied file may be a different build.
- The copied file may be the wrong architecture.
- Office installer records remain damaged.
- Related files may still be missing.
- A malicious or modified DLL can compromise the application.
A real Access troubleshooting report found that copying the file into System32, the Office directory, and a language directory did not resolve the problem. Repairing the owning Office installation addresses the entire component set instead of guessing at one file.
Frequently asked questions
Is msain900.dll a Windows file?
No. It is associated with Microsoft Office, particularly Office 2000-era components. It should not be treated like a protected Windows DLL.
Does Windows 11 support this file?
Windows 11 may run some older 32-bit Office software, but compatibility is not guaranteed. The file remains a legacy Office component, not a Windows 11 component. Repair the Office product that is requesting it.
Should I download msain900.dll?
No. There is no current Microsoft standalone download page for this DLL. Random DLL sites may provide malware, a mismatched build, the wrong architecture, or a file that does not include the required language resources. Use Office installation media, Microsoft’s repair options, or the correct Microsoft runtime package.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesCan I put it in System32?
Do not. The application may not search there, and putting a 32-bit Office file into a Windows system directory can create additional confusion.
Does regsvr32 fix it?
Usually not. regsvr32 applies to self-registering DLLs, and there is no evidence that this Office language component exposes the required registration entry point.
Can SFC restore it?
SFC and DISM repair protected Windows components. They are not the primary method for restoring an Office-owned file. Run them when broader Windows corruption is suspected, then repair Office.
Why does Office 2007 ask for an Office 2000 file?
A legacy Access component, language feature, runtime, or incomplete upgrade may still depend on the older file. A user report showing this behavior establishes that it can occur, but it does not establish one universal Office bug. Identify the executable and repair the installation that owns it.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Will Microsoft 365 Access Runtime replace it?
Not automatically. The current runtime is a separate modern package and is not a direct replacement for an Office 2000 DLL. Check the application’s required Access generation and architecture first.
What should I collect before contacting support?
Record:
- The exact error text
- The program that displays it
- Whether it occurs at startup, while opening a database, or during uninstall
- The full path of the affected executable
- Installed Office and Access Runtime entries
- Whether Office was recently upgraded, repaired, or removed
- Whether antivirus quarantined anything
- Whether the installation is under
Program Files (x86) - The results of Office repair, DISM, and SFC
That information points to the correct Office installation and prevents the most common mistake: treating an old application component as if it were a missing Windows system 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.
