Note – You should know the location of PST file to use the tool.
The same has been shown in the image below.
To repair the damaged file, click on the ‘ Repair’ button present at the bottom of the tool’s interface. The report contains the number of folders and number of items found in the file with a message that errors were found in the file. 
After the file consistency is checked, the tool presents an analysis report.
With this, the utility starts scanning the corrupt PST file. Once done, click on the ‘ Start’ tab of the scanpst.exe tool as shown in the below image: Save ost file if cannot open outlook 2016 windows#
Type in the location and file name of your Personal Folders file or Browse to find it by the use of Windows file system. Step 2: Now, repair the damaged Outlook PST file. 64-bit Outlook the location is C:\Program Files\Microsoft Office\Office15\. 64-bit Windows the location is C:\Program Files (x86)\Microsoft Office\Office15\. 32-bit Windows the location is C:\Program Files\Microsoft Office\Office15\. 64-bit Outlook the location is C:\Program Files\Microsoft Office\Office16\. 64-bit Windows the location is C:\Program Files (x86)\Microsoft Office\Office16\. 32-bit Windows the location is C:\Program Files\Microsoft Office\Office16\. The tool is found in the following locations in Outlook 20. This repair utility can be launched by double-clicking on its icon. Step 1: Close Outlook and start the Microsoft Inbox Repair Tool that scans the damaged PST file for errors. The steps to repair the damaged or corrupt PST file has been described in a step-by-step manner: PST Repair Process by Inbox Repair Tool (scanpst.exe) Try this and see if you can undo the damages caused! In such situations, you should begin with the Inbox Repair Tool (scanpst.exe) as the first option for your damaged or corrupt PST file. 
To be able to access the data items such as emails, contacts, calendars, tasks, and journals, you would have to repair your Outlook’s PST file. If you are unable to open PST file in Outlook 2016 or 2013, then certainly, there exists some issue with the file.
0 kommentar(er)
