Using Classic Outlook on Windows for personal email, calendar, and contact management
For a damaged .ost file, the supported recovery path depends on whether the data is still on the server or only in the local cache.
- If the mailbox is available in Outlook Web Access or on Exchange, rebuild the
.ostfile.- Close Outlook.
- Go to
%localappdata%\Microsoft\Outlook. - Find the affected
.ostfile. - Delete it, or rename the extension to
.old. - Start Outlook again.
.ostfile. - If Outlook reports corruption and the file cannot be opened, ScanOST is not the solution in current versions.
-
Scanost.exeis no longer available starting in Outlook 2010. - Current guidance is to delete or rebuild the offline Outlook Data File and let Outlook resync from Exchange.
-
- If locally cached content must be preserved, use the Inbox Repair tool only as a limited diagnostic/repair option.
-
Scanpst.execan scan both.ostand.pstfiles and try to repair internal file structure. - It does not connect to or analyze mailbox data stored on Exchange.
- For Outlook 2016/2019, one documented location is
C:\Program Files (x86)\Microsoft Office\root\Office16forSCANPST.EXE. - Before running it, back up the existing Outlook data file.
-
- If the issue is with a
.pstfile instead of an.ostfile, useSCANPST.EXE.- Exit Outlook.
- Open
SCANPST.EXE. - Select Browse and choose the
.pstfile. - Select Start.
- If errors are found, select Repair.
- After repair, reopen Outlook.
- If
SCANPST.EXErepairs a.pstand creates a.bakfile, additional items may be recoverable.- Copy the
.bakfile. - Rename the copy to use a
.pstextension. - Import it into Outlook with the Import and Export Wizard.
- Copy the
- To confirm the data file location in Outlook when Outlook can open:
- Select File > Account Settings > Account Settings.
- Open the Data Files tab.
If the mailbox is still accessible in Outlook Web Access, rebuilding the .ost file is the primary supported method. The main risk is loss of data that exists only in the local offline cache and was never synchronized to the server, so backing up the damaged file first is the safest step.