ErrorFindly
0x800401FOfficeHigh

Error 0x800401F — PST Cannot Be Accessed | Microsoft Office Fix

Microsoft 365Office 2021Office 2019Office 2016

What Does 0x800401F Mean?

Outlook cannot open or access the Personal Storage Table (PST) file. The file may be locked, corrupted, or in an inaccessible location.

Real-World Causes

  1. 1PST file is on a network drive that is currently unavailable
  2. 2File permissions changed preventing Outlook from reading the PST
  3. 3PST file locked by another application or process
  4. 4PST file stored on removable media that was disconnected

Symptoms

  • ⚠Error on Outlook startup about data file
  • ⚠Cannot open folders in the PST file
  • ⚠Outlook prompts to locate a data file
  • ⚠Previous emails and data inaccessible

DIY Fix

Beginner-friendly steps you can try at home

  1. 1Verify the PST file exists at the expected location
  2. 2Copy the PST file to a local drive if it's on a network share
  3. 3Check file permissions — right-click the file > Properties > Security
  4. 4Ensure no other program is locking the PST file

Advanced Fix

For experienced users and IT professionals

  1. 1Remove the PST reference from Outlook: File > Account Settings > Data Files > Remove
  2. 2Re-add the PST file: File > Open & Export > Open Outlook Data File
  3. 3Run scanpst.exe to check for corruption
  4. 4Check disk health using chkdsk /f

Frequently Asked Questions

Can I store PST files on a network drive?
Microsoft does not support or recommend storing PST files on network drives due to data corruption risk. Always keep PST files on a local hard drive for best reliability.
How do I move a PST file to a new location?
Close Outlook. Move the file to the new location. Reopen Outlook — it will ask for the file location. Browse to the new path. Alternatively, remove and re-add the data file in Account Settings.

Related Error Codes

0x8004010FOutlook Data File Error0x80040600Outlook Data File Corrupt0x80040119Unknown Outlook Error

About the Author

Windows Troubleshooting Team

Verified against official Microsoft documentation and real-world diagnostic data. Error behavior confirmed across Windows 10, Windows 11, and Windows Server.