How to Fix Outlook Error 0x8004010F (Data File Cannot Be Accessed)
What 0x8004010F means
Hit Send/Receive in Outlook and a small error dialog pops up: 0x8004010F: Outlook data file cannot be accessed — sometimes worded as The operation failed. An object could not be found. From that moment, nothing sends and nothing arrives. Emails you compose sit stuck in the Outbox, and new messages stop coming in. The worrying part is how sudden it feels: Outlook worked fine yesterday, and today every sync attempt fails with the same code.
Here is the reassuring part: your emails are not gone. Open your account in a web browser — Outlook on the web or wherever your mail lives — and everything will be there, sending and receiving normally. That proves the problem is local to the Outlook desktop app on your PC, not your account. Microsoft documents 0x8004010F as a corrupted Outlook profile issue: the profile stores the pointer to your data file — the OST or PST file holding your emails, contacts, and calendar — and when that pointer or the profile breaks, Outlook can no longer reach the file, so every send and receive fails.
Common causes
- Corrupted Outlook profile: the number-one cause. A bad shutdown, a disk hiccup, or a failed update can damage the profile, so Outlook points at a data file location that no longer works.
- Data file moved or renamed: if you or a cloud sync tool moved the OST or PST to a new folder, Outlook keeps looking in the old place and reports 0x8004010F.
- Data file stored on OneDrive, USB, or a network drive: Outlook needs its data file on a local disk. Cloud-synced or removable locations cause access failures and corruption.
- Damaged OST or PST file: oversized mailboxes and abrupt shutdowns can corrupt the file's internal structure until a repair tool rebuilds it.
- Antivirus or firewall blocking access: email-shield features can lock the data file during sync, making Outlook think the file is unreachable.
How to fix Outlook error 0x8004010F — step by step
Work through these fixes in order. Most people clear the error by step 2.
- Note the location of your default data file Before rebuilding anything, find out where Outlook thinks your data file lives. Close Outlook completely, then open Control Panel, switch to small or large icons if needed, and open Mail (Microsoft Outlook). Click Show Profiles, select your current profile, and click Properties. In the Mail Setup dialog, click Data Files, then open the Data Files tab in Account Settings. A check mark shows your default data file — note its exact name and folder path, then click Close. You now know which file the new profile needs to point at, and you can check whether that file is actually still there.
- Create a new Outlook profile This is Microsoft's official fix for 0x8004010F, and it resolves the error in most cases. In the Mail Setup window (Control Panel, Mail), click Show Profiles, then click Add. Type a name such as Outlook 2 and click OK. Enter your email address and let Outlook configure the account automatically — it detects the server settings on its own. Back in the Mail window, under When starting Microsoft Outlook, use this profile, select Always use this profile and choose the new profile from the list. Start Outlook and press Send/Receive. With a fresh profile pointing at a healthy data file, the 0x8004010F error is gone. Your mail, contacts, and calendar sync back automatically for Microsoft 365, Exchange, Outlook.com, and IMAP accounts.
- Move the data file back to your local drive If your data file lives anywhere other than your computer's own disk — a OneDrive folder, a USB stick, an external drive, or a network share — move it home. Outlook cannot reliably open data files through cloud sync or removable storage, and 0x8004010F is the classic symptom. Copy the OST or PST file into Documents, Outlook Files on your local drive. Then open Control Panel, Mail (Microsoft Outlook), Show Profiles, select your profile, click Properties, then Data Files. Use Add to point Outlook at the local copy and set it as the default. Restart Outlook and run Send/Receive. Also turn off OneDrive or Dropbox sync for the Outlook Files folder so the file cannot wander back into the cloud.
- Repair the data file with SCANPST If the file itself is damaged, the Inbox Repair tool can usually fix it. Make sure Outlook is fully closed — check Task Manager and end any outlook.exe process. Press Windows key plus R, paste %programfiles%/Microsoft Office/root/office16 into the Run box, and press Enter (on older Office use office15), then double-click SCANPST.exe. Click Browse and select your data file — OST files usually sit in Documents, Outlook Files, and PST files in Documents, Outlook Files or AppData, Local, Microsoft, Outlook. Click Start and let it scan. If it reports errors, tick Make backup of scanned file before repairing and click Repair. The scan can take a while on large mailboxes. Open Outlook afterward and test send and receive.
- Pause your antivirus and firewall, then test Security software can lock Outlook's data file during a send/receive cycle and trigger 0x8004010F. Temporarily disable your antivirus's email or mail-shield feature, and briefly turn off the Windows Defender Firewall: go to Settings, Privacy and Security, Windows Security, Firewall and network protection, and switch off the active network's firewall. Now run Send/Receive in Outlook. If the error disappears, you have found the blocker — re-enable everything and add Outlook's data file folder and outlook.exe to your antivirus exclusions instead of leaving protection off. Never leave the firewall disabled permanently.
- Run an Online Repair of Office When nothing else works, the Office installation itself may be damaged — especially if 0x8004010F appeared right after a Windows or Office update. Close Outlook, then go to Settings, Apps, Installed apps. Find Microsoft 365 or your Office entry, click the three dots, and choose Modify. Select Online Repair rather than Quick Repair: the online option downloads fresh copies of every Office file and replaces anything broken, which takes longer but catches damage a quick repair misses. Stay connected to the internet and keep the PC plugged in while it runs, and don't open any Office apps. Restart your computer when it finishes, open Outlook, and run Send/Receive.
Did this fix it? Quick checklist
- Send/Receive finishes with no error dialog
- Composed emails leave the Outbox within a minute
- New incoming mail arrives on schedule
- The error stays gone after a full PC restart
If the error persists after all six steps, test in a different Windows user account — a damaged Windows profile can cause the same symptom. Run a disk check to rule out file-system damage, and as a last resort back up your PST files and let Outlook build a completely fresh OST by removing the account from the profile and adding it again. Your mail will re-sync from the server for IMAP, Exchange, and Microsoft 365 accounts.
Frequently asked questions
What does Outlook error 0x8004010F mean?
It means Outlook tried to send or receive email but could not open its data file — the OST or PST file that stores your messages, contacts, and calendar. Everything halts: nothing sends, nothing arrives, and the error dialog appears on every Send/Receive. Your account itself is fine — log in through a web browser and your mail works normally — so the problem is local to the Outlook desktop app on your PC.
Why did 0x8004010F appear all of a sudden?
The usual triggers are a corrupted Outlook profile, a data file that was moved or renamed, a file sitting on OneDrive or a USB drive instead of the local disk, or a damaged OST after a bad shutdown. It also shows up after Windows or Office updates that change data file paths. The steps above find the cause in order, starting with the official new-profile fix.
Will creating a new Outlook profile delete my emails?
No. For Microsoft 365, Exchange, Outlook.com, and IMAP accounts, your mail lives on the server and syncs back into the new profile automatically. If you use POP3, your messages are in the old PST file, which stays on your disk — re-attach it to the new profile from File, Account Settings, Account Settings, Data Files, and nothing is lost.
My Outlook data file is on OneDrive — is that causing 0x8004010F?
Very likely. Outlook data files do not belong in cloud-synced folders: sync locks and partial uploads corrupt them and block access. Move the file to Documents, Outlook Files on your local drive, point your profile at the local copy, and exclude the Outlook Files folder from OneDrive or Dropbox sync.
SCANPST cannot open my data file — what now?
First make sure Outlook is fully closed — open Task Manager and end every outlook.exe process, since an open file cannot be repaired. Copy the data file to a local folder and run SCANPST on the copy. If the tool still cannot open it, the file is beyond repair: create a new Outlook profile and let it build a fresh OST, which re-syncs everything from the server for IMAP, Exchange, and Microsoft 365 accounts.