PST is not an Outlook Data File – Causes and Solutions

What is a PST File?

A PST (Personal Storage Table) file is the format Outlook for Windows uses to keep your emails, contacts, calendar entries, and tasks on your computer. When you add a POP account or export a mailbox, Outlook writes everything into one .pst file. The format belongs to Outlook, so other programs cannot open it directly, and Outlook is fussy about the exact structure of the file. That is why a small problem inside the file stops the whole thing from loading.

Why You See the “PST is not an Outlook Data File” Error

I have hit this message on several machines while moving old archives around, and the cause is almost always one of these:

• The .pst file is corrupt because Outlook closed during a write, the disk had a bad sector, or the file grew past the size limit.
• The file is marked read only, so Outlook can open it but refuses to mount it as a working data file.
• You moved the file to a network drive or a removable disk and Outlook lost the path.
• The file was created or edited by a program that is not Outlook, so the internal header does not match what Outlook expects.

Knowing which of these caused your error tells you which fix below to try first. A read only flag clears in seconds. Real corruption needs ScanPST or a dedicated repair tool.

Fix 1: Run ScanPST.exe (and Find It on Modern Outlook)

ScanPST.exe is the free Inbox Repair Tool that ships with Outlook. It scans the .pst, fixes minor structural errors, and is the first thing to try. The catch is the location. Most old guides point you to a Program Files (x86) path, but that only applies to a 32 bit MSI install.

On a current Click to Run install of Microsoft 365, Outlook 2024, 2021, or 2019, ScanPST.exe lives here instead:

• Microsoft 365 / 2024 / 2021 / 2019 (Click to Run): C:\Program Files\Microsoft Office\root\Office16
• Older 32 bit MSI install: C:\Program Files (x86)\Microsoft Office\root\Office16

Open that folder, run ScanPST.exe, browse to your problem .pst, click Start, then click Repair if it finds errors. One note from testing: the new Outlook for Windows (the rebuilt app) does not use PST files at all and has no ScanPST, so this fix only applies to classic Outlook.

Fix 2: Clear the Read Only Property

If ScanPST reports no errors but the file still will not open, check the read only flag. Close Outlook, find the .pst in File Explorer, right click it, choose Properties, and on the General tab clear the Read only checkbox at the bottom. Click Apply and reopen Outlook. This is the fastest fix and it solves the error whenever the file came off a CD, a backup drive, or a folder with locked permissions.

Fix 3: Move the PST to a Local Folder

Outlook does not officially support running a .pst from a network share or a USB drive, and that setup throws this exact error. Close Outlook, copy the .pst to a local folder such as Documents, then open Outlook and point it at the copied file through File, then Open and Export, then Open Outlook Data File. Working from the local copy removes the latency and permission problems that a remote file creates.

Fix 4: Update Outlook

An outdated build can misread a .pst that a newer version handles fine. In Outlook go to File, then Office Account, then Update Options, and choose Update Now. Restart Outlook after it installs and try the file again.

Fix 5: Check the Disk for Errors

A failing disk or a bad sector under the .pst will keep corrupting it no matter how often you run ScanPST. Open Command Prompt as administrator and run chkdsk on the drive that holds the file, for example chkdsk C: /f /r. Let it finish, restart, then repair the .pst again. Fixing the disk first stops the corruption from coming back.

Fix 6: Create a New Outlook Profile

If the profile itself is damaged, a fresh one often clears the error. Close Outlook, open Control Panel, go to Mail, click Show Profiles, then Add, and give the new profile a name. Set Outlook to use the new profile, open it, and attach your .pst through Open Outlook Data File. The old profile stays in place, so nothing is lost if this does not help.

When every native fix fails, the .pst is corrupt beyond what ScanPST can rebuild. At that point the safe move is to read the mailbox with a dedicated repair tool and write it back to a clean file or another format. This is the only step where a paid tool earns its place. For a single read only flag or a minor scan, stick with the free methods above.

Steps to Convert the PST

1. Launch the tool and click Open, then add the damaged .pst file.
2. Let it scan and preview the recovered mailbox so you can confirm the items are intact.
3. Choose your output, for example a fresh PST or PDF.
4. Pick a save location and run the export.

FAQs

Why does Outlook say my PST is not an Outlook Data File when it opened yesterday?
Something changed the file between sessions, usually a read only flag, a move to a network drive, or corruption from an unclean shutdown. Clear the read only box first, then run ScanPST.

Where is ScanPST.exe on Microsoft 365 or Outlook 2021?
On a Click to Run install it sits in C:\Program Files\Microsoft Office\root\Office16, not the old Program Files (x86) path that pre 2019 guides list.

Can ScanPST fix every PST error?
No. It repairs minor structural damage. If the header is badly broken or the file came from a non Outlook program, ScanPST cannot rebuild it and you need a dedicated repair tool.

Does the new Outlook for Windows have an Inbox Repair Tool?
No. The rebuilt new Outlook does not store mail in PST files, so there is no ScanPST. These fixes apply to classic Outlook only.

Will repairing the PST delete any of my emails?
ScanPST tries to keep everything and creates a backup copy first. A good repair tool previews the data before export so you can confirm nothing is missing.

Concluding Words

The “PST is not an Outlook Data File” error almost always traces back to a read only flag, a misplaced file, or genuine corruption. Work down the list from clearing the flag to running ScanPST from the correct Click to Run folder, and only reach for a paid repair tool when the file is too damaged for the native options. Which of these causes turned out to be behind your error?