borlndmm.dll Missing: Trace the Right Legacy App to Repair

borlndmm.dll is the Borland Memory Manager runtime used by some older Delphi and C++Builder applications, and its absence can stop a program before it opens. The safest fix is to identify the application named in the error and repair or reinstall that application, rather than downloading borlndmm.dll from a random DLL site.

What this file actually does

borlndmm.dll is an application runtime file associated with Borland Delphi, Borland C++Builder, and later Embarcadero development tools. Older software may use it to provide shared memory management between Delphi modules or between an application and a DLL.

As an Amazon Associate I earn from qualifying purchases.

It is not a Windows system component. It is also not part of the Microsoft Visual C++ Redistributable.

An application commonly needs this file when it was built with Delphi’s ShareMem support or with a dynamic Borland runtime. The original application installer should normally place the matching copy beside the program executable.

Older metadata may identify the developer as Inprise Corporation. That historical label does not mean the file belongs to Windows or that a single universal version works with every Delphi or C++Builder application.

Do not assume that every file named borlndmm.dll is interchangeable. Different development-tool generations can supply incompatible copies. Exact versions, sizes, timestamps, and other file details vary by application.

Causes and symptoms at a glance

What you see	Most likely cause	Best next step
“The program can’t start because borlndmm.dll is missing”	The application was installed or copied without its runtime	Repair or reinstall the affected application
“Can’t find the BORLNDMM.DLL dll”	The executable cannot find its application-local dependency	Restore the file from the original installer
The error appeared after antivirus activity	Windows Security or another antivirus quarantined the file	Check quarantine, then repair the application
The file exists beside the executable but loading still fails	Wrong build, damaged file, or another dependency is missing	Reinstall and inspect the complete error
The message says “specified module could not be found”	A dependency of borlndmm.dll, rather than the file itself, may be absent	Repair the complete application installation
An access violation occurs inside borlndmm.dll	A memory-manager mismatch, incompatible component, profile problem, or application defect	Treat it as an application compatibility problem
Several Delphi or C++Builder versions are installed	A copy from one toolchain may be mixed with an application from another	Use the copy supplied with the affected program
Windows is 64-bit and the app is old	The application may be 32-bit and need a 32-bit runtime	Match the DLL to the application, not just to Windows

Fix borlndmm.dll errors in order

1. Identify the program producing the error

The DLL name alone cannot identify the correct replacement. Start with the complete error and the executable that triggers it.

1. Write down the exact wording of the message.
2. Note whether it appears when opening a named program, game, installer, shortcut, or file association.
3. Right-click the shortcut and select Properties.
4. On the Shortcut tab, read the path in Target.
5. Open that folder and note the executable name.
6. If the message appears during installation, identify the installer and the product it is installing.
7. If several programs fail, record each executable separately.

If the error appears immediately after opening a shortcut, the affected program is usually the application represented by that shortcut. If it appears during an installation, repair the product being installed rather than copying a DLL into Windows.

Do not begin by searching the entire drive for a file named borlndmm.dll. A copy belonging to a different application or development environment may be unsuitable.

2. Repair or reinstall the affected application

This is the most reliable fix because it restores the executable, its matching runtime, and any companion files together.

Use Windows’ repair option

1. Press Windows + I to open Settings.
2. Select Apps.
3. Select Installed apps on Windows 11, or Apps & features on some Windows 10 builds.
4. Search for the application named in the error.
5. Select the three-dot menu beside it.
6. Choose Advanced options, if available.
7. Select Repair.
8. Start the program again.

If there is no Repair button, or the error remains:

1. Return to the application’s entry in Installed apps.
2. Select Uninstall.
3. Restart Windows if requested.
4. Download or obtain the original installer from the application’s publisher or your organization’s software archive.
5. Install the program again.
6. Launch it from its newly installed shortcut.

For a game, use the launcher’s file verification or repair function instead of manually replacing the DLL. The exact menu name varies by launcher, but it is usually near the game’s installation or management options.

Run the installer as an administrator only when necessary:

1. Right-click the trusted original installer.
2. Select Properties.
3. Open the Compatibility tab.
4. Select Run this program as an administrator.
5. Select Apply, then OK.
6. Right-click the installer again and select Run as administrator.

A successful repair means the program starts without the missing-file message. If the installer reports another missing DLL, record that name rather than replacing several files from unrelated sources.

3. Check antivirus quarantine

Security software can remove or quarantine an application file after an update, false detection, or incomplete installation.

Check Windows Security

1. Open Start and search for Windows Security.
2. Open it.
3. Select Virus & threat protection.
4. Select Protection history.
5. Look for an event involving the affected application’s installation folder.
6. Expand the event and review the file path and detection details.

Restore a quarantined file only when all of the following are true:

• You recognize the application.
• The application came from a trusted publisher or known internal source.
• The file path belongs to that application.
• You can repair or reinstall the application immediately afterward.

Do not disable antivirus protection permanently to make the error disappear. The safer process is to repair the application from its original installer. If the file is restored and immediately quarantined again, stop and contact the application’s publisher or your administrator rather than forcing the file back into place.

After restoring or reinstalling:

1. Open the application’s installation folder.
2. Confirm that borlndmm.dll is beside the affected executable when the application uses application-local deployment.
3. Start the application.
4. If the error returns, use the installer again because the restored copy may not match the executable.

There is no reliable basis for assuming that borlndmm.dll is inherently malware. There is also no basis for trusting an arbitrary replacement downloaded from an unknown source.

4. Restore the file from the original application package

Some portable or internally developed programs do not register in Windows’ installed-app list. In that case, obtain the file from the program’s original distribution.

Acceptable sources include:

• The application’s original installer.
• A verified backup of the same application release.
• The publisher’s official installer.
• An internal software repository maintained by the application’s developer or administrator.
• The matching Delphi or C++Builder deployment package for a program you built.

For an application-local DLL, the normal location is the folder containing the affected executable. Copying it to C:WindowsSystem32 or C:WindowsSysWOW64 is not a general repair and can create conflicts with other applications.

If you control the source code, deploy the exact runtime files required by that build. Applications using dynamic runtime packages may also require associated .bpl files. Embarcadero’s deployment documentation describes distributing required runtime files with the application.

Do not rename another DLL to borlndmm.dll. A renamed file does not provide the same exports, memory manager, or compatibility behavior.

5. Match the application architecture

A 64-bit version of Windows can run many 32-bit applications. That does not make the application a 64-bit program.

Use this rule:

• A 32-bit application needs the matching 32-bit dependency.
• A 64-bit application needs the matching 64-bit dependency.
• The correct copy is the one supplied for that application build.

The operating system’s architecture alone does not tell you which borlndmm.dll is required. Do not copy both variants into Windows directories in an attempt to make the loader choose correctly.

If you have the application’s original installer, use it instead of trying to identify the architecture manually. If you built the application, check the project’s target platform and deployment settings, then rebuild or redeploy the matching runtime.

If the file is beside the executable but Windows reports that it cannot load, possible causes include:

• The DLL is for the wrong architecture.
• The DLL belongs to another Delphi or C++Builder generation.
• The file is damaged.
• Another dependency is missing.
• The executable and runtime use incompatible memory-management assumptions.

Remove a misplaced copy only after confirming that you have a trusted installer or a verified replacement. Then reinstall the application so the correct files are restored as a set.

6. Reinstall the complete application, not just the DLL

A missing borlndmm.dll may indicate an incomplete deployment. This can happen when someone copies only an executable from a development computer, when an installer is interrupted, or when a cleanup tool deletes application files.

A complete reinstall works better than a DLL-only replacement because it can restore:

• The executable.
• borlndmm.dll.
• Other Borland or application runtime files.
• Configuration files.
• Required runtime packages.
• Application registry entries and shortcuts.

Before uninstalling, back up saved data and settings if the program stores them inside its installation folder. Then uninstall, restart Windows, and reinstall from the original source.

If the application is old and no longer has a working installer, ask its publisher, system administrator, or developer for the matching distribution package. Avoid assembling a runtime from files found on unrelated computers.

7. Investigate a file that exists but still fails

A present file does not prove that the loader can use it.

If the error says the “specified module could not be found,” Windows may be unable to find a dependency required by borlndmm.dll or by the main executable. The named file can exist while another required module is absent.

Use this sequence:

1. Confirm that the file is in the application’s expected folder.
2. Check the exact spelling and extension.
3. Run the application’s original repair or reinstall process.
4. Record any new DLL name shown by the error.
5. Check whether the application was built for the current architecture.
6. Remove only unauthorized or misplaced copies from the application folder.
7. Reinstall the affected program.

Do not use regsvr32 as a general DLL repair command. Microsoft documents regsvr32 for DLLs that expose registration entry points such as DllRegisterServer, typically COM or ActiveX components. borlndmm.dll is a memory-manager runtime, not a documented COM component.

Running a command such as this will generally not fix the problem:

regsvr32 borlndmm.dll

It may instead produce an error about a missing entry point or an invalid module. Registration is not the same as making an application-local dependency available.

8. Handle access violations separately

An access violation mentioning borlndmm.dll is not the same as a missing-file error. It can involve:

• A Delphi memory-manager mismatch.
• An incompatible component or package.
• A damaged application installation.
• A damaged user profile.
• An application defect.
• Incorrect handling of memory across module boundaries.

If the program starts and then crashes, do not assume that copying a new DLL will help. First:

1. Repair or reinstall the application.
2. Disable recently added plug-ins or components.
3. Test the program with a new Windows user profile if the failure is limited to one profile.
4. Check the application’s own logs.
5. Contact the publisher or developer with the exact exception text.

If you compiled the program, review whether modules allocate memory in one runtime and release it in another. A shared memory manager may be required when memory crosses Delphi module boundaries. Change runtime or package settings only when they match the project’s deployment design.

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

Windows repair tools: when they help and when they do not

borlndmm.dll is not a protected Windows system file, so System File Checker and DISM will not normally recreate the application-local runtime. Use them when Windows has other corruption symptoms, such as broken built-in applications, damaged system components, or repeated servicing failures.

Run DISM, then SFC

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

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for it to finish.
2. In the same window, run:

sfc /scannow

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

A successful DISM or SFC operation repairs Windows components or protected system files. It does not prove that the correct borlndmm.dll was restored. If the application still reports the DLL error, return to its original installer.

Manually hunting through Windows components and repeating SFC or DISM without knowing what changed can be time-consuming. Outbyte PC Repair can scan for system issues and show what it identifies; repairs are performed by the full version. It is optional, and reinstalling the application remains the definitive fix when this DLL belongs to that application.

When System Restore is reasonable

Use System Restore only as a last-resort recovery option when:

• The file disappeared after a known system change.
• No valid application installer is available.
• A restore point from before the change exists.
• You understand that applications, drivers, and settings installed after that point may be affected.

To open it:

1. Press Windows + R.
2. Type rstrui.exe.
3. Press Enter.
4. Select Next.
5. Choose a restore point from before the problem.
6. Select Scan for affected programs.
7. Review the results.
8. Select Finish if the consequences are acceptable.

System Restore is not a substitute for obtaining the correct application package, and it is unlikely to help when only one legacy application is missing its private runtime.

Drivers, Windows Features, and Visual C++

Do not install Visual C++ automatically

borlndmm.dll is generally unrelated to the Microsoft Visual C++ Redistributable. Installing or repairing Visual C++ may help only if the affected application separately reports a Visual C++ runtime dependency.

Do not replace the Borland runtime with a Visual C++ file, and do not treat a Visual C++ installation as the primary solution.

Update a driver only for an independent driver error

Driver repair is not a default fix for a missing Borland runtime. Consider it only if the same application also reports graphics, audio, input, or hardware-driver failures.

To check a device:

1. Right-click Start.
2. Select Device Manager.
3. Expand the relevant category, such as Display adapters or Sound, video and game controllers.
4. Right-click the device.
5. Select Properties.
6. Open the Driver tab.
7. Note the provider and status.
8. Use Update Driver only when a suitable driver is available from Windows or the hardware manufacturer.

Guessing which of many drivers is stale can waste time when the real issue is an application-local DLL. Outbyte Driver Updater can scan for driver issues and identify available updates; the full version performs the driver installation. It is optional and does not replace reinstalling the application that owns borlndmm.dll.

Check Windows Features only when the application requires one

Legacy programs may independently require an optional Windows component, but borlndmm.dll itself does not establish that requirement.

To review optional features:

1. Open Settings.
2. Select Apps.
3. Select Optional features.
4. Select More Windows features or Windows features, depending on the Windows version.
5. Review the currently enabled features.
6. Enable a feature only when the application’s documentation specifically requires it.
7. Restart Windows if prompted.

Do not enable random legacy features as a substitute for restoring the application runtime.

Safe-source rules

Avoid DLL-index websites and unofficial file mirrors. A downloaded replacement can contain malware, be the wrong architecture, belong to another compiler generation, or fail to fix the missing companion dependency.

The safe sources are:

• The affected application’s original installer.
• The publisher’s official download or support channel.
• A verified organizational software repository.
• A matching deployment package from the developer of an application you built.
• A trusted backup of the same application release.

Keep the replacement beside the affected executable when the application’s deployment design calls for an application-local DLL. Do not place an unknown copy in System32 or SysWOW64.

FAQ

Is borlndmm.dll a Windows file?

No. It is a Borland Memory Manager runtime associated with older Delphi and C++Builder applications.

Is it part of Visual C++?

Generally no. Visual C++ Redistributables and Borland runtimes serve different development ecosystems.

Should I download borlndmm.dll separately?

Usually no. Repair or reinstall the application that reports the error, or obtain the matching file from its original distribution.

Where should a legitimate copy go?

Usually in the same folder as the affected application’s executable, when that is how the application was packaged. Do not copy it into a Windows system folder without authoritative instructions from the application’s developer.

Does 64-bit Windows require a 64-bit copy?

Not necessarily. A 64-bit Windows installation can run a 32-bit application, which needs its matching 32-bit dependency. Match the file to the application build.

Should I run regsvr32?

No, not for a normal missing borlndmm.dll error. It is not documented as a COM or ActiveX registration DLL.

What if antivirus quarantined it?

Check the quarantine history. Restore it only when the application and source are trusted, then repair or reinstall the application so the file comes from a verified package.

What if the file exists but the error continues?

The file may be the wrong build, damaged, or dependent on another missing module. Reinstall the application and capture the complete error text.

Are SFC and DISM the solution?

Usually not. They repair Windows components, while borlndmm.dll is an application runtime. Use them when other Windows corruption symptoms exist.

What should I provide when asking for further help?

Include the exact error, affected executable, application installation source, Windows version, file location, whether the program is 32-bit, and whether the failure is a missing-file message or an access violation.

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.