How to fix 0x8004010F after importing MBOX into Outlook
MBOX does not import straight into Outlook, so this appears after converting the MBOX to a PST and adding it to Outlook. The error means Outlook cannot access the data file, usually a profile or file-path problem. Jump to your situation below or work through the methods in order.
By Neeraj Singh ~7 min Updated Jun 2026 90% found this helpful
Error message
0x8004010F: Outlook data file cannot be accessed. The operation failed, an object could not be found.
Summary
0x8004010F (“Outlook data file cannot be accessed”) shows up in an MBOX migration after you convert the MBOX to a PST and add it to Outlook, because Outlook then cannot reach the data file. Microsoft attributes it to a corrupted Outlook profile or a changed or wrong data-file path: the PST is not where the profile expects it, the default data file is misconfigured, or the profile itself is damaged. Antivirus or permissions can also block access. The fix is to confirm the PST's actual location in Account Settings, point the profile at it (or set a valid default data file), and if the profile is corrupt, create a fresh Outlook profile and map the converted PST into it. Checking permissions and pausing antivirus clears the remaining causes.
What this error means
Outlook does not read MBOX, so a migration converts the MBOX into a PST and adds that PST to a profile. The 0x8004010F error means Outlook cannot access that data file. Microsoft points at two causes: the data-file path is wrong or has changed, or the Outlook profile is corrupt.
In a migration both are easy to hit. The converter may place the PST somewhere the profile is not looking, or the default data file may be set incorrectly, so Outlook cannot find it. A profile damaged during all the configuration changes produces the same result. Pointing the profile at the real PST, or rebuilding the profile, restores access.
Common causes
The PST is not at the path the Outlook profile expects.
The default data file in the profile is misconfigured.
The Outlook profile is corrupt.
Insufficient permissions on the PST file or its folder.
Antivirus or a backup tool is locking the data file.
The PST was moved after it was added to the profile.
Expert insight
“People hit this right after a migration and assume the conversion failed, but the PST is usually fine, Outlook just cannot find or open it. Either the file is not where the profile thinks it is, or the profile got scrambled during all the setup. So I check the data-file path in Account Settings first, point it at the real PST, and if the profile itself is rotten, I build a clean one and map the PST in. Outlook opens it and the imported mail is all there.”
Manager, Tech Support & Operations · 19+ years fixing Windows and system errors
✓ How to fix it
Method 1
Check the data-file path
1In Outlook, go to File, Account Settings, Account Settings, then the Data Files tab.
2Confirm the converted PST is listed and that its path matches where the file actually is.
3If it is missing, click Add and browse to the real PST.
Method 2
Fix the default data file
1On the Data Files tab, make sure a valid data file is set as the default (it has a check mark).
2If the default points at a missing or wrong file, set a valid one.
3Restart Outlook.
Method 3
Create a fresh profile
1If the profile is corrupt, open Control Panel, Mail, Show Profiles, and Add a new profile.
2Configure your account, then add the converted PST via Open Outlook Data File.
3Set the new profile as default and restart Outlook.
Method 4
Check permissions
1Make sure your Windows account has read and write permission on the PST file and its folder.
2Move the PST out of any protected or synced location into a normal local folder.
3Then reopen it.
Method 5
Pause antivirus
1Temporarily disable antivirus or a backup tool that may be locking the PST.
2Test send and receive, then re-enable it with the PST folder excluded.
3This clears a lock that blocks access.
In an MBOX migration this is about the PST data file, not the MBOX, so check the data-file path in Account Settings first, that resolves most cases. If the profile itself is corrupt, a fresh profile with the converted PST mapped in is the clean fix. Keep the PST in a normal local folder, not a synced or protected one, to avoid access locks.
Frequently asked questions
What does 0x8004010F mean?
It means Outlook cannot access its data file. Microsoft attributes it to a corrupted Outlook profile or a changed or wrong data-file path, which is easy to hit after an MBOX-to-PST migration.
Why do I get it after importing MBOX?
Outlook cannot read MBOX, so a migration converts it to a PST and adds that to a profile. If the PST is not where the profile expects, or the profile is damaged, Outlook reports 0x8004010F.
How do I fix the data-file path?
In File, Account Settings, Account Settings, Data Files, confirm the converted PST is listed at its real location. If it is missing, Add it and browse to the actual file.
How do I create a new Outlook profile?
Open Control Panel, Mail, Show Profiles, Add. Configure your account, add the converted PST via Open Outlook Data File, set the profile as default, and restart Outlook.
Could antivirus cause this?
Yes. Antivirus or a backup tool can lock the PST so Outlook cannot access it. Pause it to test, then exclude the PST folder from scanning.
Is my imported mail lost?
Usually not. The mail is in the PST; Outlook just cannot reach it. Pointing the profile at the correct PST, or rebuilding the profile, brings it back.
Still not working?
If the path is correct and a fresh profile still cannot open the PST, the converted PST itself may be damaged. Run Microsoft's Inbox Repair tool (SCANPST.EXE) against the PST, then add the repaired file to your profile. You can also submit your error to us for a tailored fix.
