Recommended Free Tools
mso97rt.dll is a legacy 32-bit Microsoft Office/VBA runtime component, not a normal Windows system file. The safest fix is to identify the old application requesting it, then repair or reinstall that application’s original Access, Office, Visual Basic, or runtime component.
What this file actually does
mso97rt.dll belongs to the older Microsoft Office 97 and Visual Basic software family. It is most strongly associated with Microsoft Access 97 runtime mode and applications created with the Office 97 Developer Edition Tools. Some Visual Basic 5/6 installations and older Excel, Query, and VBA components may also require it.
As an Amazon Associate I earn from qualifying purchases.
It does not normally ship with Windows 10 or Windows 11. You should not treat it as a missing file from C:WindowsSystem32, and Windows Update is not expected to restore it.
A 32-bit legacy application may historically look for the file under:
#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
C:Program FilesCommon FilesMicrosoft SharedVBA
On 64-bit Windows, the equivalent location may be:
C:Program Files (x86)Common FilesMicrosoft SharedVBA
The installer decides the correct location. Do not copy the file into System32 or `SysWOW64 merely because a website recommends it.
Causes and symptoms
| What you see | Most likely cause | Correct direction |
|---|---|---|
Can't find the dynamic-link library (DLL) Mso97rt |
Access 97 was started with /runtime without its runtime component |
Check the shortcut and remove /runtime, or reinstall the original runtime |
A required .DLL file, MSO97RT.DLL, was not found |
Visual Basic or an older Office component is damaged | Repair or reinstall the original product |
Unexpected Error; Quitting when starting Visual Basic |
Visual Basic 5/6 files are missing or incompatible | Run the original Visual Basic setup again |
Cannot execute MSQRY32.EXE |
Excel 7, Query, and Visual Basic components conflict | Reinstall the affected legacy components in a compatible order |
| The error began after antivirus activity | The file may have been quarantined | Check quarantine before reinstalling |
| The error appears after replacing Office | A shared legacy component was removed or overwritten | Restore the original application’s installer |
| The error appears at every startup | A stale shortcut, startup entry, or old application remains | Find and remove or repair the program that launches |
Microsoft’s historical Access documentation specifically connects Mso97rt.dll with Access 97 runtime mode and the Office 97 Developer Edition Tools. The exact message can state that the /runtime switch cannot be used unless those tools are installed.
Fix 1: Check the program and shortcut first
Before downloading or replacing anything, find which program is asking for the DLL.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →- Write down the full error message and the application name shown in its title bar.
- If the error appears after clicking a shortcut, right-click that shortcut.
- Select Properties.
- On the Shortcut tab, inspect Target.
- Look for a switch named
/runtime. - Check whether the target points to Access 97 or an old custom Access application.
- Also check the Start in field for the application’s original installation folder.
- Select Cancel without changing anything unless this is clearly the Access 97 case described below.
If the message appears during startup rather than after opening a program, check these locations:
- Settings > Apps > Startup
- The Startup folder opened with
Win + R, followed byshell:startup - Task Scheduler, under Task Scheduler Library
- Shortcuts in the Start menu
Do not delete an entry until you know which application owns it. A missing DLL message at boot often comes from an old application that was partially uninstalled.
Fix 2: Correct the Access 97 /runtime shortcut
This is the most important specific fix for mso97rt.dll.
If full Microsoft Access 97 is installed but the shortcut unnecessarily starts it in runtime mode, remove the switch:
- Right-click the Access shortcut.
- Select Properties.
- Select the Shortcut tab.
- Click inside Target.
- Remove
/runtimefrom the end of the command. - Leave the quotation marks around the executable path intact.
- Select Apply, then OK.
- Start Access from the edited shortcut.
For example, a target may contain an executable path followed by /runtime. Remove only that switch, not the path to the executable.
If Access opens normally afterward, the shortcut was wrong and the DLL was not necessarily missing from the full Access installation.
If the application genuinely needs runtime mode, do not remove the switch permanently. Reinstall the original Access runtime or the Office 97 Developer Edition Tools from legitimate installation media instead.
Fix 3: Repair the original Access or custom application
Custom Access applications created with the Office 97 Developer Edition Tools often deployed their own matching runtime files. A generic DLL downloaded from the internet is not a reliable substitute.
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 the application’s original setup media or installer:
- Close the affected program.
- Open Control Panel.
- Select Programs > Programs and Features.
- Select the old Access runtime, Office component, or custom application.
- Choose Change, Repair, or Modify, if available.
- Follow the setup wizard.
- Restart Windows if setup requests it.
- Test the original application again.
If no repair option exists, run the original Setup.exe from the installation disc or backed-up installer. Choose a reinstall or maintenance option when offered.
If the application was deployed by an employer or software vendor, ask for its original deployment package rather than sourcing an individual DLL. The installer may need to place several matching Office and VBA files together.
Fix 4: Repair Visual Basic 5 or Visual Basic 6
Microsoft’s archived troubleshooting guidance identifies MSO97RT.DLL among files that older Visual Basic installations may need. It also identifies the Visual Basic installation CD’s OSSystem directory as a historical source.
If the error began after installing or repairing Visual Basic:
- Insert the original Visual Basic installation disc, if available.
- Open the disc in File Explorer.
- Run the main setup program.
- Choose Repair, Reinstall, or the equivalent maintenance option.
- Allow setup to restore its supporting files.
- Restart Windows.
- Open Visual Basic again.
If setup reports that another Office or Visual Basic version is already installed, do not force files into the VBA directory manually. Multiple Office generations can share components and overwrite each other with incompatible versions.
For a damaged installation with no repair choice:
- Back up your Visual Basic projects and custom templates.
- Uninstall the affected Visual Basic product from Programs and Features.
- Restart Windows.
- Reinstall it from the original media.
- Apply only updates intended for that product.
- Test the application that originally reported the error.
Fix 5: Resolve an Office, Excel, or Query version conflict
Older Microsoft products could replace shared components when installed in a different order. Microsoft documented cases involving Excel 7, MS Query, Visual Basic 5, and MSO97RT.DLL.
If the problem started after installing Visual Basic, Excel, Office, or a Query component:
- Note which legacy products are installed.
- Open Control Panel > Programs and Features.
- Record the entries before removing anything.
- Uninstall the component that was installed immediately before the error began.
- Restart Windows.
- Reinstall the affected product from its original media.
- Test Excel, Query, and the original application separately.
Do not assume that the newest-looking legacy component is compatible with every other installed Office product. If the software belongs to a business or line-of-business application, follow that application’s deployment instructions.
Fix 6: Check antivirus quarantine
Security software may quarantine an old DLL because legacy files can have unusual age, metadata, or behavior. A quarantine event is not proof that the file is safe to restore.
- Open your antivirus or Windows Security application.
- Open Protection history, Quarantine, or Detection history.
- Search for
mso97rt.dll. - Check the file path and the application that installed it.
- Restore it only when the path belongs to a known, legitimate installation and you trust the original installer.
- If you cannot verify the source, leave it quarantined.
- Reinstall the original Access, Office, Visual Basic, or application package instead.
- Run a full system scan.
After reinstalling, test the application before changing any security exclusions. Do not create a permanent exclusion for a DLL obtained from an unknown source.
Fix 7: Check the 32-bit installation path
mso97rt.dll is a legacy 32-bit component. A 32-bit application on 64-bit Windows needs its 32-bit dependencies, but that does not mean the file belongs in the Windows system directories.
Free tools Windows power users keep installed
One-click scans. No signup required.
Check the application’s own installation folder and the shared VBA folders:
C:Program FilesCommon FilesMicrosoft SharedVBA
C:Program Files (x86)Common FilesMicrosoft SharedVBA
The correct folder depends on the installer and the application. If the file exists in one of these locations but the program still reports it as missing, the application may be using an incorrect shortcut, a broken installation path, or another missing dependency.
A 64-bit copy of this file is not the expected solution. Claims that an arbitrary 64-bit mso97rt.dll is interchangeable with the legacy 32-bit component should be treated skeptically.
Fix 8: Use SFC and DISM only for wider Windows corruption
System File Checker and DISM repair protected Windows components. They generally cannot recreate an Office 97 DLL that was never part of the Windows component store.
Use them when other Windows features are also failing:
- Open Start.
- Type
Command Prompt. - Right-click Command Prompt.
- Select Run as administrator.
- Run:
DISM.exe /Online /Cleanup-Image /RestoreHealth
- Wait for it to complete.
- Then run:
sfc /scannow
- Restart Windows.
- Test the affected application.
Microsoft documents this DISM-then-SFC sequence for repairing the Windows image and protected system files. If the commands report that Windows was repaired but mso97rt.dll is still missing, reinstall the legacy application. Repeating SFC will not create a file supplied by an old Office installer.
Manually checking Windows components and interpreting repeated repair output takes time, especially when the missing file is actually owned by an old application. Outbyte PC Repair can scan for problems and show what needs attention; its full version performs the repair, but reinstalling the original program remains the definitive fix for an application-specific DLL.
Fix 9: Update drivers only when the application also has hardware errors
A graphics, printer, database, or peripheral driver does not normally supply mso97rt.dll. Driver work is therefore a secondary step, appropriate only when the old application also fails while accessing a device or Windows reports separate driver problems.
Outdated 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 matchWindows 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 reinstallTo check manually:
- Right-click Start.
- Select Device Manager.
- Expand the relevant category, such as Display adapters, Printers, or Sound, video and game controllers.
- Right-click the affected device.
- Select Update driver.
- Choose Search automatically for drivers.
- Restart Windows if a driver is installed.
- Test the application again.
Do not expect a driver update to restore an Office or Visual Basic runtime file. Outbyte Driver Updater can scan for outdated drivers and identify which versions need attention; the full version performs the installation, while the original application’s installer remains the correct source for mso97rt.dll.
Why downloading the DLL separately is unsafe
Avoid DLL download repositories and copied files from forums, file-sharing pages, or another computer. A replacement may have the wrong version, wrong architecture, altered contents, or missing dependencies. It may also leave the underlying broken installation unchanged.
There is no current Microsoft redistributable specifically named mso97rt.dll. The safe sources are:
- The original Access runtime installer
- Office 97 Developer Edition Tools media
- The original Visual Basic 5/6 media
- The installer for the custom Access application
- A trusted backup of that application’s complete installation package
Microsoft’s current Microsoft 365 Access Runtime is a different product. Installing it is not a guaranteed replacement for the Office 97 component.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsDoes regsvr32 fix mso97rt.dll?
Usually not. regsvr32 is intended for DLLs that provide registration entry points such as DllRegisterServer; it is not a general missing-DLL repair command.
Running:
regsvr32 mso97rt.dll
may produce an error stating that the module loaded but the DllRegisterServer entry point was not found. That message does not necessarily mean the file is corrupt. It usually means registration is not the appropriate operation.
Microsoft documents the command’s purpose and syntax in its regsvr32 reference. Reinstall the owning application instead.
Frequently asked questions
Is mso97rt.dll part of Windows 11 or Windows 10?
No. It is a legacy 32-bit Microsoft Office/VBA runtime component and is not a standard Windows system file.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Is it only used by Access?
No. Access 97 runtime mode is the clearest documented association, but older Office components and Visual Basic 5/6 may also require it.
Can I copy it into System32?
Do not. The correct location is determined by the original installer, and a 32-bit application does not become repaired by placing a random DLL in a Windows system folder.
Should I install the current Access Runtime?
Not as a direct replacement. The current Access Runtime is a different product intended for current supported Office releases.
What if the file exists but the error remains?
Inspect the shortcut for /runtime, confirm that the application is using the correct installation, and repair the complete product. Another dependency may be missing even though the visible error names mso97rt.dll.
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 matchWhat if the original media is unavailable?
Look for a legitimate backup, the application’s original deployment package, or the software vendor’s support channel. If the old application is no longer needed, remove its stale startup entry instead of downloading the DLL.
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.
