fldpub.dll Missing: Rebuild Microsoft Outlook the Safe Way

fldpub.dll is generally identified as the Microsoft Outlook Network Folders component, so the safest first repair is Microsoft Office or Microsoft 365 repair, not a replacement DLL download. If Windows says fldpub.dll is missing, not found, or could not be loaded, repair the Office installation that is trying to load it and verify the file before taking deeper Windows-repair steps.

What this file actually does

The available file identification describes fldpub.dll as Microsoft Outlook Network Folders, a Microsoft Outlook component published by Microsoft Corporation. That makes it an Office application file rather than a general-purpose Windows library such as a normal System32 component.

#	Preview	Product	Price
1		Microsoft 365 Outlook For Dummies	$16.77	Buy on Amazon
2		Microsoft Outlook: A Crash Course from Novice to Advanced | Unlock All Features to Streamline Your...	$17.97	Buy on Amazon
3		The Microsoft Office 365 Bible: The Most Updated and Complete Guide to Excel, Word, PowerPoint,...	$39.97	Buy on Amazon
4		Microsoft Outlook 365 - 2019: a QuickStudy Laminated Software Reference Guide	$6.48	Buy on Amazon
5		Microsoft Office Mastery: The Ultimate 10-in-1 Guide for Mastering Excel, Word, PowerPoint, Outlook,...	$29.99	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

The exact Office release, bitness, installation directory, file version, and size associated with a particular copy are not established here. Those details can vary with the installed Office product and servicing system, so do not use an Internet file listing to decide which copy belongs on your PC.

Under the hood, an Outlook executable or related Office process asks Windows to load required libraries when it starts or activates a feature. The Windows loader checks whether the requested file exists, whether it matches the process architecture, and whether its dependencies can load. A failure at any of those stages can produce a fldpub.dll message.

#1 Best Overall

Sale

Microsoft 365 Outlook For Dummies

$16.77

Buy on Amazon

That means the DLL named in the error is not always the original cause. The actual problem may be:

• A damaged or incomplete Office installation
• A failed Office update or rollback
• A quarantined file
• Manual deletion or disk-cleanup software
• A 32-bit and 64-bit Office mismatch
• Filesystem corruption
• A damaged Outlook profile or user installation
• Malware or an impostor file in an unexpected directory

The file name alone does not prove that every copy named fldpub.dll is genuine.

Causes by symptom

Error messages you may see

Windows loader-style dialogs can use wording such as:

• “The program can’t start because fldpub.dll is missing from your computer. Try reinstalling the program to fix this problem.”
• “fldpub.dll was not found.”
• “The code execution cannot proceed because fldpub.dll was not found.”
• “fldpub.dll is either not designed to run on Windows or it contains an error.”
• “There was a problem starting fldpub.dll.”

The exact wording depends on the Windows version and the Office component making the request. These messages do not establish that Outlook itself is the only possible caller. Check the program named in the dialog, shortcut, or Event Viewer entry.

A DLL message also does not prove that the DLL is independently broken. Windows may be reporting the first dependency it could not resolve, while the underlying problem is a damaged Office installation, incompatible architecture, or a missing dependency.

Fix 1: Repair Microsoft 365 or Office

This is the most likely fix because repair restores the Office installation as a coordinated set. It can replace missing files and correct installation metadata without requiring you to guess which version of fldpub.dll belongs on the system.

Windows 11 and current Windows 10 Settings

1. Close Outlook and every other Office application.
2. Right-click Start and select Installed apps. On some Windows 10 systems, open Settings → Apps → Apps & features instead.
3. Search for Microsoft 365, Microsoft Office, or the affected Office product.
4. Select the three-dot menu beside the product.
5. Choose Modify.
6. Approve the User Account Control prompt if Windows asks.
7. Select Quick Repair.
8. Select Repair and wait for the process to finish.
9. Restart Windows.
10. Start Outlook from the Start menu rather than an old taskbar shortcut.
11. Test the action that originally produced the fldpub.dll error.

Quick Repair is a relatively fast first pass. It may repair the installation structure and replace common damaged files, but it does not necessarily download a complete fresh Office installation.

If the error remains, repeat the process and choose Online Repair instead. Online Repair generally requires an Internet connection and can reconfigure or restore the broader Office installation. It is the stronger choice when Quick Repair completes successfully but Outlook still cannot load the component.

Older MSI-based Office installations

Some older Office installations use Control Panel rather than the modern Settings repair interface.

1. Press Windows key + R.
2. Type appwiz.cpl.
3. Press Enter.
4. Select Microsoft Office in Programs and Features.
5. Click Change.
6. Choose Repair.
7. Follow the prompts.
8. Restart Windows and test Outlook.

Do not assume that repairing whichever Office entry appears first will fix the failing program. Multiple Office versions can coexist, and an old shortcut may launch an older installation. If the dialog names a particular executable, inspect that application and repair the corresponding Office product.

How to tell whether repair worked

Repair worked if Outlook starts without the DLL message and the feature that previously failed now opens normally. If Outlook starts but the same error appears when accessing a particular folder or function, the installation may still be incomplete, or the problem may involve a damaged Outlook profile.

Rank #2

Microsoft Outlook: A Crash Course from Novice to Advanced | Unlock All Features to Streamline Your Inbox and Achieve Pro-level Expertise in Just 7 Days or Less

$17.97

Buy on Amazon

If Quick Repair reports success but changes nothing, do not keep repeating it. Move to Online Repair, then consider a full uninstall and reinstall if Online Repair also fails.

Fix 2: Check antivirus quarantine before replacing anything

Security software can quarantine a legitimate file after a detection or a false positive. This is especially worth checking if the error began immediately after a security notification, scan, update, or cleanup action.

The exact menu names depend on the antivirus product, but the general process is:

1. Open your antivirus or Windows Security application.
2. Open Protection history, Quarantine, Detected threats, or the equivalent area.
3. Search for fldpub.dll.
4. Inspect the recorded file location.
5. Do not restore it solely because the name matches the error.
6. Restore it only if it is located inside the legitimate Office installation, has Microsoft file information, and passes the product’s trust checks.
7. Update Office after restoration.
8. Run a full malware scan.

If the quarantined file came from a temporary directory, a user-profile folder, a startup location, or an unrelated application directory, treat it as suspicious rather than restoring it. A malicious file can use a familiar Microsoft filename.

If the antivirus repeatedly removes a file from a valid Office installation, update both the security product and Office, then contact the security vendor through its normal support process. Do not disable protection permanently to force a DLL into place.

Fix 3: Verify the surviving file and its installation path

If fldpub.dll still exists somewhere on the computer, inspect it before deciding whether it is the copy Outlook needs.

1. Open File Explorer.
2. Search the locations associated with the Office installation for fldpub.dll.
3. Right-click the file and choose Properties.
4. Open the Details tab.
5. Check whether the description identifies Microsoft Outlook Network Folders and whether Microsoft Corporation appears as the publisher.
6. Open the Digital Signatures tab.
7. Select the signature and click Details.
8. Confirm that Windows reports the signature as valid.

A valid Microsoft signature is useful evidence, but it is not the only check. The file should also be associated with the Office installation that is actually launching Outlook. A correctly signed copy from a different Office generation or architecture may still be unsuitable.

Do not invent a normal path from a search result. The expected directory depends on the Office product, installation technology, release, and architecture. If several copies exist, use the path of the executable named in the error and the installed Office entry to determine which installation is relevant.

You can also check whether Windows is launching an unexpected Outlook copy:

1. Open Task Manager with Ctrl + Shift + Esc.
2. Use the Details tab if Outlook is running.
3. Right-click the Outlook process and choose Open file location.
4. Compare that location with the Office product you repaired.

If Outlook will not stay open, right-click its shortcut, choose Properties, and inspect the Target field. An obsolete shortcut may point to an older installation.

Fix 4: Check 32-bit versus 64-bit Office

Windows bitness and Office bitness are separate. A 32-bit Office installation can run on 64-bit Windows, so installing or copying a 64-bit DLL simply because Windows itself is 64-bit is unsafe.

Rank #3

Sale

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

• 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

$39.97

Buy on Amazon

A mismatch can occur after:

• Installing a different Office edition over an older one
• Restoring files from another computer
• Mixing old MSI and newer Click-to-Run installations
• Repairing one Office product while an old shortcut launches another
• Performing an incomplete update or rollback

To identify the Office architecture:

1. Open any Office application that still starts, such as Word.
2. Choose File → Account.
3. Select About Word, About Excel, or the equivalent About option.
4. Look for the stated 32-bit or 64-bit architecture.
5. Record the Office product and update channel information shown there.

If no Office application opens, use Settings → Apps → Installed apps or Control Panel → Programs and Features to identify the installed products, then repair the matching entry. The interface may not always display architecture clearly, so the reliable fix for a suspected mismatch is repair or reinstall of the intended Office product, not manual DLL replacement.

Never copy a 32-bit fldpub.dll into a 64-bit Office installation, or the reverse. The DLL must match the process architecture, its dependent libraries, and the installation’s servicing state.

Fix 5: Repair Windows components with DISM and SFC

DISM and System File Checker are secondary steps here. fldpub.dll is identified as an Office file rather than a Windows-protected system component, so SFC may report no integrity violations and still not restore this file.

Use these commands when the PC shows broader corruption, Windows servicing errors, failed updates, or problems affecting applications beyond Outlook.

1. Save your work and close running applications.
2. Open Start and type Command Prompt.
3. Right-click Command Prompt and choose Run as administrator.
4. Select Yes at the User Account Control prompt.
5. Run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for DISM to finish. Do not close the window merely because progress appears paused.
2. When the command completes, run:

sfc /scannow

1. Wait until verification reaches 100 percent.
2. Restart Windows.
3. Retry Office Online Repair if fldpub.dll is still missing.

DISM repairs the Windows component store that Windows uses for system servicing. SFC then checks protected Windows files against that repaired store. Neither command is a substitute for repairing an Office installation.

If DISM or SFC reports that it could not complete the operation, restart Windows, install pending Windows updates, and run the commands again from an elevated Command Prompt. If they report no integrity violations, return to Office repair rather than treating that result as proof that the Office files are healthy.

Outbyte PC Repair can reduce the guesswork of hunting through system reports and repeating SFC or DISM without knowing what changed; its free scan shows detected issues, while repair is performed by the full version, and it is not required when Office repair is the actual cause.

Fix 6: Install pending Windows and Office updates

A failed update can leave an Office installation in a mixed state. Updating after repairing Windows components can allow the Office servicing system to complete its work.

Check Windows Update

1. Right-click Start and select Settings.
2. Open Windows Update.
3. Select Check for updates.
4. Install available updates.
5. Restart when prompted.
6. Return to Windows Update and check again until no required restart remains.

Update Office

If an Office application opens:

1. Open Word or another Office application.
2. Choose File → Account.
3. Select Update Options.
4. Choose Update Now.
5. Wait for the update process to finish.
6. Restart Windows.
7. Test Outlook.

If Office will not open, use Online Repair instead of trying to force an update through a broken installation.

Fix 7: Test a new Outlook profile

A new profile will not restore a missing binary, so use this only after Office repair has completed or when Outlook starts but fails with profile-specific behavior.

1. Close Outlook.
2. Press Windows key + R.
3. Type control.
4. Press Enter.
5. Set View by to Small icons or Large icons.
6. Open Mail or Mail (Microsoft Outlook).
7. Select Show Profiles.
8. Select Add.
9. Enter a name for the test profile.
10. Follow the prompts to add the account.
11. Under When starting Microsoft Outlook, select Prompt for a profile to be used, or select the new profile directly.
12. Start Outlook and test it.

If the new profile works, the original profile or its local configuration is likely damaged. If both profiles produce the same fldpub.dll error, the problem remains at the Office installation or system level.

Fix 8: Check drivers only when the evidence points there

A normal fldpub.dll load failure is not primarily a graphics, chipset, storage, or audio-driver problem. Do not install random drivers merely because the error appears while starting a game or another application. First identify which executable is calling the DLL.

Rank #4

Microsoft Outlook 365 - 2019: a QuickStudy Laminated Software Reference Guide

$6.48

Buy on Amazon

Driver work becomes reasonable when Device Manager shows an error, Windows is crashing broadly, storage problems are present, or the application’s own documentation identifies a driver dependency.

1. Right-click Start.
2. Select Device Manager.
3. Expand the relevant category, such as Display adapters, Storage controllers, or Sound, video and game controllers.
4. Right-click the affected device.
5. Choose Properties.
6. Check the General tab for a device status error.
7. Open the Driver tab and note the provider and date.
8. Use Update driver only when an appropriate update is available from the hardware or PC manufacturer.
9. Restart Windows and retest Outlook.

Outbyte Driver Updater can show which of many installed drivers are stale instead of making you guess through Device Manager; its free scan identifies issues, while driver installation is handled by the full version, and it is not required for an Office-only DLL failure.

Fix 9: Reinstall Office using Microsoft’s supported process

Use reinstall when Online Repair fails, the Office installation is visibly incomplete, repair repeatedly rolls back, or multiple conflicting Office installations are present.

Before starting, make sure you know the Microsoft account or license arrangement used for the installation and close all Office applications.

1. Open Microsoft’s official Office uninstall and reinstall guidance.
2. Follow Microsoft’s supported uninstall workflow for the installed Office type.
3. Restart Windows when instructed.
4. Remove only the affected Office installation unless Microsoft’s procedure directs otherwise.
5. Sign in through Microsoft’s official installation process.
6. Reinstall the intended Office product and architecture.
7. Restart Windows.
8. Open Outlook and allow its first-run setup to complete.
9. Test the operation that originally failed.

Reinstalling only Outlook may not be possible or sufficient when Outlook is installed as part of a full Office suite. A complete Office repair or reinstall is the definitive fix for a missing Office component.

Why you should not download or copy fldpub.dll

Do not download an isolated fldpub.dll from a random DLL download site. An untrusted copy can contain malware, have the wrong version, target the wrong architecture, lack required dependencies, or fail to match the Office installation’s servicing state.

Even a clean DLL copied into the wrong directory may not fix the loader error. Windows could continue loading a different copy, reject the architecture, or report another missing dependency. Manual replacement can also hide the original Office corruption and create version conflicts during later updates.

Use Microsoft Office repair, Online Repair, or Microsoft’s official uninstall and reinstall process instead. If antivirus quarantined a legitimate copy, verify its location and Microsoft signature before restoring it.

Does regsvr32 fix this error?

Usually not. regsvr32 is intended for DLLs that expose the COM registration entry point DllRegisterServer. A missing Outlook module is not automatically a registration problem.

Running it against a library that does not support self-registration can produce an error such as:

The module was loaded but the entry-point DllRegisterServer was not found.

That result does not mean the DLL needs to be downloaded or that Windows registration is the root cause. Do not register fldpub.dll unless Microsoft documentation for the specific Office build explicitly requires it. For the normal missing-file scenario, repair Office instead.

Best Value

Microsoft Office Mastery: The Ultimate 10-in-1 Guide for Mastering Excel, Word, PowerPoint, Outlook, Teams, OneNote, Access, Publisher, OneDrive, and ... Users (Business Productivity Blueprint)

$29.99

Buy on Amazon

Advanced checks when the error persists

If reinstalling Office does not help, identify the real caller:

1. Reproduce the error.
2. Note the application named in the dialog.
3. Open Event Viewer by pressing Windows key + R, entering eventvwr.msc, and pressing Enter.
4. Check Windows Logs → Application for an event at the same time.
5. Look for the failing application name and module path.
6. Compare that path with the Office installation you repaired.

If the caller is not Outlook or an Office process, another program may be requesting a Microsoft component from an obsolete or damaged installation. Repairing Outlook repeatedly may not affect that program.

If the file exists outside an expected Office directory, check its signature and run a full malware scan. Do not assume a matching filename makes it legitimate.

FAQ

Is fldpub.dll a Windows system file?

It is identified as a Microsoft Outlook Network Folders component associated with Microsoft Outlook and Microsoft Corporation. It is not established here as a standalone Windows System32 or SysWOW64 component, so treat it as an Office installation file unless local installation evidence proves otherwise.

Is fldpub.dll legitimate?

The described identity is consistent with a genuine Microsoft Outlook component. Confirm a surviving copy through Properties → Details and Properties → Digital Signatures, then verify that its location belongs to the Office installation being used. A file with the same name in a temporary or unrelated directory may be an impostor.

Will SFC restore fldpub.dll?

Not necessarily. SFC repairs protected Windows files, while this file is believed to belong to Office. Run DISM and SFC when broader Windows corruption is suspected, but use Office repair as the primary fix.

Should I copy the DLL from another computer?

No. The other computer may use a different Office release, architecture, update channel, dependency set, or installation path. Repair or reinstall the matching Office product instead.

Can a 32-bit Office installation run on 64-bit Windows?

Yes. Windows architecture does not determine Office architecture. Check the Office About screen and repair or reinstall the intended architecture rather than copying a DLL based on the Windows bitness.

What if Outlook alone still fails after Office repair?

Check antivirus quarantine, confirm which Outlook executable is launching, test a new Outlook profile, and inspect Event Viewer. If the binary remains missing or the installation is inconsistent, use Microsoft’s supported uninstall and reinstall process.

Could malware cause the message?

Yes, particularly if the file is found outside an expected Office directory or has no valid Microsoft signature. Scan the system and do not restore suspicious copies from quarantine.

Quick Recap

SaleBestseller No. 1

Microsoft 365 Outlook For Dummies

$16.77

Bestseller No. 2

Microsoft Outlook: A Crash Course from Novice to Advanced | Unlock All Features to Streamline Your Inbox and Achieve Pro-level Expertise in Just 7 Days or Less

$17.97

SaleBestseller No. 3

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

$39.97

Bestseller No. 4

Microsoft Outlook 365 - 2019: a QuickStudy Laminated Software Reference Guide

$6.48

Bestseller No. 5

Microsoft Office Mastery: The Ultimate 10-in-1 Guide for Mastering Excel, Word, PowerPoint, Outlook, Teams, OneNote, Access, Publisher, OneDrive, and ... Users (Business Productivity Blueprint)

$29.99

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.