dbexpmss.dll Is Missing: Restore the Delphi SQL Driver

Start with this diagnostic checklist

Before changing Windows, note:

• Which program shows the error? Record the executable name and installation folder.
• When does it happen? Does it appear when Windows starts, when opening a legacy business application, or when connecting to SQL Server?
• What is the exact message? “The specified module could not be found” can mean that a dependency is missing, not necessarily dbexpmss.dll.
• Is the application 32-bit or 64-bit? A historical dbexpmss.dll deployment is associated with 32-bit Delphi-era software. Verify the application and file rather than guessing.
• Was anything recently changed? Check for an antivirus quarantine, application reinstall, disk cleanup, migration to another PC, Windows update, or driver change.

dbexpmss.dll is a Borland dbExpress Microsoft SQL Server driver used by older Delphi and DataSnap-era applications. The safest repair is to restore it through the application’s original installer, repair option, backup, or software vendor.

Do not download a random copy and place it in C:WindowsSystem32 or C:WindowsSysWOW64. That can install the wrong build, introduce malware, or leave the application unable to find its other database components.

What dbexpmss.dll is

dbexpmss.dll is not a Windows component, Microsoft Visual C++ runtime, DirectX file, or general-purpose Microsoft SQL Server system DLL. It is historically identified as the Borland dbExpress MSSQL driver, associated with Borland’s DataSnap Direct Drivers and older Delphi applications.

dbExpress applications use database-specific driver DLLs. The driver is normally deployed with the application and loaded from the program’s own directory or a related private runtime folder. It is not normally registered globally as a Windows component.

The application may be an old:

• Delphi desktop program
• DataSnap client or server
• Accounting, inventory, manufacturing, or medical system
• Internal line-of-business tool
• SQL Server front end built by a third-party vendor

The name of the file does not identify the exact program that installed it. Start with the application named in the error dialog, the shortcut’s Target field, and the folder containing the program’s executable.

Current Delphi documentation uses different dbExpress names, including dbxmss.dll and dbxmss9.dll. Do not substitute either file for dbexpmss.dll unless the application vendor confirms that the application was built for that driver generation.

Fix 1: Repair the application that owns the file

This is the most likely and safest fix.

Find the owning application

1. Press Ctrl+Shift+Esc to open Task Manager.
2. Select Startup apps and look for the program if the error appears during sign-in.
3. If the error appears after clicking a shortcut, right-click that shortcut and select Properties.
4. On the Shortcut tab, inspect Target and Start in.
5. Open the target folder in File Explorer.
6. Look for the application executable and any bin, drivers, or database-related subfolder.

If the error appears in a service or scheduled task, do not delete or replace files yet. Ask the system administrator or software vendor which executable owns the service.

Use Windows’ repair option

1. Press Windows+I.
2. Select Apps, then Installed apps.
3. Search for the application name.
4. Select the three-dot menu beside it.
5. Choose Advanced options if available.
6. Select Repair.

Not every older desktop installer exposes this option. If Repair is unavailable, open the application’s original setup program and look for Repair, Modify, or Maintenance.

Restart Windows and open the application again. A successful repair usually restores the file beside the application and allows the program to reach its normal login or database connection screen.

If the error remains, uninstalling and reinstalling may be necessary. Before doing that, confirm that you have:

• The original installer or licensed deployment package
• The application’s configuration and database connection details
• Any required license key or activation information
• A backup of application data
• The vendor’s instructions for the supported SQL Server client components

Do not remove an old business application until you know how its data and configuration are stored.

Fix 2: Restore the file from trusted quarantine or backup

Antivirus software may remove a legacy DLL because its age, packing, or behavior resembles unwanted software. A quarantine event is not proof that the file is safe.

Check Microsoft Defender Protection History

1. Open Start and search for Windows Security.
2. Select Virus & threat protection.
3. Select Protection history.
4. Review detections around the time the application stopped working.
5. Open the relevant item and inspect its name, path, and detection details.

Restore the file only when all of these are true:

• You recognize the application.
• The file came from the application’s original licensed installation.
• The detection is understood and the software vendor confirms the file is legitimate.
• The application and its installer have not been tampered with.

If you restore it, place it back in the application’s original folder, not in a Windows system directory. Microsoft provides guidance for Protection History and restoring quarantined files.

If the detection is credible or the file came from an unknown source, do not restore it. Reinstall the application from clean original media instead.

Fix 3: Reinstall the complete application package

A common cause is copying only the main program executable to another computer. The application may also require its private dbExpress driver, configuration files, SQL client provider, and other runtime files.

Use the complete installer supplied by:

• The software vendor
• Your organization’s original deployment package
• Licensed Borland or Delphi product media
• A verified backup made from the original installation

Do not copy dbexpmss.dll from another unrelated computer merely because the filename matches. Two files with the same name may belong to different Delphi releases or builds. A mismatched file can produce an entry-point error, access violation, connection failure, or another database error after the initial missing-file message disappears.

After reinstalling:

1. Restart Windows.
2. Launch the application from its normal shortcut.
3. Confirm that the original executable is being used.
4. Test the normal workflow that previously failed.
5. If the program opens but cannot connect to SQL Server, treat that as a separate provider or configuration problem.

Fix 4: Check whether a dependency is missing

Windows may display “The specified module could not be found” when dbexpmss.dll exists but one of its dependencies does not.

Possible dependencies vary by application and historical build. The required SQL Server client, OLE DB provider, or related runtime must be identified from the application’s original deployment instructions. Do not assume that installing a current SQL Server package or Visual C++ Redistributable will provide this Borland driver.

Check the application directory:

1. Open the folder containing the application executable.
2. Confirm whether dbexpmss.dll is present.
3. Check whether the application has a separate bin, drivers, or runtime folder.
4. Compare the installed files with the original deployment package.
5. Read the vendor’s installation instructions for SQL Server client components.

Microsoft’s Visual C++ Redistributable documentation explains what those packages provide. They supply Microsoft C and C++ runtime libraries; they do not supply dbexpmss.dll.

If a trusted dependency checker identifies a missing component, obtain it from the application vendor or Microsoft where applicable. Avoid downloading individual dependency DLLs from file-index sites.

Fix 5: Verify 32-bit and 64-bit compatibility

Older Delphi applications commonly use 32-bit binaries. A 32-bit application needs a compatible 32-bit driver and compatible database components. Installing a 64-bit file with the same name will not make a 32-bit application work.

To check the application architecture:

1. Start the application if possible.
2. Open Task Manager with Ctrl+Shift+Esc.
3. Select Details.
4. Right-click a column heading and choose Select columns.
5. Enable Platform if that column is available.
6. Check whether the application is listed as 32-bit or 64-bit.

You can also inspect the file’s Properties, although ordinary Properties pages may not show architecture. A trusted PE inspection tool can identify whether the DLL is Win32 or x64. Use the original file or a verified backup for this check.

Do not replace an old dbexpmss.dll with a similarly named modern dbxmss.dll or dbxmss9.dll. Matching the filename prefix is not enough. The Delphi generation, driver interface, application architecture, and SQL Server provider must all be compatible.

Fix 6: Do not register this DLL with regsvr32

regsvr32 is intended for COM, OLE, and ActiveX DLLs that provide registration entry points such as DllRegisterServer. A dbExpress database driver is normally loaded by the application’s dbExpress loader instead.

Running this command is not a standard repair:

regsvr32 dbexpmss.dll

It may produce an error stating that DllRegisterServer was not found. That does not prove the file is damaged. It usually means the DLL was not designed to be registered that way.

Use the application installer and its private deployment folder instead. Microsoft describes the purpose and limitations of regsvr32 in its documentation.

Fix 7: Check recent hardware or driver changes

Device Manager does not normally install or repair dbexpmss.dll. This is an application database driver, not a Windows hardware driver. Do not expect a display, audio, printer, chipset, or network driver update to recreate it.

However, if the error began immediately after a hardware-driver change and other programs also fail, inspect the recent driver state:

1. Press Windows+X.
2. Select Device Manager.
3. Expand the category related to the recent change.
4. Right-click the device and select Properties.
5. Open the Driver tab.
6. Use Roll Back Driver if Windows offers it and the problem began after that update.
7. Otherwise select Update Driver and follow the manufacturer-approved installation process.
8. Restart Windows and retest the application.

Do not remove unrelated devices simply because the DLL error mentions a “driver.” The file’s driver designation refers to database connectivity.

Manually checking every device for stale packages can mean hunting through many driver versions and guessing which change matters. Outbyte Driver Updater can scan for outdated drivers and show what it identifies; its free scan shows the findings, while driver installation through the full version is optional. Reinstalling the application remains the definitive fix when that application owns dbexpmss.dll.

Fix 8: Repair broader Windows component corruption

Windows system repair tools normally will not recreate a third-party Borland DLL. Use them when Windows itself has other damaged components, update failures, or system-wide errors.

Open an elevated Command Prompt:

1. Open Start.
2. Type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Select Yes at the User Account Control prompt.
6. Run this command first:

DISM /Online /Cleanup-Image /RestoreHealth

Wait for it to finish. Then run:

sfc /scannow

Restart Windows after both commands complete. Microsoft documents this sequence in its System File Checker guidance.

If SFC reports that it repaired damaged files, test the application again. If both commands complete without changing the error, return to the application installer and dependency checks. Repeating SFC and DISM will not normally obtain a missing Borland driver.

Manually interpreting repeated repair output can be time-consuming, especially when Windows has several unrelated component problems. Outbyte PC Repair can scan and show reported Windows issues; its free scan identifies findings, while repair through the full version is optional and is not required for this application-specific fix.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Fix 9: Use System Restore after a recent system change

If the error started immediately after a software installation, Windows change, or driver update, System Restore may return system settings and installed components to an earlier restore point. It does not replace a proper application reinstall and should not be treated as a source for an unverified DLL.

1. Press Windows+R.
2. Type rstrui.exe.
3. Press Enter.
4. Select Next.
5. Choose a restore point dated before the problem began.
6. Select Scan for affected programs if available.
7. Review the changes.
8. Select Next, then Finish.
9. Allow Windows to restart.

Microsoft explains this process in its System Restore documentation.

If no suitable restore point exists, use the application’s original installer or contact the software vendor.

Why random DLL downloads are unsafe

A search result promising a free dbexpmss.dll download does not establish that the file is authentic or compatible. A downloaded DLL may be:

• Modified or infected
• From a different Delphi release
• The wrong architecture
• Missing required dependencies
• Intended for a different application
• Distributed without the application’s licensed runtime context

Even a file that removes the first error may cause a later database failure. It may also create a false sense that the application has been repaired.

The safe sources are the owning application’s original installer, a verified organizational backup, the original vendor, or licensed Borland/Delphi media. Do not place the file in System32 or SysWOW64, and do not use a system-wide copy to make one application work.

Advanced diagnosis when the error remains

If the file is present and the application was reinstalled but still fails:

1. Capture the full error dialog.
2. Record the name of the calling executable.
3. Check the application folder for duplicate copies of the driver.
4. Confirm that the shortcut points to the intended installation.
5. Review Event Viewer:
6. Press Windows+R.
7. Type eventvwr.msc.
8. Open Windows Logs, then Application.
9. Look for an error at the time of the failed launch.
10. Check whether the application works for another Windows user.
11. If it works under another profile, inspect permissions, controlled-folder access, and per-user configuration files.
12. Ask the original vendor which SQL Server client provider and driver build the application requires.

If a different copy of the application works on another PC, compare the complete deployment folders and installed prerequisites rather than copying only one DLL.

Historical public listings may show a version, file size, or copyright year for dbexpmss.dll, but those details are not a reliable universal specification. Verify the exact binary supplied with your application.

Frequently asked questions

Is dbexpmss.dll part of Windows?

No. It is a historical Borland dbExpress Microsoft SQL Server driver associated with Delphi and DataSnap applications.

Can Microsoft Visual C++ Redistributable restore it?

No. Visual C++ Redistributable packages provide Microsoft runtime libraries. They do not contain this Borland driver.

Should I copy it to System32?

No. Restore it to the owning application’s original folder using trusted installation media or backup.

Should I run regsvr32 dbexpmss.dll?

No. A dbExpress driver is normally loaded by the application, not registered as a COM or ActiveX component.

Is dbexpmss.dll 32-bit or 64-bit?

Historical public information identifies the file with older Win32 deployments, but verify the exact file and application. Do not assume that every similarly named driver has the same architecture.

Which Delphi version installed it?

The exact Delphi release varies. Historical evidence connects the driver with older Delphi-era deployments, and availability could depend on the Delphi edition and license. The original application installer is the reliable source.

Why does Windows say that the specified module cannot be found when the file exists?

The message may refer to a dependency of dbexpmss.dll, such as an application-specific SQL Server or OLE DB component. Check the complete deployment package rather than replacing the visible file repeatedly.

What is the final fix if none of these steps work?

Identify the calling executable, preserve the error details, and obtain the complete supported installer from the original software vendor. A modern, unrelated dbExpress driver or a random DLL download is not a safe substitute.

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.