Error when you add a PST or OST file on a non-local drive in Outlook 2016


When you try to add a personal folder file (.pst) or an offline folder file (.ost) in Microsoft Outlook 2016, you receive an error message that states that the file can't be opened. These may include:

  • Errors indicating that the PST file has an "invalid file name."
  • "Access denied" errors.

This issue occurs when the following conditions are true:


This issue occurs because of a change in the way that Microsoft Outlook 2016 works with file names and paths. That change can make Outlook 2016 unable to add .pst and .ost files from a non-local drive, which was previously successful.

Change details

Starting with build 16.0.7910.1000, Outlook 2016 makes a specific call to an operating system component to determine the canonical path. With the change, the GetFinalPathNameByHandle Windows API returns the normalized path to a file. In the case of a mapped drive, GetFinalPathNameByHandle converts the path into the Universal Naming Convention (UNC) format. When converting the path, Windows must traverse the entire folder structure of the path to build the final name. If there are insufficient permissions to any folder in the UNC path, GetFinalPathNameByHandle will be unable to return a normalized path. As a result, Outlook 2016 can't add any .pst files from this location.

For example, suppose you have mapped to drive P: \\Server\Share\Restricted\Everyone and you want to add a .pst file from P:\MyData.pst. In this example, you have permissions to the "Everyone" folder in the path, but have no permissions to the "Restricted" or "Share" folder. In this case, Windows is unable to return the normalized path. As a result, Outlook 2016 can't add the .pst file. After an administrator adds List and Read permissions for you to the "Restricted" folder, Windows can traverse the full path and return a normalized path to Outlook. Then you can successfully add the .pst file.

As a reminder, adding .pst files from a network share isn't technically supported in Outlook 2016. While this workaround will allow you to add a .pst file to your profile, you take the risk of any performance or stability problems when you use the .pst file in an unsupported configuration.


To work around this issue, copy the .pst or .ost file to a local hard drive, and then add the file in Outlook 2016.

What if the .pst or .ost file can't be moved from the non-local drive

You can try to continue to use the file in this unsupported configuration. In that case, you may want to contact the vendor that provides the network storage about potential changes that might allow the storage path to be successfully translated into a final canonical path by Windows.


More information on the GetFinalPathNameByHandleA function, which is used by Outlook.