Fix ‘Outlook Data File Cannot Be Accessed’

What this error can identify—and what it cannot

Microsoft documents 0x8004010F: Outlook data file cannot be accessed as a Send/Receive error in Outlook 2010 and 2013. For that documented case, Microsoft identifies a damaged Outlook profile and directs users to locate the default data file, then create a new profile.

The wording alone does not tell you whether the configured store is a PST or an OST, and it is not a structural-corruption finding. An Outlook profile contains the accounts, data files, and settings that tell Outlook where mail is stored. A wrong or damaged profile association can therefore fail even when the underlying file is usable.

This guide’s profile procedures apply to classic Outlook for Windows. If you are using new Outlook or are directly trying to attach a PST, use the PST open-error guide to check current version behavior and the file itself.

Find out which store the profile expects

If classic Outlook opens, Microsoft’s current data-file guidance lists the configured files under File → Account Settings → Account Settings → Data Files. Note the default file, its extension, and its location. Microsoft’s specific 0x8004010F article also explains how to locate the default data file through Windows Mail profile settings when Outlook cannot be used normally.

Test a new classic Outlook profile

1. Keep the existing profile for now.Microsoft warns that removing a profile deletes its offline cached content. Back up PST files first, and test a new profile before deleting the old one.
2. Open the profile picker.Hold Shift while starting Outlook, or press Windows+R and run Outlook.exe /profiles.
3. Create a separate profile.Select Options, select New, name the profile, and add the affected account using the correct provider details.
4. Start Outlook with the new profile.If Send/Receive now works, Microsoft’s test has isolated the old profile as the problem. There is no reason to repair a PST solely because the old profile failed.

Use Microsoft’s maintained instructions to create a profile in classic Outlook. For the version-specific error flow, see Microsoft Learn’s 0x8004010F troubleshooting article.

If the new profile does not resolve it

Return to the store type rather than assuming corruption. For an OST or server-backed account, continue with the account, synchronization, and OST recreation path documented by Microsoft. CorrectPST cannot help with that branch.

For a confirmed PST, make sure the profile points to the intended local file and that the file can be read from its current location. The cannot-open-PST checklist covers moved files, unsuitable storage, permissions, and classic versus new Outlook without repeating those steps here.

Only after the intended PST and its access path are confirmed does file-level repair become reasonable. Microsoft lists the Inbox Repair Tool for Outlook data-file errors; follow the ScanPST procedure on a protected working copy. If its result still fails, the structural repair guide explains the evidence and limits of further recovery.

When CorrectPST diagnosis fits this error

The relevant branch is narrow: the affected store has been confirmed as a Unicode PST, the intended local file is accessible, profile troubleshooting did not resolve the error, and Microsoft’s repair path could not produce a usable result. CorrectPST can then check a format-version-23 PST up to 7.5 GiB for supported structural damage.

CorrectPST cannot repair a profile, account settings, an OST, Windows file access, a deleted file, or a password-protected PST, and diagnosis is not a promise of complete recovery.

Data-file access questions