scnpst32.dll Missing: Rebuild Outlook’s Repair Chain Safely

If scnpst32.dll is missing, not found, or could not be loaded, repair the Microsoft Outlook or Office installation that owns the file rather than downloading the DLL separately. scnpst32.dll is an Outlook component used by the Inbox Repair Tool, SCANPST.EXE, especially when working with ANSI Outlook data files.

The safest sequence is:

1. Close Outlook and other Office programs.
2. Repair Office, preferably with Online Repair when a file is missing.
3. Restart Windows.
4. Launch the copy of SCANPST.EXE installed with the same Office installation.
5. Check Windows Security if antivirus software quarantined the file.
6. Reinstall the matching Office product if repair does not restore it.

What scnpst32.dll does

scnpst32.dll is a genuine Microsoft Outlook file associated with the Inbox Repair Tool. Microsoft Outlook update manifests list it alongside files such as SCANPST.EXE, SCNPST64.DLL, and MPSPT32.DLL.

As an Amazon Associate I earn from qualifying purchases.

The file is associated with Outlook’s handling of ANSI-format data stores. The 32 in the filename identifies the 32-bit component. It does not mean that the file is a Windows system DLL.

A 64-bit Outlook package can contain both SCNPST32.DLL and SCNPST64.DLL. Microsoft’s published Outlook manifests show that file versions and sizes vary by Outlook release, architecture, language, update level, and installation type. Therefore, a version found on one computer should not be treated as a universal replacement.

Microsoft publishes Outlook file manifests, including scnpst32.dll, in its Outlook 2016 update file list and Outlook 2010 security-update file list.

Fix 1: Repair Microsoft Office

Time needed: About 10–30 minutes, depending on the repair type and internet connection.

Office repair is the best first fix because it restores missing or damaged application files together with their related dependencies. It also avoids mixing files from different Office releases.

For Microsoft 365 or Click-to-Run Office

1. Close Outlook, Word, Excel, and every other Office program.
2. Right-click the Start button.
3. Select Installed apps.
4. Find Microsoft 365, Microsoft Office, or the relevant Office product.
5. Select the three-dot menu beside it.
6. Choose Modify.
7. If Windows asks for permission, select Yes.
8. Choose Quick Repair, then select Repair.
9. Wait for the process to finish.
10. Restart Windows.
11. Try Outlook or SCANPST.EXE again.

Quick Repair is a reasonable first attempt when the installation has a minor problem. If scnpst32.dll is still missing, repeat the process and choose Online Repair instead.

Online Repair replaces a broader set of Office files and normally requires an internet connection. It can take longer and may repair more of the installation than Quick Repair.

1. Open Settings > Apps > Installed apps.
2. Select the three-dot menu beside Microsoft 365 or Office.
3. Choose Modify.
4. Select Online Repair.
5. Select Repair.
6. Allow the repair to complete.
7. Restart Windows.

Microsoft’s current instructions are in Repair an Office application.

For an MSI-based Office installation

Older volume-license and traditional Office installations may use Windows Control Panel instead of the Click-to-Run repair screen.

1. Press Windows key + R.
2. Type appwiz.cpl.
3. Press Enter.
4. Select the Microsoft Office installation.
5. Select Change.
6. Choose Repair.
7. Select Continue.
8. Follow the prompts.
9. Restart Windows.

If the repair wizard does not offer a repair option, the installation may use a different deployment method. Use the Office entry under Settings > Apps > Installed apps, or contact the administrator who deployed Office.

How to tell whether repair worked

Repair is successful when:

• Outlook starts without the scnpst32.dll error.
• SCANPST.EXE opens normally.
• The error does not return after restarting Windows.
• The repaired ScanPST can browse to an Outlook data file.

If the error remains, do not copy a DLL from another computer. Continue with the checks below.

Fix 2: Reinstall the matching Office product

Time needed: About 20–60 minutes, plus the time needed to download Office.

If Online Repair cannot restore the file, reinstall the same licensed Office product and architecture. Reinstalling is more reliable than replacing one file because it restores the surrounding Outlook components as a consistent set.

Before uninstalling, make sure you know:

• Whether the installation is Microsoft 365, Office 2010, Office 2013, Office 2016, or another edition.
• Whether Office is 32-bit or 64-bit.
• Which Microsoft account or organizational installation source owns the license.
• Where important PST files are stored.
• Whether Outlook uses an Exchange or Microsoft 365 mailbox whose data is available on the server.

Microsoft provides installation and reinstall instructions in Download, install, or reinstall Microsoft 365 or Office.

After reinstalling:

1. Restart Windows.
2. Open Outlook once.
3. Close Outlook again.
4. Locate and run the newly installed SCANPST.EXE.
5. Test the Inbox Repair Tool with a backup copy of the PST if possible.

Do not install a different Office branch merely because it contains a similarly named file. Files from Office 2007, 2010, 2013, 2016, Microsoft 365, and other releases are not interchangeable.

Fix 3: Use the correct copy of SCANPST.EXE

Time needed: 5–15 minutes.

A common cause of this error is launching a copied SCANPST.EXE from the desktop, a download folder, an old backup, or another computer. ScanPST can depend on neighboring files in its original Office directory. Moving only the executable can break that relationship.

Do this instead:

1. Close Outlook.
2. Delete or set aside the copied SCANPST.EXE. Do not delete the installed Office copy.
3. Open the Office installation folder.
4. Find the SCANPST.EXE located in that installation.
5. Run it from its original folder.

The exact path varies by Office version, whether Office is 32-bit or 64-bit, and whether it was installed with Click-to-Run or MSI technology. Search for SCANPST.EXE with File Explorer, then inspect its location before opening it.

To check the installation:

1. Press the Windows key.
2. Type SCANPST.EXE.
3. Right-click the result and choose Open file location.
4. Confirm that the location is inside an Office or Microsoft Office installation directory.
5. Run that copy.

If the only copy is on the desktop or in a download folder, repair Office before using ScanPST.

Fix 4: Repair the PST separately

Time needed: 10 minutes to several hours, depending on the PST size.

Repairing Office restores scnpst32.dll. It does not repair a damaged Outlook data file. These are separate problems.

Use ScanPST only after the tool itself opens successfully.

1. Exit Outlook completely.
2. Make a backup copy of the PST before attempting repairs.
3. Start the correct installed SCANPST.EXE.
4. Select Browse.
5. Choose the PST file.
6. Select Start.
7. If errors are reported, select Repair.
8. Allow the process to finish.
9. Start Outlook and check the affected folders.

Microsoft explains this process in Repair Outlook data files.

Microsoft’s tool creates a backup during repair, but keeping your own copy first is still prudent. ScanPST may need to be run more than once. It cannot guarantee recovery of every item, especially when data has been permanently deleted or is severely corrupted.

ANSI PST and Unicode PST

ANSI and Unicode describe Outlook data-file formats and compatibility. An ANSI PST may be associated with older Outlook versions and has different limitations from a Unicode PST.

That format distinction does not make scnpst32.dll a Windows file. It remains an Outlook component. Microsoft documents ANSI PST compatibility in Cannot import an ANSI PST file into Outlook.

If the problem concerns an OST

An OST is an offline cache for an Exchange or Microsoft 365 account. Before removing an OST, confirm that the mailbox data is available on the server and that Outlook can synchronize it.

Microsoft’s PST and OST repair guidance explains the distinction. Do not treat an OST like a standalone PST backup.

Fix 5: Check Windows Security quarantine

Time needed: 5–10 minutes.

Antivirus protection can occasionally quarantine a genuine Office file, or a damaged Office installation can trigger a detection. Check the event before attempting to restore anything.

1. Open Start.
2. Type Windows Security.
3. Open the app.
4. Select Virus & threat protection.
5. Select Protection history.
6. Look for an event involving Outlook, Office, or scnpst32.dll.
7. Open the event details.
8. Check the detected file path and the detection name.

Restore or allow the file only when the Office installation is genuine and the detection has been verified as a false positive. If the event is suspicious, leave the file quarantined and repair or reinstall Office instead.

Microsoft notes that Protection History retains events for a limited period, so an old quarantine event may no longer appear. See Protection history in Windows Security.

After a verified false positive is restored, run the Office repair process anyway if the installation is incomplete. A restored file may still be the wrong version or may have missing neighboring dependencies.

Fix 6: Check Office architecture and mixed installations

Time needed: 10–20 minutes.

A 32-bit DLL should not be substituted into a 64-bit Office directory, and a file from one Office release should not be mixed with another. A 64-bit Outlook package may contain both the 32-bit and 64-bit ScanPST-related components, so the filename alone does not tell you which complete installation is present.

To check Office bitness in Outlook:

1. Open Outlook if it starts.
2. Select File.
3. Select Office Account or Account.
4. Select About Outlook.
5. Read the version and bitness shown in the dialog.

If Outlook will not start, check the Office product under Settings > Apps > Installed apps and the installer or account used to deploy it. On managed computers, ask the organization’s Office administrator.

Repair or reinstall the same product family and architecture. Do not copy SCNPST32.DLL from a 32-bit installation into a 64-bit installation, or vice versa.

Fix 7: Run DISM and SFC only for broader Windows corruption

Time needed: 15–45 minutes.

SFC and DISM repair protected Windows components. They do not normally restore a DLL installed exclusively by Office. Use them when Windows itself shows other corruption symptoms, or when Office repair is failing alongside broader system problems.

1. Save your work.
2. Open Start.
3. Type Command Prompt.
4. Right-click Command Prompt.
5. Select Run as administrator.
6. Select Yes at the permission prompt.
7. Run this command:

DISM.exe /Online /Cleanup-Image /RestoreHealth

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

sfc /scannow

1. Wait until the verification reaches 100 percent.
2. Restart Windows.
3. Run Office Online Repair again if scnpst32.dll is still missing.

Do not close the Command Prompt while either scan is running. A successful result means Windows component repair completed, not necessarily that the Outlook DLL was restored. The official procedure is in Microsoft’s DISM and SFC guidance.

Running these commands repeatedly without checking what changed is unlikely to fix an Office-only file problem. If you are manually hunting through Windows components and cannot determine whether corruption was found, Outbyte PC Repair can scan for system problems and show what it detects; its repair actions are handled by the full version, and it is not required for this Outlook-specific fix.

Fix 8: Use System Restore for a recent rollback

Time needed: 20–60 minutes.

System Restore is appropriate when the error began after a recent Office installation, update, cleanup operation, or suspected system change and a suitable restore point exists.

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

System Restore rolls back system files, registry settings, and installed programs. It does not normally remove personal files, but you should still preserve important PST files first. Microsoft describes the process in System Restore.

After the rollback, check Office and Windows Update. If the Office installation is still incomplete, run Online Repair.

Fix 9: Test a new Outlook profile

Time needed: 10–20 minutes.

If Office repair succeeds but Outlook still fails, the remaining problem may be an Outlook profile rather than scnpst32.dll.

1. Close Outlook.
2. Press Windows key + R.
3. Type:

control mlcfg32.cpl

1. Press Enter.
2. Select Show Profiles.
3. Select Add.
4. Create a new profile.
5. Add the mailbox account.
6. Choose Always use this profile and select the new profile, or select Prompt for a profile to be used.
7. Start Outlook.

Do not delete the old profile until you have confirmed that needed accounts and data are available. A new profile can diagnose profile corruption, but it does not repair a missing Office DLL.

Microsoft’s Outlook startup troubleshooting covers profile-related startup failures.

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

Do not use regsvr32 for this error

regsvr32 is not a general DLL repair command. It applies to DLLs that expose registration entry points such as DllRegisterServer. It does not restore a missing Office file or rebuild ScanPST’s dependency chain.

A command such as:

regsvr32 scnpst32.dll

is therefore not a standard fix. If it reports that the module could not be found, that may mean the file or one of its dependencies is missing. It does not prove that registration is required.

Microsoft documents the command’s intended scope in regsvr32.

Do not download the DLL from a random site

Avoid standalone DLL download sites pages and files copied from another computer. A downloaded replacement may have:

• The wrong Office version.
• The wrong architecture.
• Missing dependent files.
• No trustworthy chain of origin.
• A damaged or modified file.
• A mismatch with the installed Outlook branch.

Never place a downloaded DLL in C:WindowsSystem32, C:WindowsSysWOW64, the Windows directory, or an arbitrary application folder. Microsoft’s supported path is to repair or reinstall the Office product that owns the file.

The safe sources are:

• The existing Microsoft Office repair feature.
• The Microsoft account or organizational Office installer.
• A genuine Office installation medium or deployment source managed by your organization.

Updating drivers is not a normal fix

scnpst32.dll is an Outlook component, not a device driver. Driver updates are relevant only if Windows has separate hardware or system instability symptoms.

Check Device Manager only when you also see a device warning:

1. Right-click Start.
2. Select Device Manager.
3. Expand the affected hardware category.
4. Right-click a device with a warning icon.
5. Select Update driver.
6. Choose Search automatically for drivers.

Do not expect this to replace scnpst32.dll. If you are manually checking many devices and guessing which driver is stale, Outbyte Driver Updater can scan and identify driver issues; driver installation is handled by the full version, and it is not required for repairing Outlook.

The Windows Features dialog is also not relevant to this file. Enabling .NET Framework, DirectPlay, or another optional feature will not install an Outlook component.

Likely causes and the matching fix

Likely cause	Best response
Damaged or incomplete Office installation	Run Online Repair
SCANPST.EXE was copied elsewhere	Use the installed copy beside its Office files
Antivirus quarantine	Inspect Protection History and verify authenticity
Mixed Office versions or architectures	Repair or reinstall the matching Office product
Damaged PST	Back up the PST and run ScanPST after Office is repaired
Windows component corruption	Run DISM, then SFC
Recent installation or update problem	Use System Restore if a suitable point exists
Damaged Outlook profile	Create and test a new profile

Frequently asked questions

Is scnpst32.dll a Windows system file?

No. It is an Outlook or Office component associated with the Inbox Repair Tool. It should not be treated like a general Windows runtime DLL.

Is it related to Visual C++, DirectX, or .NET?

There is no basis for treating it as a Visual C++, DirectX, or .NET runtime file. Installing those runtimes is not the normal solution.

Should I download scnpst32.dll separately?

No. Repair or reinstall the matching Microsoft Office installation. A standalone copy can be incompatible or unsafe and may leave other Office files damaged.

Why does the error appear when I am repairing a PST?

ScanPST needs its Office files before it can open. If the ScanPST executable or its neighboring DLLs are missing, the tool may fail before it reaches the PST repair stage.

Can I copy SCANPST.EXE to the desktop?

You can, but you should not use the copied version. Its related Office files may remain in the original installation directory, causing a missing-DLL error.

Does SCNPST32.DLL mean I have 32-bit Windows?

No. The suffix identifies the component, not necessarily the Windows edition. A 64-bit Outlook package can contain both SCNPST32.DLL and SCNPST64.DLL.

Will SFC repair the missing file?

Usually not directly. SFC repairs protected Windows components, while this file belongs to Office. Run SFC only when there are broader Windows corruption symptoms or Office repair is failing alongside system problems.

What if Outlook still fails after Office repair?

Confirm that the correct SCANPST.EXE is being launched, check antivirus quarantine, verify Office architecture, test a new Outlook profile, and reinstall Office if necessary. Preserve PST and OST backups before taking destructive steps.

What information should I provide to support?

Record the exact error text, Office edition, Office bitness, whether it is Microsoft 365 or a traditional installation, the path of the executable being launched, and whether Windows Security quarantined a file. Keep PST or OST backups available.

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.