ldap60.dll Missing in Thunderbird: Safe Repair Steps for Windows

“The program can’t start because ldap60.dll is missing from your computer.” You may also see “ldap60.dll was not found,” “The code execution cannot proceed,” “bad image,” or an ordinal error when Thunderbird starts.

ldap60.dll is a Mozilla LDAP library historically bundled with some Thunderbird Windows builds. It is an application file, not a Windows system DLL. The safest repair is to reinstall the correct Thunderbird build over the existing installation, not to download a loose DLL or copy it into System32.

As an Amazon Associate I earn from qualifying purchases.

Which fix applies to you

Use this order:

• The error appeared after a Thunderbird update or interrupted installation: reinstall Thunderbird from its official installer.
• The file exists but you see “bad image,” an ordinal error, or an entry-point error: the DLL is probably damaged or from a different Thunderbird version. Reinstall the complete matching build.
• Windows Security removed the file: check Protection history before restoring anything.
• The installer seems to have done nothing: check whether the shortcut opens an older Thunderbird folder.
• Other Windows programs also fail: repair Windows components with DISM and SFC.
• Thunderbird files are repaired but startup still fails: test with a new profile without deleting the original.
• The error names another DLL: troubleshoot that named dependency instead. xul.dll, mozglue.dll, nss3.dll, VCRUNTIME140.dll, and Universal CRT files are different problems.

What ldap60.dll is and where it belongs

Mozilla’s LDAP code uses libraries including ldap60, ldif60, and prldap60. Mozilla crash and source records identify ldap60.dll as a module used by Thunderbird, particularly in historical Windows builds.

It is not part of Windows. Microsoft’s own LDAP client library is named Wldap32.dll, which is unrelated. Do not rename one file to the other, and do not copy ldap60.dll into either of these folders:

C:WindowsSystem32
C:WindowsSysWOW64

When a Thunderbird build requires this file, it belongs in the Thunderbird program directory alongside thunderbird.exe. Common installation locations are:

C:Program FilesMozilla Thunderbird
C:Program Files (x86)Mozilla Thunderbird

The historical versions commonly indexed for this file are 32-bit releases associated with older Thunderbird versions. That does not mean every Thunderbird release contains the same DLL. Modern Thunderbird also has 64-bit Windows builds, so the application architecture and all bundled libraries must match.

Fix 1: Reinstall the correct Thunderbird build

This is the most likely fix for a missing, damaged, or mismatched ldap60.dll.

1. Close Thunderbird completely

1. Save any work and close Thunderbird.
2. Press Ctrl + Shift + Esc to open Task Manager.
3. Select Processes.
4. Look for thunderbird.exe.
5. If it remains, select it and choose End task.

Do not replace the DLL while Thunderbird is running.

2. Back up the Thunderbird profile

Your mail, passwords, accounts, and settings are stored separately from the program files. A normal reinstall should not remove the profile, but the profile is not a backup.

Before reinstalling:

1. Press Windows + R.
2. Enter:

%APPDATA%Thunderbird

1. Press Enter.
2. Copy the Thunderbird folder to an external drive or another safe location.

If you use local message storage outside the normal profile, back up that location too.

3. Download the matching installer

Use the official Thunderbird download page and choose the build matching your Windows installation:

• Windows 64-bit for a 64-bit Thunderbird installation
• Windows 32-bit for a 32-bit installation
• The appropriate legacy build if the computer requires an older Windows-compatible release

If Thunderbird still opens far enough to show its menu, check Help > About Thunderbird before closing it. If it will not start, check the existing shortcut or installation folder rather than guessing.

Do not copy ldap60.dll from another computer. Even if the filename matches, the DLL may belong to another Thunderbird release or architecture.

4. Install over the existing program

1. Run the official Thunderbird installer.
2. Choose the normal installation, or use Custom Installation if you need to select the destination.
3. Install to the existing Thunderbird program directory.
4. Start Thunderbird.

A successful repair normally produces a clean startup without the ldap60.dll message. The DLL, when required by that build, should now be beside thunderbird.exe.

If Thunderbird opens a setup screen or appears to have lost your accounts, do not create a replacement profile yet. Close it and continue to the profile check below.

Fix 2: Check for a wrong folder or mixed installation

Reinstalling can appear ineffective if the shortcut points to an older copy.

1. Right-click the Thunderbird shortcut.
2. Choose Properties.
3. On the Shortcut tab, inspect Target.
4. Note the folder containing thunderbird.exe.
5. Open that folder and check whether the repaired files are there.

Also inspect both:

C:Program FilesMozilla Thunderbird
C:Program Files (x86)Mozilla Thunderbird

If more than one Thunderbird installation exists, remove confusion by using the shortcut that points to the installation you repaired. Do not combine DLLs from the two folders.

An ordinal error, such as an ordinal that cannot be located in LDAP60.dll, usually means the file exists but does not export the function expected by that Thunderbird build. A “bad image” message similarly points to corruption or a binary mismatch. Replacing the complete application is safer than replacing one file.

Fix 3: Review antivirus quarantine

Security software can quarantine or delete an application file after an update.

Windows Security steps

1. Open Start and search for Windows Security.
2. Select Virus & threat protection.
3. Choose Protection history.
4. Look for an action involving Thunderbird or ldap60.dll.
5. Expand the entry and read the detected path and action.

Only restore or allow the file after confirming that Thunderbird came from the official installer and that the detection is a false positive. Microsoft warns that restoring a genuine threat can damage the computer.

If you are uncertain:

1. Leave the item quarantined.
2. Uninstall or reinstall Thunderbird from its official source.
3. Run a full Microsoft Defender scan.
4. Do not create an exclusion merely because the filename is familiar.

If the file repeatedly disappears after a clean installation, investigate malware, security software, disk errors, and Windows Event Viewer rather than repeatedly downloading replacement DLLs.

Fix 4: Verify the Thunderbird profile without deleting it

A damaged profile usually does not make ldap60.dll disappear, but it can prevent Thunderbird from starting after the application files are repaired.

To test a separate profile:

1. Press Windows + R.
2. Enter:

thunderbird -P

1. Press Enter.
2. Choose Create Profile.
3. Start the temporary profile.

If Thunderbird opens with the new profile, the program installation is working and the original profile needs attention. Do not delete the old profile. Close Thunderbird, restore your backup if necessary, and use Profile Manager to select the existing profile.

If thunderbird -P does not open Profile Manager, run it from the folder containing thunderbird.exe, or create a shortcut whose target includes -P.

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

Fix 5: Repair Windows components only when Windows has wider problems

DISM and SFC do not normally restore ldap60.dll because it is an application file, not a protected Windows component. Use these commands when several Windows applications show system-file errors, Windows features malfunction, or other built-in files are damaged.

1. Open Start.
2. Search for Command Prompt.
3. Right-click it and select Run as administrator.
4. Run this command first:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for it to finish.
2. Then run:

sfc /scannow

1. Restart Windows and test Thunderbird again.

Microsoft recommends running DISM before SFC. If both commands report that Windows is healthy but Thunderbird still reports ldap60.dll, reinstall Thunderbird rather than repeating these commands.

If manually hunting through Windows repair steps is taking longer than expected, Outbyte PC Repair can scan for problems and show what it identifies; repairs are handled by the full version, and reinstalling Thunderbird remains the definitive fix for this application DLL.

Fix 6: Do not update drivers for this DLL error

Graphics, sound, chipset, and network drivers do not normally provide ldap60.dll. Device Manager and Windows Features are therefore not first-line fixes for this Thunderbird-specific error.

Update drivers only if Device Manager shows a separate warning:

1. Right-click Start.
2. Select Device Manager.
3. Expand the relevant device category.
4. Right-click the device.
5. Choose Update driver.
6. Select Search automatically for drivers.

Do not expect this to restore ldap60.dll. If you are manually checking many devices and unsure which driver is actually outdated, Outbyte Driver Updater can scan and identify driver issues; driver installation is handled by the full version, and it is not a substitute for repairing Thunderbird.

Why DLL download sites and regsvr32 are unsafe here

Random DLL download sites may provide:

• A file from the wrong Thunderbird release
• A 32-bit DLL for a 64-bit process, or the reverse
• A modified or malicious file
• A file that does not match the other Mozilla libraries

They also leave the incomplete Thunderbird installation untouched. Use the official Thunderbird installer instead.

regsvr32 is not an appropriate repair for ldap60.dll. That command registers COM-style DLLs that provide functions such as DllRegisterServer. There is no evidence that Thunderbird’s LDAP library is a self-registering COM server. Running this command:

regsvr32 ldap60.dll

is likely to produce another entry-point error and will not rebuild Thunderbird’s compatible library set.

If the problem continues after reinstalling

Work through these checks:

1. Confirm the shortcut points to the folder you repaired.
2. Confirm the installed Thunderbird architecture matches the selected installer.
3. Check Windows Security Protection history again.
4. Run a Microsoft Defender scan, including an offline scan when ordinary scanning cannot resolve the issue.
5. Review Event Viewer for disk or filesystem errors if files keep disappearing.
6. Test a new Thunderbird profile without deleting the original.
7. Consider System Restore after a failed update or recent software conflict. It can revert system state and remove applications or settings installed afterward.

If the error names xul.dll, mozglue.dll, nss3.dll, VCRUNTIME140.dll, or another dependency, stop treating it as an ldap60.dll problem. Repair the dependency named in the current error.

Prevention

• Keep a current backup of the Thunderbird profile.
• Let Thunderbird updates finish without shutting down Windows.
• Avoid mixing files from different Thunderbird installations.
• Do not place application DLLs in Windows system folders.
• Download Thunderbird only from its official source.
• Review antivirus quarantine before restoring or allowing a missing file.
• Do not use a historical version listing as proof that a DLL belongs to your current Thunderbird build.

FAQ

Is ldap60.dll a Windows file?

No. It is a Mozilla application library historically used by Thunderbird and potentially other Mozilla-derived software. Windows uses the separate Wldap32.dll LDAP library.

Should I copy ldap60.dll into System32?

No. It belongs beside the compatible thunderbird.exe when that Thunderbird build requires it.

Can I download just ldap60.dll?

You should not. A standalone file may be unsafe, the wrong architecture, or incompatible with the rest of Thunderbird. Reinstall the complete official application.

Will reinstalling Thunderbird delete my mail?

Normally, the program and profile are separate, so reinstalling over the application should preserve the profile. Back up the profile first because reinstalling is not itself a backup.

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

Historical indexed versions are 32-bit, but the correct answer for your installation depends on the Thunderbird build. The application and its libraries must match.

Should I run SFC or DISM first?

Only if other Windows components are also failing. For an isolated ldap60.dll error, repair Thunderbird first.

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.