Outlook Data File Cannot Be Accessed: Error 0x8004010F

outlook data file cannot accessed is a Windows error (0x8004010F) raised by Microsoft Outlook when the PST/OST file is inaccessible, typically due to profile corruption, broken file paths, insufficient NTFS permissions, or a locked file handle – not a CLI binary.

control.exe mlcfg32.cpl

This invokes the Mail control panel applet where you can manage Outlook profiles and data file paths. The error most often surfaces during send/receive or at Outlook startup.

Causes of Outlook data file cannot accessed (0x8004010F)

The error indicates the MAPI subsystem cannot obtain a read/write handle on the offline store (OST) or personal folders (PST). Common triggers include:

• Profile corruption – the .OST or .PST file header is damaged, often after an abrupt shutdown or disk write failure.
• Incorrect data file path – the registry key (HKEY_CURRENT_USERSoftwareMicrosoftOffice<version>OutlookProfiles) points to a deleted, moved, or renamed file.
• NTFS permission drift – the user account lacks Modify rights on the parent folder or the data file itself; common after a domain migration or security policy refresh.
• File lock contention – a previous Outlook process (or anti‑virus scanner) holds an exclusive lock on the .OST/.PST file, preventing a fresh mount.
• Network path instability – when the data file resides on a mapped network drive or UNC share, transient disconnects cause the error.
• Corrupted Outlook profile – the profile XML or binary registry hive becomes inconsistent (the official Microsoft root cause listed in the KB article).

Tested on Windows 11 22H2 with Microsoft 365 Apps (Outlook version 2406 Build 17726.20262) and standalone Outlook 2019.

How to fix Outlook data file cannot accessed

Methods and tools overview

Detailed steps (primary recommendation)

1. Close Outlook and kill residual processes – Open Task Manager (taskmgr.exe) and terminate any instance of OUTLOOK.EXE. Then use handle.exe -a outlook.exe to confirm no other process (antivirus, indexer) holds a lock on the .OST.
2. Locate the default data file – Go to Control Panel → Mail → Show Profiles → Properties → Data Files. Note the full path of the file with the check mark (default). Typically: %LOCALAPPDATA%MicrosoftOutlookoutlook.ost or %USERPROFILE%DocumentsOutlook Filesarchive.pst.
3. Run Scanpst.exe on the file – Locate SCANPST.EXE in the Office folder. Run as administrator, select the data file, and click Start. If errors are found, choose Repair. (Do not move the file before repairing – this worsens corruption.)
4. Create a new Outlook profile – Open control.exe mlcfg32.cpl, click Show Profiles → Add. Configure the email account using auto‑detection (for Microsoft 365) or manually (POP3/IMAP). Set this profile as default in the profile selection step at Outlook startup.
5. Open Outlook with the new profile – Close and reopen Outlook. It should sync without error 0x8004010F. If the old .OST file contains data, import it from File → Open → Import. Do not manually copy the .OST over the new one; sync regenerates content from the server.
6. Verify NTFS permissions – Right-click the folder containing the .OST → Properties → Security. Ensure your user has Modify and Write. If the error persists, grant full control temporarily and test.

Useful diagnostic commands

# Windows Event Log – filter Outlook events (source: Outlook, MSExchange, Office)
wevtutil qe Application /q:"*[System[Provider[@Name='Microsoft Office Outlook']]]" /c:10 /e:true /format:text

# PowerShell – events for error 0x8004010F in the last 24 hours
Get-WinEvent -LogName Application -MaxEvents 50 | where { $_.Id -eq 27 -or $_.Message -match "0x8004010F" } | Format-Table TimeCreated, Message -Wrap

# Verify processes locking .OST with Handle (Sysinternals)
handle.exe -a -p "C:Users%USERNAME%AppDataLocalMicrosoftOutlook*.ost"

Common errors

• 0x8004010F after manually moving the PST – Caused by moving the file to a different folder without updating the path in the profile. Solution: In Control Panel → Mail → Data Files, change the path to the new location.
• “Cannot access file” when starting Outlook – Cause: corrupted .OST file but intact profile. Solution: Close Outlook, rename the .OST (e.g., outlook.old), restart Outlook to regenerate it.
• Error only on corporate networks with .OST files in redirected folders – Network latency causes timeouts. Solution: Force local storage via the ForceOSTPath registry policy.
• SCANPST finds no errors but the error persists – Corruption is in the user profile, not the file. Solution: Create a new profile (step 4 in the table).
• Error 0x8004010F with IMAP/POP3 – Though the mechanism differs, the profile can become corrupted similarly. Solution: Repair or recreate the profile; the local .PST can be imported afterward.
• Error appears on every send/receive after an Office update – Add-ins may be improperly disabled. Solution: Start Outlook with /safe; if it works, disable add-ins from File → Options → Add-ins.

scanpst.exe /scan "C:Users%USERNAME%AppDataLocalMicrosoftOutlookarchive.pst"
scanpst.exe /repair "\fileserversharesuser.pst"

scanpst.exe /log C:Logsrepair_%DATE%.log /repair "C:UsersadminOutlooklarge.pst"

robocopy "\serversharefile.pst" "C:Temp" /Z /R:3 /W:5
scanpst.exe /repair "C:Tempfile.pst"

# Windows VM command (via WinRM or RDP)
scanpst.exe /repair "C:Mountedpstfile.pst"

New-MailboxExportRequest -Mailbox user@contoso.com -FilePath "\servershare%username%_%date%.pst" -CompletedRequestAgeLimit 7