Diagnosing the Error
When Outlook reports it cannot create the Outlook data file (typically a .pst file), the message indicates that the application was unable to write or create the personal archive that stores offline items. This can block sending and receiving, prevent new folders, and interrupt backups. Common causes include incorrect default data file paths, insufficient file system permissions, a damaged current profile, or low disk space on the drive where Outlook attempts to create the file. The following sections cover how to identify the trigger and apply verified fixes.
Confirm the Exact Error and Location
Start by capturing the full wording and any error codes in the dialog. Note whether Outlook references a specific .pst filename or simply states it cannot create data file. You can inspect current data file paths in File > Account & Settings > (Info/Advanced) > Data Files. Verify that the listed path is valid on disk, that the folder exists, and that you can browse it in File Explorer. If the path points to a missing drive or network share, that often explains the failure.
Permissions and File System Checks
NTFS Permissions on the Data Folder
The account running Outlook must have write and create permissions on the folder containing the .pst file. If the path is under Program Files, Users, or a system-protected location, move it to a user-writable directory such as Documents\Outlook Files. Use the folder’s Security tab to ensure your user account includes Modify and Write permissions. Avoid disabling real-time antivirus permanently; instead add an exclusion for the Outlook data folder and the Outlook executable.
| Attribute | Verified Detail | Source Type |
|---|---|---|
| Typical .pst location | User\Documents\Outlook Files\Outlook.pst | Best practice recommendation |
| Required NTFS permissions | Modify/Write for the signed-in user | FileSystem guidance |
| Max recommended .pst size | 50 GB (ANSI), 20 GB (Unicode) for stability | Microsoft guidance |
| Common error codes | 0x80040115, 0x80040111, CANNOT_CREATE_FILE | Support documentation |
| Minimum free disk space | 1.5× the size of the intended .pst | Capacity planning |
Correct Data File Settings and Paths
Misconfigured defaults are a frequent cause. In Data Files, verify each account points to a valid drive and folder. If a listed file is missing or moved, either repair the path or create a new .pst in a reliable location. When creating a new data file, accept the suggested filename or explicitly choose a .pst under 20 GB for Unicode profile use. Avoid spaces or special characters in folder names, and do not store data files on the desktop or root of the system drive.
Profile and Application Integrity
Create a New Outlook Profile
If permissions and paths check out, the current profile may be damaged. Create a new Windows profile and add the same Exchange or POP/IMAP accounts. Set the new profile as default, then launch Outlook and allow it to create a fresh .pst in the recommended location. This often resolves persistent creation failures linked to profile corruption.
Repair Office and Antivirus Conflicts
Use the built-in Quick Repair in Control Panel or Settings > Apps > Office > Modify > Quick Repair. If that does not resolve the issue, run an online repair. Temporarily pause any third-party antivirus or endpoint protection and retry creating the data file. If successful, adjust exclusions to balance security and functionality.
Workarounds and Recovery Options
- Move existing large .pst files to another drive and compact them to free space.
- Create a new .pst manually via File > Open & Export > Open Outlook Data File and point to a trusted folder.
- If the file is damaged, use ScanPST (Outlook Inbox Repair Tool) located in the Office installation folder.
- Export critical items to a .pst or .ost, then remove and re-add the account in Outlook.
When to Escalate
If the error persists after correcting permissions, paths, and profiles, consider recreating all data files in a clean profile, then restoring content from backups. For managed devices, contact IT to check group policies that may redirect data files or restrict disk writes. Persistent failures may indicate disk or filesystem issues that require CHKDSK or professional support.